Certbot failed to authenticate some domains

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:

I ran this command: sudo certbot certonly -d domain.com -d www.domain.com

It produced this output:
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: domain.com
Type: unauthorized
Detail: Invalid response from Website Domain Names, Online Stores & Hosting - Domain.com [2a02:4780:b:649:0:3ac3:4056:1]: 404 Domain: www.domain.com
Type: unauthorized
Detail: Invalid response from Website Domain Names, Online Stores & Hosting - Domain.com [2a02:4780:b:649:0:3ac3:4056:1]: 404Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this

My web server is (include version): nginx/1.18.0

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

My hosting provider, if applicable, is:

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

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

Welcome to the community @ykattan

It is difficult to provide specific advice without a domain name.

The error message uses an IPv6 address so you should check that your server responds on that IP. Run this

curl -6 ifconfig.co

which will show you the IPv6 address on your server. If that does not work or does not match the IP shown in the error then adjust your DNS records accordingly (the AAAA record).


Thank you @MikeMcQ
The Server is returned curl: (7) Couldn't connect to server

1 Like

Then it looks like you do not have IPv6 setup. You should remove the AAAA record from the DNS so that Let's Encrypt server does not use it.

You should also confirm your DNS A record matches your server. This is your server IPv4 address:

curl -4 ifconfig.co

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