Certbot Failures: 404 Errors for ACME Challenge Validation on Nginx Server

[sreasor]

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

I ran this command: sudo certbot --nginx --staging

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.

---

1: neverlessband.com
2: www.neverlessband.com

---

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1 2
Requesting a certificate for neverlessband.com and www.neverlessband.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: neverlessband.com
Type: unauthorized
Detail: 2a02:4780:b:1104:0:346c:a4c7:2: Invalid response from http://neverlessband.com/.well-known/acme-challenge/43-GaPQ1FM4cgspbad-luGyudcwKcd7tIsoCv10y4zY: 404

Domain: www.neverlessband.com
Type: unauthorized
Detail: 2a02:4780:b:1104:0:346c:a4c7:2: Invalid response from http://www.neverlessband.com/.well-known/acme-challenge/KdSr2Djt1-UbKFYrrjoQtcv2WwlWDc2GmJqlOsAu1ck: 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.
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):

Ubuntu 24.04

My hosting provider, if applicable, is:

hostingerr

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

2.9.0

[rg305]

Hi @sreasor, and welcome to the LE community forum

There are different web servers responding on IPv4/IPv6:

curl -Ii4 neverlessband.com
HTTP/1.1 200 OK
Server: nginx/1.24.0 (Ubuntu)     <<<<<<<<<<<<<<<<<<<<<<<<< IPv4 shows
Date: Mon, 05 Aug 2024 17:23:27 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 4757
Connection: keep-alive
Vary: RSC, Next-Router-State-Tree, Next-Router-Prefetch, Accept-Encoding
x-nextjs-cache: HIT
X-Powered-By: Next.js
Cache-Control: s-maxage=31536000, stale-while-revalidate
ETag: "sosq6d2do03nf"

curl -Ii6 neverlessband.com
HTTP/1.1 301 Moved Permanently
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
date: Mon, 05 Aug 2024 17:23:32 GMT
server: LiteSpeed     <<<<<<<<<<<<<<<<<<<<<<<<< IPv6 shows
location: https://neverlessband.com/
platform: hostinger
content-security-policy: upgrade-insecure-requests

Make sure both IPs are pointing at your server:

Name:      neverlessband.com
Addresses: 2a02:4780:b:1104:0:346c:a4c7:2
           82.180.133.231

[rg305]

And thank you for using the staging environment while testing:

@sreasor

I ran this command: sudo certbot --nginx --staging

[sreasor]

Hi there,

How would I ensure that both IPs are pointing to my server? I am new to setting up web servers and I got the nginx configuration correct, but I have never set anything up for litespeed.

[MikeMcQ]

Hostinger sets up an IPv6 address to a parking or home page of their own. And, for some reason remains even after you setup your own server address.

You should complain to them as we see this often.

Just remove the AAAA record from your DNS

[rg305]

I'd start by checking what the IPs of the server actually are.
If your HSP didn't provide you with those, try finding them yourself with:
curl -4 ifconfig.me
curl -6 ifconfig.me
OR
curl -4 ifconfig.io
curl -6 ifconfig.io