Figuring out manual cert install

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: devonbisaillon.ca

I ran this command: certbot certonly --manual

It produced this output:Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
Domain: devonbisaillon.ca
Type: dns
Detail: DNS problem: looking up TXT for _acme-challenge.devonbisaillon.ca: DNSSEC: DNSKEY Missing

Hint: The Certificate Authority failed to verify the manually created DNS TXT records. Ensure that you created these in the correct location, or try waiting longer for DNS propagation on the next attempt.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): unknown. looking to make wildcard for NGINX Proxy Manager

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: Web Hosting Canada (uses cPanel for managing)

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): cPanel 110.0.35 for DNS zone

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 2.9.0

When I use dig _acme-challenge.devonbisaillon.ca txt it does produce the updated record that the certbot command asks for

2

This is a bit of an aside, but trying to deal with manually-authenticated wildcard certificates, with NPM, is almost certainly one of the hardest ways to accomplish whatever you're trying to accomplish.

Then I'm guessing you're not validating DNSSEC. Your registrar (and thus the .ca name servers) think that your domain is DNSSEC-signed, but your DNS server isn't actually signing the records. You either need to disable DNSSEC at your registrar, or configure your DNS server to sign DNSSEC. Right now your domain doesn't work with any DNSSEC-validating resolver. It's nothing specific to Let's Encrypt, you just need a working domain first before you can get a certificate.

https://dnsviz.net/d/devonbisaillon.ca/dnssec/

5 Likes
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.