Unable to renew certificate using certbot. nging in my ec2

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

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

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

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: gabapentinshop.com
Type: unauthorized
Detail: 2a02:4780:b:736:0:3b52:8912:b: Invalid response from http://gabapentinshop.com/.well-known/acme-challenge/ac9DjAySGB2_HUKuLqyyuaV-oBcDNJheVI4koQyclnQ: 404

Domain: www.gabapentinshop.com
Type: unauthorized
Detail: 2a02:4780:b:736:0:3b52:8912:b: Invalid response from http://www.gabapentinshop.com/.well-known/acme-challenge/-55ODZDBVeBmLp8uHK_9E0m2BNgxga5aO5zGiGHwD_g: 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.

My web server is (include version):nginx version: nginx/1.24.0 (Ubuntu)

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

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

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

Your DNS has an AAAA record for IPv6 that points to a LiteSpeed server and not your nginx. You need to update that to be your nginx IPv6 address.

See: Let's Debug

Any client trying to use IPv6 will connect to that LiteSpeed server instead of your server. Let's Encrypt favors IPv6 when an AAAA record is present.

5 Likes

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