Cert Renewal Failure

Greetings. Website is available from outside my local area. Cannot renew cert though.

My domain is: XXXXXXaming.com

I ran this command: sudo certbot renew -v --dry-run as well as sudo certbot renew and sudo certbot renew -nginx

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/xxxxxxaming.com.conf


Certificate is due for renewal, auto-renewing...
Plugins selected: Authenticator nginx, Installer nginx
Simulating renewal of an existing certificate for xxxxxxaming.com
Performing the following challenges:
http-01 challenge for xxxxxxaming.com
Waiting for verification...
Challenge failed for domain xxxxxxaming.com
http-01 challenge for xxxxxxaming.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: xxxxxxaming.com
Type: connection
Detail: xx.xxx.51.124: Fetching http://xxxxxxaming.com/.well-known/acme-challenge/3x_PMhGf0RjXDvTM6mCEWzyVbAP-Ygg2QJheFqKunPE: Timeout during connect (likely firewall problem)

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.

Cleaning up challenges
Failed to renew certificate xxxxxxaming.com with error: Some challenges have failed.


All simulated renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/xxxxxxaming.com/fullchain.pem (failure)


1 renew failure(s), 0 parse failure(s)
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): nginx/1.22.1

The operating system my web server runs on is (include version): Debian GNU/LInux 12.5

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

Does not look like either your IPv4 or IPv6 address can connect from everywhere with HTTP (port 80).

The connection failure from Let's Encrypt is reproduced also on Let's Debug (link here)

A port test from my own test server shows port 443 (HTTPS) working but port 80 (HTTP) is "filtered". Most likely by a firewall.

You need port 80 to remain open to validate using the HTTP Challenge (which you are)

curl -I -m5 http://thanegaming.com
curl: (28) Failed to connect to thanegaming.com port 80 after 2702 ms: 
Connection timed out

curl -I -m5 https://thanegaming.com
HTTP/1.1 302 Found
Server: nginx/1.22.1
5 Likes

Aha. Ok. Thank you. I will work on that.

2 Likes

That was it. Originally I had set that up. Router must have put it back on. Thank you

3 Likes