Cannot renew cert (Timeout during connect) on Nginx and Ubuntu

Like a lot of others, I’m having issues renewing my certificate. I’m using the certbot-auto renew command. It’s actually put into a cronjob and I guess never worked. My cert just expired so I only realised now.
It’s just hosted on my own ubuntu server at home, with nothing much on it. I can kind of hit the root but if I refresh it fails (I assume due to expired cert).

If I check the log, this looks kind of important:

Domain: endor.noonecares.dk
Type: connection
Detail: Fetching http://endor.noonecares.dk/.well-known/acme-challenge/em9Ork3aTlbI-109KFVfRHGqbUqRhnVluaWrfQ_S-iQ: Timeout during connect (likely firewall problem)

But I’m not really sure why it can’t connect.

My domain is: endor.noonecares.dk

I ran this command: sudo /opt/certbot/certbot-auto renew

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/endor.noonecares.dk.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for endor.noonecares.dk
Waiting for verification...
Challenge failed for domain endor.noonecares.dk
http-01 challenge for endor.noonecares.dk
Cleaning up challenges
Attempting to renew cert (endor.noonecares.dk) from /etc/letsencrypt/renewal/endor.noonecares.dk.conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
  /etc/letsencrypt/live/endor.noonecares.dk/fullchain.pem (failure)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

All renewal attempts failed. The following certs could not be renewed:
  /etc/letsencrypt/live/endor.noonecares.dk/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: endor.noonecares.dk
   Type:   connection
   Detail: Fetching
   http://endor.noonecares.dk/.well-known/acme-challenge/qj6m06iIogNyiy3_Wd9IM6ZPHI5mwmWJvW41DoxxZWk:
   Timeout during connect (likely firewall problem)

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address. Additionally, please check that
   your computer has a publicly routable IP address and that no
   firewalls are preventing the server from communicating with the
   client. If you're using the webroot plugin, you should also verify
   that you are serving files from the webroot path you provided.

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

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

My hosting provider, if applicable, is: N/A

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 0.33.1 (certbot-auto)

Hi @Nicoolai

your port 80 doesn’t answer, so Letsencrypt can’t check your domain ( https://check-your-website.server-daten.de/?q=endor.noonecares.dk ):

Domainname Http-Status redirect Sec. G
http://endor.noonecares.dk/
46.32.38.117 -14 10.027 T
Timeout - The operation has timed out
https://endor.noonecares.dk/
46.32.38.117 401 0.727 N
Unauthorized
Certificate error: RemoteCertificateChainErrors
http://endor.noonecares.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
46.32.38.117 -14 10.030 T
Timeout - The operation has timed out
Visible Content:

An open port 80 (and a correct port forwarding if you have a router) is required to use http-01 challenge.

You have older certificates:

CRT-Id Issuer not before not after Domain names LE-Duplicate next LE
1114648741 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-01-15 22:51:26 2019-04-15 21:51:26 endor.noonecares.dk
944731492 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2018-11-13 22:46:42 2019-02-11 22:46:42 endor.noonecares.dk
827180829 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2018-09-11 20:46:47 2018-12-10 21:46:47 endor.noonecares.dk
694971681 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2018-07-13 13:12:24 2018-10-11 13:12:24 endor.noonecares.dk

Perhaps you have used tls-sni-01 validation, that’s not longer supported.

1 Like

Thank you very much, that port 80 was indeed the issue. I just forwarded it and everything worked again!
I didn’t realise I had to have port 80 accessible as well.

2 Likes

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