Cannot access acme challenge file

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: mbaessaygenius.com

I ran this command: certbot --nginx -d mbaessaygenius.com -d www.mbaessaygenius.com

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for mbaessaygenius.com and www.mbaessaygenius.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: mbaessaygenius.com
Type: unauthorized
Detail: 2a02:4780:2b:1558:0:ccf:5c35:2: Invalid response from http://mbaessaygenius.com/.well-known/acme-challenge/4kuuawhnkF4NwKuraOQkYgW6Ntcj9YzN_Hn6pXC-VhM: 404

Domain: www.mbaessaygenius.com
Type: unauthorized
Detail: 2a02:4780:2b:1558:0:ccf:5c35:2: Invalid response from http://www.mbaessaygenius.com/.well-known/acme-challenge/vzrGy2zHqTwud2DP5NMlAcHEUoIqDEBysGJL5VNg6_Q: 404

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.

Some challenges have failed.

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

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

My hosting provider, if applicable, is: Hostinger

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

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

Welcome @kmg10303

You should review the IP addresses in your DNS. Make sure they are the public IP for your nginx server.

You have an AAAA record for an IPv6 address but that points to a LiteSpeed server. This was probably put there initially by Hostinger. You should correct this value so it points to your nginx. Or remove it if you don't support IPv6. Note nginx also needs a listen statement for IPv6

Your A record for IPv4 reaches an nginx server. Although right now any requests except the "home" page give an HTTP error 500.

Let's Encrypt prefers the IPv6 AAAA address so fails because it is talking to the LiteSpeed server and not your nginx.

If you remove that Let's Encrypt will use the IPv4 address and might fail with the HTTP error 500. We'd need to see your nginx config to help if that happens.

4 Likes