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

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 -v certonly --register-unsafely-without-email --agree-tos -d mydomain.com

It produced this output: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):

The operating system my web server runs on is (include version):VM kali linux - Apache/2.4.54 (Debian)

My hosting provider, if applicable, is: windows host

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

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

Hi @aml, and welcome to the LE community forum :slight_smile:

As you haven't provided any information that can be used to troubleshoot your problem, I am left to use my :crystal_ball: ...
It said that these two things seem contradictory:
"The Certificate Authority failed to verify the temporary nginx configuration"
"VM kali linux - Apache/2.4.54 (Debian)"

Hope that helps you on your quest.

4 Likes

Hello @aml,

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.

Thank you for assisting us in helping YOU!

2 Likes

Let’s Encrypt offers Domain Validation (DV) certificates.

Thus you need to own and have control over the Domain Name you wish to obtain a certificate for,
from an ICANN Accredited Registrar.

For Let’s Encrypt to issue a Domain Validation (DV) certificate Domain Validation must happen
and it is a CA/Browser Forum Baseline Requirement.

Best Practice - Keep Port 80 Open

What IP addresses does Let’s Encrypt use to validate my web server?
Let’s Encrypt does not publish a list of IP addresses we use to validate,
and these IP addresses may change at any time.

Let's Encrypt uses Multi-Perspective Validation Improves Domain Validation Security - Let's Encrypt

Since these are Domain Validation (DV) certificates the Domain Name System (DNS) is used extensively in the validation process as well a allowing us to assist here on Let's Encrypt community.
DNS Queries need to give consistent results from any location on the Internet, all your authoritative DNS Servers for the Domain need to also give consistent results as well.

Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher. Rate Limits are per week (rolling).

And to assist with debugging there is a great place to start is Let's Debug.

2 Likes

With them you need to Find and purchase a domain name as your first step.

2 Likes

That's funny, you're the second person today who's posted that their domain is mydomain.com. Are you sure you own that domain name? Or are you just using that as a placeholder for your real domain name? If the latter, please stop and tell us the real domain name.

5 Likes