Certificate generation error (The Certificate Authority reported these problems)

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 --nginx -d epslvs.dovianainstitute.com -m roronoawardev@proton.me --agree-tos

It produced this output:
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:

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.

My web server is (include version):
nginx version: nginx/1.18.0 (Ubuntu)
The operating system my web server runs on is (include version):
|Distributor ID:|Ubuntu|
|Description:|Ubuntu 22.04.4 LTS|

My hosting provider, if applicable, is:
I on an EC2 ubuntu instance
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot --version

Welcome @roronoawardev

You have both IPv4 and IPv6 address in your DNS (A and AAAA records). But, the IPv6 address points to a LiteSpeed server not nginx like your IPv4 does.

Let's Encrypt prefers the IPv6 address when present which is shown in the error above (it starts with 2a02:4780).

You should update the IPv6 AAAA record to point to your EC2 instance. Or, remove it if you don't support IPv6.

If you do, make sure your nginx has a listen statement for both IPv4 and v6


Thanks for the prompt reply.
I decided to delete the AAAA record of the domain, do i try the command again or are there other steps i need to perform


Re-running the Let's Debug test showed success so you should just retry the original Certbot command now


Great it works


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