- Checked
- 2026-11-14
The SSL certificate expired. Here is how to fix it.
Visitors get a full-page warning and most of them leave. The fix is usually a renewal that failed quietly weeks ago. Find out why it failed, or it will fail again in ninety days.
Confirm it is the expiry
Run the free server health check on the address. It reads the certificate the server presents and says when it expires. From a terminal, this prints the dates directly:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -datesIf notAfter is in the past, the certificate expired. If the dates are fine but browsers still complain, the server may be sending the wrong certificate for that name, or an incomplete chain.
Why automatic renewal stopped
- The renewal timer or cron job is not running any more, often after an OS upgrade or a move to a new server.
- Port 80 is closed or redirected somewhere that cannot answer the challenge, so the HTTP-01 check fails.
- The domain's DNS now points somewhere else, a CDN or a new host, and the challenge never reaches this server.
- The certificate was renewed on disk, but the web server was never reloaded and still serves the old one from memory.
- The certificate was bought by hand a year ago and nobody had a reminder.
Renewing with Certbot
Most small Linux servers use Let's Encrypt through Certbot. Run these in order and read the output of each before the next:
certbot certificateslists what Certbot manages and when each expires.certbot renew --dry-runtries a renewal without saving it. Its error message names the cause, usually the challenge.certbot renewdoes the real renewal once the dry run passes.systemctl reload nginx(or apache2) makes the web server pick up the new file.systemctl list-timers | grep certbotshows whether the automatic renewal is scheduled again.
See the next one coming
A renewal that fails quietly gives you weeks of warning that nobody reads. Something should look at the certificate from outside and tell you when its expiry date gets close or it stops being valid.
The free health check does that on demand. If you look after several sites for clients, Site Watch reads every site's certificate once a day as part of its server health check, and tells you when the score drops.
When to hand it over
If the dry run fails and the message does not make sense, or the certificate sits behind a load balancer or a panel you did not set up, our Server Rescue covers it: one incident at a fixed $69, a same-day start listed at $109, and nothing to pay if we cannot fix it. The fix includes finding why renewal stopped, so it does not expire again.
Questions people ask
- Can I just click through the certificate warning?
- You can, your visitors mostly will not, and browsers make it harder each year. Payment forms and logins should not be used until the certificate is valid again.
- How long does a Let's Encrypt certificate last?
- Ninety days. Certbot tries to renew it when about thirty days are left, so an expired one means renewal had been failing for about a month.
- The certificate is renewed but browsers still show the old one. Why?
- The web server keeps the certificate it loaded at start. Reload it (
systemctl reload nginxor apache2) after a renewal, and check that the site's config points at the renewed files. - What does fixing an expired certificate cost?
- With us, Server Rescue at $69 for the incident, or $109 for a same-day start. No fix, no fee.
More server help
- Renewing a Let's Encrypt certificate
- Too many redirects
- DNS not resolving or still on the old server
- Server down: what to check first
- 502 Bad Gateway on nginx
- 504 Gateway Timeout
- Error establishing a database connection
- WordPress white screen or critical error
- 403 Forbidden on nginx or Apache
- Disk full: no space left on device
- Email from the server going to spam
- Website hacked: the first steps
- Moving a site to a new server
- Linux server hardening checklist
- All server help guides
