Certificate Expired: How to Renew and Redeploy Fast

When a TLS certificate expires, every visitor sees a hard error such as NET::ERR_CERT_DATE_INVALID and the connection is refused. The fix is to renew the certificate, redeploy it with the full chain, and verify. For example, Let's Encrypt issues certificates with a default 90-day lifetime (Let's Encrypt, 2026-11). At the same time, the CA/Browser Forum's SC-081v3 ballot is shortening maximum public TLS certificate lifetimes to 200 days (from 2026-03-15), then 100 days (2027-03-15) and 47 days (2029-03-15). Monitor expiry and renew before the deadline to avoid repeated outages.
Let's Encrypt OCSP end-of-life announcement (2025-08-06).
What an expired certificate does to visitors
Once a certificate passes its notAfter, the browser treats it as invalid and blocks the connection, showing NET::ERR_CERT_DATE_INVALID (some clients fail outright). This differs from "untrusted": the chain is correct, only the time has expired.
Why certificates expire (and the shortening validity window)
Short lifetimes limit the impact of key compromise and mis-issuance and push automation. Let's Encrypt has issued 90-day certificates by default since 2015 (Let's Encrypt, 2026-11); industry rules (CA/Browser Forum SC-081v3) are shrinking the maximum lifetime from 398 days down to 47 days, so automated renewal is no longer optional.
How browsers check certificate status
Beyond expiry, browsers confirm a certificate is not revoked via OCSP/CRL or OCSP stapling. Note that Let's Encrypt retired its OCSP service on 2025-08-06, shifting status checks to mechanisms such as CRLs — but expiry remains the independent and far more common failure point.
Step 1: Confirm the certificate is actually expired
Run openssl s_client -connect yourdomain.com:443 -servername yourdomain.com and read notAfter, comparing it with the server date. Do not confuse an expired root or a stale cached copy — check the served leaf, which you can verify with the SSL Checker.
Step 2: Renew the certificate
Use Certbot/ACME or your CA console to request a new certificate. Common failures: the renewal timer was disabled, port 80/443 validation was blocked by a firewall, or DNS does not point at the server. Run certbot renew --dry-run to troubleshoot.
Step 3: Redeploy with the full chain
Deploy the new certificate together with its intermediates (e.g. Nginx fullchain) and reload/restart the service so the new certificate takes effect. Replacing only the leaf while omitting intermediates introduces a new chain error.
Step 4: Verify the deployment
Re-check notAfter with the SSL Checker or openssl to confirm the served leaf is updated, the chain is complete, and the error is gone.
Step 5: Set up monitoring and automation
Track days-remaining for every certificate with a monitor and alert at roughly 30 days left. Automate renewal where possible and add a CI check that fails on expired certificates in staging, eliminating human miss-renewals at the root.
Troubleshooting checklist
| Symptom | Likely cause | Fix |
|---|---|---|
| All visitors see NET::ERR_CERT_DATE_INVALID | Certificate expired | Renew and redeploy with the full chain; verify with the SSL Checker |
| Error persists despite "renewal" | Wrong/old cert deployed, or cached | Confirm the served leaf notAfter; restart the service |
| Renewal command fails | 80/443 blocked, DNS wrong, timer disabled | Check certbot renew --dry-run; re-enable the timer |
| Some clients OK, others fail | Stale cached cert or clock skew | Clear cache; check client clocks |
| Expiry incidents keep recurring | No monitoring/automation | Alert at ~30 days left; automate renewal |
Related tools and next steps
- Use the SSL Checker to see the exact certificate and chain the server returns.
- Use the Certificate Decoder to parse and verify the full chain.
- Use the Certificate & Key Matcher to confirm the certificate matches its private key.
- Use the Format Converter to convert certificate/key formats (e.g. PEM and PFX).
- Explore the SSL certificate guide for TLS basics, certificate types, and best practices.
Related articles
FAQ
How long does a certificate last?
It depends on the CA and configuration: Let's Encrypt issues 90-day certificates by default (Let's Encrypt, 2026-11), while many commercial certificates were historically one year. Under the CA/Browser Forum SC-081v3 ballot, maximum public TLS certificate lifetimes are shrinking to 200 days (from 2026-03-15), then 100 days (2027-03-15) and 47 days (2029-03-15).
Can I just ignore the expiry warning?
No. An expired certificate is hard-blocked by modern browsers; visitors cannot reach the site securely, and it hurts SEO and trust. Renew immediately rather than bypassing the warning.
I set up auto-renewal, so why did it still expire?
Common causes: the renewal timer was disabled, port 80/443 validation was blocked by a firewall, DNS did not point at the server, or the deploy step was missed so the new certificate never took effect. Run `certbot renew --dry-run` and inspect the actually served leaf to pinpoint it.
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.