Let’s Encrypt has set a date: on 10 February 2027 its default classic profile moves from 90-day to 64-day certificates, and on 16 February 2028 to 45 days. Nothing breaks that day. What breaks is the renewal setup that only ever worked by luck: a timer that stopped, a service that never reloads the new file, a firewall rule that blocks the challenge. Shorter lifetimes give those faults less slack. This post is a 15-minute audit you can run on any box.
What actually changes
Per Let’s Encrypt’s announcements, the default lifetime shrinks in two steps, and the authorization reuse period shrinks with it: from 30 days to 10 days in 2027, and to seven hours in 2028. Staging gets each change about a month earlier. The last 90-day certificate is expected to expire on 11 May 2027. Changes apply to new certificates, so you see 64 days at the first renewal after the switch.

The chart shows how little headroom is left by 2028: a 45-day certificate with a renewal that fails twice is already close to expiry. Let’s Encrypt’s own advice is to renew at roughly two thirds of the lifetime rather than hard-code an interval, and that is what the audit checks.
Step 1: inventory what you have
Start with the certbot version:
sudo certbot --version
You need 4.0.0 or newer for the renewal rule described below. Then list every certificate certbot manages:
sudo certbot certificates
Since Certbot 4.0.0 a certificate is renewed when less than a third of its lifetime remains (for lifetimes of 10 days or less, half). Before 4.0.0 the threshold was a fixed 30 days. A 64-day certificate therefore renews with about 21 days left on a current certbot. If certbot --version prints something older, upgrade first: the fixed 30-day rule still works for 64 days but leaves much less room at 45.
Step 2: confirm the renewal job exists and runs
systemctl list-timers | grep -i certbot
sudo certbot renew --dry-run
The first command should show a next run time. If it prints nothing, check for a cron entry instead (sudo crontab -l, /etc/cron.d/certbot). The dry run talks to Let’s Encrypt’s staging environment and exercises the whole path, including the challenge. A failure here is your most valuable finding: fix it now, not in February.

Step 3: make sure the service picks up the new file
A renewed file on disk does nothing if the web server keeps the old one in memory. Certbot runs scripts from /etc/letsencrypt/renewal-hooks/deploy/ only after a successful renewal. Add one:
sudo tee /etc/letsencrypt/renewal-hooks/deploy/reload-nginx.sh >/dev/null <<'EOF'
#!/usr/bin/env bash
systemctl reload nginx
EOF
sudo chmod +x /etc/letsencrypt/renewal-hooks/deploy/reload-nginx.sh
Swap nginx for apache2, haproxy or whatever terminates TLS for you. Reload, not restart, keeps connections alive.
Step 4: Traefik
Traefik’s documentation says it manages 90-day certificates by default and starts renewing 30 days before expiry. A 64-day certificate still renews comfortably under that rule. The option certificatesDuration (default 2160 hours, i.e. 90 days) is documented as used only to determine renewal dates, so if you set it explicitly, check that it is not pinned to a value that no longer matches the certificates you receive.
Traefik keeps its certificates in acme.json, a JSON object keyed by resolver name (the name you gave under certificatesResolvers), each holding a Certificates list. The filter below walks the whole file, so it works whatever your resolver is called. Read the real expiry dates out of it:
jq -r '.. | .certificate? // empty' acme.json | while read -r c; do
echo "$c" | base64 -d | openssl x509 -noout -subject -enddate
done
Each pair of output lines gives a domain and the date its certificate expires. Anything that looks older than your expected renewal window means Traefik is failing to renew: check its logs for ACME errors.



