My domain is:
hula-hoop.cz
I ran this command:
/usr/local/bin/certbot-auto renew
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/hula-hoop.cz.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 hula-hoop.cz
http-01 challenge for www.hula-hoop.cz
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (hula-hoop.cz) from /etc/letsencrypt/renewal/hula-hoop.cz.conf produced an unexpected error: Failed authorization procedure. hula-hoop.cz (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://www.hula-hoop.cz/.well-known/acme-challenge/XlBAZWnn-pVYD-VM8EHNT00uYwF8tCnY0DVwoDZQfH4: Connection refused, www.hula-hoop.cz (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://www.hula-hoop.cz/.well-known/acme-challenge/6hhKAXFBR_4XjcnMJShEUIEtc1Sj0q7MvReB1RgZuB8: Connection refused. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/hula-hoop.cz/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/hula-hoop.cz/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: hula-hoop.cz
Type: connection
Detail: Fetching
https://www.hula-hoop.cz/.well-known/acme-challenge/XlBAZWnn-pVYD-VM8EHNT00uYwF8tCnY0DVwoDZQfH4:
Connection refused
Domain: www.hula-hoop.cz
Type: connection
Detail: Fetching
https://www.hula-hoop.cz/.well-known/acme-challenge/6hhKAXFBR_4XjcnMJShEUIEtc1Sj0q7MvReB1RgZuB8:
Connection refused
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.2.1
The operating system my web server runs on is (include version):
Debian 7.11
My hosting provider, if applicable, is:
Linode
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.31.0
This install and cronjob have been running happily for a few years. I recently upgraded certbot-auto
as another installation of mine got the email about TLS-SNI-01. I thought it just a question of time before I got that same email so preemptively upgraded. Now the cert is due for renewal, the process is failing.
I am pretty sure this must be something to do with the TLS-SNI-01/http-01 switch. I’ve read a load of other threads which don’t seem to help. Port 80 is open, but redirected, and according to another thread that is enough.
If I manually run certbot-auto renew
and in another terminal watch the contents of docroot, I can see the correct directories and files get created (and then removed). If I manually create those exact dirs/files (with mkdir
and touch
), I can access them via https or http (which just redirects to https). I’ve checked my DNS, everything looks fine AFAICT (and hasn’t changed in years).
Any help appreciated, thank you.