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 web server is (include version):
Apache/2.4.56 (Debian)
The operating system my web server runs on is (include version):
Devuan Chimaera (equiv. Debian 11.1)
My hosting provider, if applicable, is:
Altitud
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 1.12.0
The "only" thing I changed since last renewal is the IP number of the server. Now it is 185.199.25.198, which internally is NATted to 192.168.1.254. The redirection from tana.it to www.tana.it has been there for quite some time. Yet, I find the request for tana.it but not the redirected one:
AAAANotWorking
Error
www.tana.it has an AAAA (IPv6) record (2a06:a003:e016::2) but a test request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address. You should either ensure that validation requests to this domain succeed over IPv6, or remove its AAAA record.
A timeout was experienced while communicating with www.tana.it/2a06:a003:e016::2: Get "http://www.tana.it/.well-known/acme-challenge/letsdebug-test": context deadline exceeded
Trace:
@0ms: Making a request to http://www.tana.it/.well-known/acme-challenge/letsdebug-test (using initial IP 2a06:a003:e016::2)
@0ms: Dialing 2a06:a003:e016::2
@10000ms: Experienced error: context deadline exceeded
I see... Route48.org, which provided the IPv6 link said they're closing down. I hoped that would have lasted until I get new IPv6 addresses, but it didn't. Now I've deleted them. By tomorrow it should work with IPv4 only...
