DE

↑ ↓ select, Enter open, Esc close

Test the renewal of all Let's Encrypt certificates (certbot)

harmless rootSSL and certificatesdebian, ubuntu
root@server
certbot renew --dry-run

Runs a complete renewal against the Let’s Encrypt staging server for every certificate managed by certbot, but saves nothing. This shows in advance whether domain validation works or fails because of a redirect, a firewall or changed DNS, for example. At the end there is a summary with success or failure per certificate.

Note: Configured hooks (--pre-hook and --post-hook) also run during the dry run, such as briefly stopping the web server. Not applicable to Plesk, which manages Let’s Encrypt through its own extension.

Also searched as

  • certbot renew dry run
  • test let's encrypt auto renewal
  • let's encrypt renewal not working
  • check certbot automatic renewal

Related one-liners

All in SSL and certificates

Show all certbot certificates with domains and expiry dates

#certbot certificates
harmlessSSL and certificates

Check the contents of a CSR before submitting it

$openssl req -in example.com.csr -noout -text -verify
harmlessSSL and certificates

Check the SSL certificate expiration date of a website

$openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -dates
harmlessSSL and certificates

Check whether a certificate expires within the next days

#openssl x509 -in /etc/letsencrypt/live/example.com/cert.pem -noout -checkend $(( 30 * 86400 )) && echo "noch gültig" || echo "läuft bald ab"
harmlessSSL and certificates

Check whether a private key matches a certificate

#openssl x509 -noout -modulus -in /etc/ssl/certs/example.com.crt | openssl md5 && openssl rsa -noout -modulus -in /etc/ssl/private/example.com.key | openssl md5
harmlessSSL and certificates

Check whether a server supports TLS 1.3

$openssl s_client -connect example.com:443 -servername example.com -tls1_3 </dev/null 2>/dev/null | grep -E "^New,|Protocol *:"
harmlessSSL and certificates

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.