Certificates

NET::ERR_CERT_DATE_INVALID: expired certificate, what to do

In short. This error means your website's security certificate (its proof of identity, which makes the secure connection possible) has expired: it was not renewed in time. Your visitors see a warning and may leave without entering your site. It is up to you, or to your hosting provider or web provider, to renew the certificate and install it. Once the new certificate is in place, the warning goes away immediately, with no waiting period. If the error only appears on one device, that device's clock is probably wrong.

NET::ERR_CERT_DATE_INVALID means Chrome refused the site's security certificate because its validity date has passed, or has not started yet. If the error appears on every device, your site's certificate has expired: you need to renew and reinstall it. If it appears on one device only, that device's clock is probably wrong.

Last verified: November 18, 2026, in the Chromium and Firefox source code.

What your visitors see

Chrome shows "Your connection is not private", with the code NET::ERR_CERT_DATE_INVALID below it. Under Advanced, its explanation reads as follows (Chromium text):

This server could not prove that it is your-domain.com; its security certificate expired 3 days ago. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to […]. Does that look right? If not, you should correct your system's clock and then refresh this page.

Firefox shows "Warning: Potential Security Risk Ahead", with the code SEC_ERROR_EXPIRED_CERTIFICATE and the exact expiry date.

Step 1: find out whether it is the site or the device

Open the site from another device, on another network.

  • Same error everywhere: the certificate has expired. Go to step 2.
  • Error on one device only: set that device's date and time to automatic, then reload the page.

Our free SSL certificate check shows the real expiry date, as seen from the Internet.

Step 2: renew the certificate

It depends on who provides the certificate.

  • Free certificate provided by the host (most often Let's Encrypt): it normally renews on its own. If it has expired, automatic renewal failed. In the host's customer area, restart the certificate issuance for the domain. The most frequent causes of failure: the domain no longer points to that host, or a redirect blocks validation.
  • Purchased certificate from an authority or reseller: renew the order, validate the domain, then install the new certificate on the server. Paying for the renewal is not enough: until the new certificate is installed, the old one keeps being served.
  • Server you manage (certbot, acme.sh…): run the renewal by hand and read the error shown, then check that the scheduled task is actually running.

Step 3: check that the new certificate is being served

  1. Reload the site in a private window.
  2. Run the free tool again: it should show the new expiry date.
  3. Check every address: with and without www, and every subdomain that has its own certificate.

If the old date still appears, the web server has not been reloaded, or a CDN is still serving the old certificate.

Never be caught out by an expiry again. AttackScout monitoring checks your certificate every day and warns you 30, 14, 7 and 1 day before it expires. Check my domain

Why this is happening more and more

The CA/Browser Forum voted in April 2025 for a gradual reduction of the maximum certificate lifetime, from 398 days to 47 days, in stages from March 2026 to March 2029. The shorter the lifetime, the faster a forgotten manual renewal shows. Automatic renewal is no longer optional.

Frequently asked questions

The certificate is renewed but the error persists. Why?

The new certificate is not being served: web server not reloaded, wrong file installed, or a CDN keeping the old certificate. The free tool shows the certificate a browser actually receives.

My certificate only expires in a month, and the error still shows.

Then the error comes from a certificate that is not yet valid, or from the visitor's clock. Chrome uses the same code in both cases. Check the time on the device concerned.

How long do visitors see the error after renewal?

The change is immediate as soon as the new certificate is served. There is no propagation delay as with DNS.

Sources

Accessed on 11/18/2026.