Help for owners
My SSL certificate should renew by itself but the renewal keeps failing
Short answer
Automatic renewal still has to prove control of your domain each time. It fails when the validation request cannot reach your server, when DNS records are wrong, when a redirect or firewall blocks it, or when the renewal job stopped. Let's Encrypt has also ended its expiry reminder emails, so a failure can go unnoticed.
Does this sound like your situation?
- The certificate is due to expire soon even though it is supposed to renew itself.
- Renewal worked for a year, then stopped.
- A hosting panel or log shows a renewal error.
- Only one of my domains or subdomains fails.
- Nobody warned me the certificate was about to lapse.
Why does this happen?
The validation request cannot reach the site
Let's Encrypt's HTTP check uses port 80 only, and it fails if the port is blocked or if several servers answer and not all of them hold the validation file. A firewall change or a new load balancer is a common trigger.
Confirmed by letsencrypt.orgTechnical detail: A Let's Encrypt certificate did not renew with Certbot
A DNS-based check has bad or stale records
The DNS check looks up a TXT record. It fails if the record is wrong, if DNS has not spread before validation, or if too many old TXT records pile up. Wildcard certificates need this method.
Confirmed by letsencrypt.org
The renewal job stopped running
A server move, an operating system change or a deleted scheduled task silently turns renewal off, and the certificate runs to its end date.
Nobody is told when it fails
Let's Encrypt states that it has ended its expiration email service, so reminders no longer arrive from there. The site owner has to monitor the date.
Confirmed by letsencrypt.org
What can I do about it today?
- Find the real expiry dateClick the padlock in the browser, open certificate details and note the valid-until date.
- Do not delete the certificate or its folderA working but ageing certificate is better than none while the cause is found.
- Ask who set up the renewalA hosting panel, a server job or a service. Knowing which one narrows the cause.
- Tell your developer or host the date and any error textA screenshot of the error is enough.
- Put the expiry date in a shared calendarWith a reminder two weeks ahead, owned by a named person.
When should I bring someone in?
- The date is within a few days.
- Several domains or subdomains share the failing renewal.
- A change to the server, firewall or DNS happened just before it began.
How do I handle it?
- Read the renewal logThe error names the failing check: port, DNS or permission.
- Test renewal without changing anythingA dry run shows whether the fix works before the real certificate is touched.
- Fix the path the check needsOpen the port, correct the redirect, repair the DNS record or restore the job.
- Add monitoring on the dateAn alert well before expiry, to a monitored address.
- Write down how it renewsMethod, schedule and owner, for the next person.
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?
How long does a certificate last?
Let's Encrypt certificates are meant to be renewed automatically. Check the valid-until date in your own certificate, since the interval depends on the provider and setup.
Will visitors see a warning if it expires?
Yes, browsers warn on an expired certificate. See the page on an expired certificate for what to do at that point.
Can I pay for a certificate instead?
You can, but a paid certificate still has to be installed and renewed. The underlying cause of the failure is worth fixing.
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 CertbotSSL_CTX_use_PrivateKey_file("/etc/nginx/ssl/example.com.key") failednginx refuses to start: private key does not match the certificate