HTTP-01 challenge failed for functional domain

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: my-readme-stats.duckdns.org

I ran this command: sudo certbot --nginx -d my-readme-stats.duckdns.org

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Requesting a certificate for my-readme-stats.duckdns.org
Performing the following challenges:
http-01 challenge for my-readme-stats.duckdns.org
Waiting for verification...
Challenge failed for domain my-readme-stats.duckdns.org
http-01 challenge for my-readme-stats.duckdns.org

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: my-readme-stats.duckdns.org
Type: dns
Detail: While processing CAA for my-readme-stats.duckdns.org: DNS problem: query timed out looking up CAA for duckdns.org

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Cleaning up challenges
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): nginx/1.24.0 (Ubuntu)

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

My hosting provider, if applicable, is: Me

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): no

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

1 Like
2

Technically the command I used for that output was: sudo certbot --nginx -vd my-readme-stats.duckdns.org

I have another domain on this server that successfully passed the certbot challenges and got an SSL certificate. It also uses a duckdns domain, so I'm not sure what the problem is.

3

The DuckDNS servers are especially slow right now. It may just work if you try later.

Let's Encrypt queries the authoritative DNS Servers directly. LE is not getting all the responses fast enough querying the DuckDNS severs (that is, it is timing out).

Other tools report the same thing. For example: my-readme-stats.duckdns.org | DNSViz

3 Likes
4

I see, what sort of timeline do these problems usually have? Should I simply try again tomorrow?

5

Hard to say. The Duck people would have a better understanding of that.

I'd refer you to their community forum but I couldn't find one. You could try the duckdns Reddit to get comments from others.

We usually only see the initial "it does not work" report. People don't usually come back to let us know when it started working :slight_smile: And, of course, we don't hear from anyone who happily uses Duck.

2 Likes
6

I have run it again the next day, and it worked!

2 Likes
7

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