Cannot renew certificate

Help
1

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: devrh1.kal800.com

I ran this command: certbot renew --dry-run -v

It produced this output:

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: devrh1.kal800.com
Type: connection
Detail: 89.68.13.20: Fetching http://devrh1.kal800.com/.well-known/acme-challenge/xqpFc0_c3jcewFpwHv7UdAsgYbqHpV46YnOqIJ0Tgnc: 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 devrh1.kal800.com with error: Some challenges have failed.

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

1 renew failure(s), 0 parse failure(s)

My web server is (include version): nginx/1.14.1

The operating system my web server runs on is (include version): Red Hat Enterprise Linux 8.4 (Ootpa)

My hosting provider, if applicable, is:

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.8.0

2

Did you check from an external network that you can connect to the server?

Mostly likely a firewall.

2 Likes
3

I don't see good connections on any port to that domain. You need port 80 open for the HTTP Challenge you are using.

Maybe the IP in your public DNS has changed. What does this show?

curl -4 http://ifconfig.io

I see you have a long history with Let's Encrypt certs. But, something has changed with your internet connection since Oct3 when you got your most recent cert. If not the IP then maybe a firewall, or ISP changes, or change to your own network routing.

3 Likes
4

Well, it happened to be a mistake of firewall port redirection rules. Thanks for suggestions

4 Likes
5

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