The certificate renewed, but the server still serves the old one
Your renewal client says it worked and the new files are on disk, yet clients still get the old certificate. The renewal is done; the new certificate has not reached the connection clients make. This guide finds where it stopped.
Compare what is served with what is on disk
Read the serial and dates the server presents, with your hostname sent as SNI:
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -serial -dates
Then read the same fields from the file your server is configured to use. For certbot that is usually:
openssl x509 -in /etc/letsencrypt/live/example.com/fullchain.pem -noout -serial -dates
If the serials differ, the new certificate exists but is not being served. If they match and clients still see the old one, those clients reach a different machine or layer: look at the same hostname with the free checker, from outside your network.
The service never reloaded
A common cause. Web servers such as nginx and Apache read certificate files when they load their configuration and keep them in memory, so a new file on disk changes nothing until the service reloads. Reload it, then compare again:
sudo systemctl reload nginx
The service name varies by system.
To stop it happening again with certbot, add a deploy hook. Certbot runs every executable file in
/etc/letsencrypt/renewal-hooks/deploy/ after a successful renewal, and only then. A two-line script
such as #!/bin/sh and systemctl reload nginx is enough. Other clients have the same
step: look for the reload or deploy hook in your client's docs.
The certificate lands somewhere else
-
A copied file. The server reads a copy, such as a file under
/etc/nginx/ssl/, and nothing replaces it. Point the server at the path your client writes, or copy the file in the deploy hook. - A load balancer, CDN or proxy. TLS ends at a layer in front of the server, which holds its own certificate. A renewal on the origin never reaches it, so replace the certificate there.
-
Several servers. One has the new certificate and others do not, so the result changes between
connections. Check each one:
openssl s_client -connect 203.0.113.10:443 -servername example.com - A second service. A mail server on 465 or 993 reading the same files needs its own reload.
How CertWatch catches this
CertWatch connects from outside every hour, on every plan, and reads the certificate clients actually get. A renewal it has not seen served is not done, whatever the renewal client reports, so the endpoint turns Late past its renewal point and CertWatch alerts you. From outside, a renewal that was never deployed looks the same as one that never ran, so the alert's steps cover both. When some addresses serve the new certificate and others still serve the old one past its renewal point, the alert names them. A Recovered alert follows once a check finds the certificate Healthy.
Check a hostname now with the free checker, no account needed, or add it to CertWatch so the next renewal is checked from outside.