Issue with nginx & active24

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. |, 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 -d

It produced this output: Domain:
Type: unauthorized
Detail: 2a00:4b40:aaaa:2005::7: Invalid response from 404

Type: unauthorized
Detail: 2a00:4b40:aaaa:2005::7: Invalid response from 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):

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

My hosting provider, if applicable, is: dedicated server

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

❯ certbot --version
certbot 1.21.0

letsencrypt.txt (162.8 KB)

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

"detail": "2a00:4b40:aaaa:2005::7: Invalid response from 404",

Does your site work via IPv6?

curl -Ii4     <<<<<<<<<<<<<<<<<<<<<<<<< IPv4
HTTP/1.1 200 OK
Server: nginx/1.18.0 (Ubuntu)     <<<<<<<<<<<<<<<<<<<<<<<<< NGINX
Date: Tue, 05 Dec 2023 23:50:36 GMT
Content-Type: text/html
Content-Length: 612
Last-Modified: Tue, 05 Dec 2023 23:27:49 GMT
Connection: keep-alive
ETag: "656fb1f5-264"
Accept-Ranges: bytes

curl -Ii6     <<<<<<<<<<<<<<<<<<<<<<<<< IPv6
HTTP/1.1 200 OK
Server: openresty     <<<<<<<<<<<<<<<<<<<<<<<<< OPENRESTY
Date: Tue, 05 Dec 2023 23:50:41 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Keep-Alive: timeout=10
Vary: Accept-Encoding
Vary: Accept-Encoding

the ipv6 was configured from Active24... I noticed it only now, I removed the AAAA records and now I'm waiting until I can do another validation. because I exceeded the limit.,

1 Like

The one hour limit?


Yes that one

❯ less /var/log/nginx/error.log
❯ sudo certbot --nginx -d -d
[sudo] password for coffee:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for and
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
╭─    /var/www/html 

Let us know how this goes.
[ once you've woken up and had the required amount of cooffee :wink: ]


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