Dry run failed on trying to update certbot/letsencrypt


#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. https://crt.sh/?q=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: gormanlab.science

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

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


Processing /etc/letsencrypt/renewal/gormanlab.science.conf


Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for gormanlab.science
Cleaning up challenges
Attempting to renew cert (gormanlab.science) from /etc/letsencrypt/renewal/gormanlab.science.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/gormanlab.science/fullchain.pem (failure)


** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/gormanlab.science/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)


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

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.1 LTS

My hosting provider, if applicable, is: digital ocean

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.28.0

I got the email about end of life for TLS-SNI-01.
I followed the instructions at How to stop using TLS-SNI-01 with Certbot
Now my server does not respond at all
Previously I manually updated my certificate when I got the expiration email with:
/var/elabftw/letsencrypt/letsencrypt-auto renew --no-self-upgrade

My server is running elabftw


#2

Hi @cbgorman

the standalone authenticator creates an own webserver. This is good, if there is no webserver. But if you have a running webserver, you should use this webserver.

You have a nginx, so use

certbot renew --nginx --dry-run

#3

Thanks for the prompt response. I think the problem is that my application is running inside docker, and the external update is interfering with it. I am going to try to contact the application developer.

  • C