Help for owners
My website says "Not secure" because the SSL certificate expired
Short answer
A certificate is only valid for a limited time, and when it lapses browsers warn visitors and many will leave. Let's Encrypt certificates last 90 days and are meant to renew automatically. If the renewal job stopped, someone must renew once and repair the automation, so it does not happen again.
Does this sound like your situation?
- Browsers show a full-page warning or "Not secure" next to my address.
- The padlock disappeared from the site.
- Customers message me that the site is unsafe.
- An API or app that calls my site suddenly fails.
Why does this happen?
Certificates have an end date
Let's Encrypt certificates are valid for 90 days by default, and the service recommends renewing every 60 days. The lifetimes cannot be changed.
Confirmed by letsencrypt.org
The renewal job stopped
Renewal is normally automated, but the schedule can stop after a server change, a changed firewall, or a moved website.
Technical detail: A Let's Encrypt certificate did not renew with Certbot
The new certificate was never loaded
A certificate can renew on disk while the web server keeps serving the old one until it reloads.
Technical detail: The site looks fine in a browser but its SSL chain is incomplete
Nobody owns it
The person who set it up has left, the reminder emails go to an old address and no one is watching the date.
What can I do about it today?
- Do not click through the warning on customers' behalfTell customers to wait. A warning page is also the one they should not accept.
- Check who installed the certificateIs it from your host, a service like Let's Encrypt or one you bought? Find who has the login.
- Look at the dateIn the browser, click the warning or padlock and read the certificate's end date. Send it to your developer.
- Contact your host or developer nowAsk for a one-off renewal today, then a fix for automatic renewal.
- Do not delete anything on the serverRemoving certificate files without a backup can take the site down completely.
When should I bring someone in?
- Your host says it is not their responsibility and no one else has access.
- The site takes payments or logins and visitors are blocked.
- It has expired before.
How do I handle it?
- Renew the certificate onceI renew it and confirm from outside that the browser shows a valid certificate.
- Find why automation stoppedI read the renewal log and find the exact reason, not a general one.
- Prove the next renewal worksI run a test renewal, so the next one is known to pass.
- Add a warning before it expiresI set up a check that alerts you well before the date, and I note who owns it.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why does it expire so often?
Let's Encrypt certificates are valid for 90 days. Short lifetimes are intended to be paired with automatic renewal.
Will Let's Encrypt remind me?
Not any more. Let's Encrypt has ended its expiration email service, so a monitor is the safer reminder.
Is my data at risk?
An expired certificate is a trust and availability problem, not proof of a break-in. I check the logs anyway.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:A Let's Encrypt certificate did not renew with CertbotIs this SSL certificate chain broken?The site looks fine in a browser but its SSL chain is incompleteSSL_CTX_use_PrivateKey_file("/etc/nginx/ssl/example.com.key") failednginx refuses to start: private key does not match the certificateMixed Content: The page at 'https://example.com/' was loaded over HTTPS, but requested an insecure script 'http://example.com/app.js'. This request has been blocked; the content must be served over HTTPS.An HTTPS page is blocked from loading an insecure http:// resource