← Guides

Why Let's Encrypt renewals fail, and how to catch it before expiry

Updated 2026-11-22. Sources are listed at the end.

Let's Encrypt certificates are short-lived and meant to renew automatically. When renewal stops, nothing looks wrong until the certificate expires, and Let's Encrypt no longer emails you before that happens (that service ended on 4 June 2025).

1. The renewal job is no longer running

After a server migration, a container rebuild or an operating system upgrade, the cron entry or systemd timer that ran your ACME client may be gone. Check that it exists, then test a renewal against Let's Encrypt's staging environment:

systemctl list-timers | grep -i certbot
crontab -l | grep -i -E "certbot|acme"
sudo certbot renew --dry-run

Other clients (acme.sh, Caddy, Traefik, a hosting control panel) keep their own logs; look for the last successful renewal there.

2. Port 80 is closed, or goes somewhere else (HTTP-01)

The HTTP-01 challenge can only use port 80. Let's Encrypt follows up to 10 redirects, but only to http: or https: URLs on ports 80 or 443. Renewals fail when a firewall rule closes port 80, when a CDN or load balancer does not pass /.well-known/acme-challenge/ to the server running the client, or when a redirect sends the request to another host. HTTP-01 cannot issue wildcard certificates.

3. DNS changed, or the DNS-01 credentials did

If the domain now points at a different server or CDN, the HTTP-01 request reaches a machine that does not have the challenge file. With DNS-01, the client creates a TXT record at _acme-challenge.<your domain> through your DNS provider's API, so a rotated or expired API key stops renewals. Let's Encrypt notes that DNS changes can take time to reach every DNS server and that some setups need to wait as much as an hour before validating.

4. Rate limits after repeated failures

A failing client that retries in a loop can hit Let's Encrypt's limits, including up to 5 authorization failures per hostname per account per hour, and up to 5 certificates for the exact same set of names every 7 days. Renewals coordinated through ACME Renewal Information (ARI) are exempt from the rate limits. Fix the cause before retrying.

5. It renewed, but the server still presents the old certificate

Renewal writes new files. The web server has to reload them, and a load balancer, CDN or appliance may hold its own copy that also needs updating. Check what the server actually presents with openssl (see how to check when a certificate expires) and compare it with the files on disk.

6. Lifetimes are getting shorter

Let's Encrypt has announced shorter default certificates: 64 days from 10 February 2027 and 45 days from 16 February 2028 (with an opt-in 45-day profile planned for 13 May 2026). It says a fixed 60-day renewal interval will no longer be enough, and recommends ARI or renewing about two-thirds of the way through a certificate's lifetime. It also recommends monitoring for missed renewals.

How to notice in time

  • Check the certificate each server presents on a schedule (the openssl -checkend command) and alert well before expiry.
  • Watch issuance: if a hostname's newest certificate in CT logs is getting close to expiry, its renewal has probably stopped.

Doing this for many domains?

If renewal stops, no newer certificate appears in CT logs, so Lindenkit's 30, 14, 7 and 1-day emails arrive while there is still time to fix it. It cannot catch case 5 above (renewed but not installed), because it does not connect to your servers.

Lindenkit Certificates lists the certificates logged in public Certificate Transparency logs for each domain you add, tracks the domain's registration expiry through RDAP, and emails you 30, 14, 7 and 1 days before either lapses. It reads public data and does not connect to your servers, so it shows the latest certificate per CT logs, which may not be the one a server presents. Free for up to 10 certificates; Base US$29/month for 100.

How Lindenkit Certificates works Try the free checker

Sources