In short. The certificate that secures your website has expired: visitors see a "connection is not private" warning and most of them leave. This free certificate was supposed to renew itself, but automatic renewal failed without warning anyone. Your hosting provider, or whoever manages your server, needs to restart it and find the cause. Once the cause is found, renewal takes a few minutes, and the site is back to normal as soon as the new certificate is in place.
A Let's Encrypt certificate that expires despite automatic renewal almost always has one of these causes: the scheduled task no longer runs, validation fails (port 80 closed, domain pointing elsewhere), or the certificate was renewed but the web server was not reloaded. And since June 4, 2025, Let's Encrypt no longer sends a warning email before expiry: nobody gets notified.
Last checked: November 18, 2026, in the Let's Encrypt and certbot documentation.
The symptom
Visitors see "Your connection is not private" with the code NET::ERR_CERT_DATE_INVALID (Chrome) or SEC_ERROR_EXPIRED_CERTIFICATE (Firefox). See our page on this error.
Why nobody was warned
Let's Encrypt stopped its expiration emails on June 4, 2025 (announced January 22, 2025). It recommends a monitoring service instead. Many sites were still counting on those emails without knowing it.
Step 1: test the renewal
On the server, as administrator:
certbot renew --dry-runThis command simulates the renewal without changing anything. If it fails, the message says why. Detailed logs are in /var/log/letsencrypt.
On shared hosting there is no command: restart the certificate issuance in the customer area and read the error message shown.
Step 2: fix the cause
Validation fails (HTTP-01). The most common method checks a file on your site, and Let's Encrypt states that it goes only through port 80. It fails if:
- port 80 is closed (firewall, router, a host that only listens on HTTPS);
- the domain points to another server (change of host, CDN, modified DNS);
- you have several servers, and the validation file is not present on all of them.
Redirects to HTTPS are not a problem: Let's Encrypt follows them, and does not check the certificate at that point, so it can be expired.
Wildcard certificate (*.your-domain.com). It requires DNS validation (DNS-01), which does not work through port 80. If access to your DNS API has changed (expired token, change of provider), renewal fails.
The scheduled task no longer runs. Certbot usually installs a task that runs certbot renew regularly. Check that it exists: systemctl list-timers (systemd timer) or the /etc/crontab file and /etc/cron.*/. After a server migration, it is often forgotten.
Step 3: reload the web server after renewal
A renewed certificate is only served after the web server is reloaded. Without that reload, the new file is on disk, and visitors still get the old one. Certbot provides a hook that only runs after a successful renewal:
certbot renew --deploy-hook "systemctl reload nginx"(or apache2/httpd depending on the server). A script placed in /etc/letsencrypt/renewal-hooks/deploy/ has the same effect for all renewals.
Step 4: prepare for shorter certificates
Let's Encrypt is shortening its certificate lifetimes: 64 days for the default profile from February 10, 2027, then 45 days from February 16, 2028 (announced December 2, 2025). It warns that renewing at a fixed 60-day interval will no longer be enough.
Certbot, since version 4.0.0, renews when less than a third of the lifetime remains, which adapts to shorter lifetimes on its own. Before that version, the threshold was fixed: 30 days. Update certbot, and never renew by hand.
Step 5: check from the Internet
Run our free SSL certificate check again: the new expiry date should show. Check every address, with and without www.
Replace the emails Let's Encrypt no longer sends. AttackScout monitoring checks your certificate every day, from the Internet, and warns you 30, 14, 7 and 1 day before it expires. Check my domain
Frequently asked questions
certbot renew --dry-run succeeds, but the site still shows the old certificate.
The web server was not reloaded, or a CDN is serving its own certificate. Add the hook from step 3 and check the CDN's configuration.
My host manages the certificate. What can I do?
Restart the issuance in the customer area. If it fails, check that the domain really points to that host, then contact its support with the error message.
Should I switch to a paid certificate to avoid the problem?
No. A paid certificate also expires, and its maximum lifetime is shrinking just like the others (CA/Browser Forum). What avoids the problem is automatic renewal that works and monitoring that confirms it.
Sources
Accessed on November 18, 2026.
- Let's Encrypt, Ending Support for Expiration Notification Emails (January 22, 2025, ends June 4, 2025): https://letsencrypt.org/2025/01/22/ending-expiration-emails/
- Let's Encrypt, Decreasing Certificate Lifetimes to 45 Days (December 2, 2025): https://letsencrypt.org/2025/12/02/from-90-to-45/
- Let's Encrypt, Challenge Types (updated February 12, 2026): https://letsencrypt.org/docs/challenge-types/
- Certbot, User Guide (
renew,--dry-run,--deploy-hook, timers, logs, one-third threshold since 4.0.0): https://eff-certbot.readthedocs.io/en/stable/using.html