SSL certificates7 min read
NET::ERR_CERT_DATE_INVALID: what it means and how to fix it
By the RenewalRemind team
NET::ERR_CERT_DATE_INVALID means the browser thinks the site's SSL certificate is outside its valid dates. If only you see it, your device's date and time are wrong — fix the clock. If everyone sees it, the site's certificate has expired (or a renewed one was never installed): the owner must renew it, install it with the full chain on every server, reload the web server and fix the renewal job.
Key takeaways
- One visitor sees it → check that device's date, time and time zone.
- Everyone sees it → the certificate expired; renew and install it on every server, CDN and load balancer.
- Firefox shows SEC_ERROR_EXPIRED_CERTIFICATE; Safari shows "This Connection Is Not Private" for the same problem.
- Find out why renewal failed (stopped timer, broken validation, server not reloaded) or it will happen again.
NET::ERR_CERT_DATE_INVALID appears under Chrome's "Your connection is not private" warning. It means the browser compared the site's SSL certificate dates with the current date and the certificate wasn't valid — either it has expired, it isn't valid yet, or the device's clock is wrong. The first question is who sees it.
| Browser | What it shows |
|---|---|
| Chrome / Edge | Your connection is not private — NET::ERR_CERT_DATE_INVALID |
| Firefox | Warning: Potential Security Risk Ahead — SEC_ERROR_EXPIRED_CERTIFICATE |
| Safari | This Connection Is Not Private |
| Android Chrome | Your clock is behind / ahead, or NET::ERR_CERT_DATE_INVALID |
If you're a visitor: fix your device's clock
If the site works for others (or on your phone) but not on one device, that device's date or time is almost certainly wrong. A clock set to 2019 makes every current certificate look "not yet valid".
- Windows: Settings → Time & language → Date & time → turn on Set time automatically and Set time zone automatically, then click Sync now.
- Mac: System Settings → General → Date & Time → turn on Set time and date automatically.
- Android: Settings → System → Date & time → Set time automatically.
- iPhone: Settings → General → Date & Time → Set Automatically.
If the clock keeps resetting on an older computer, the motherboard's CMOS battery may be dead. If the clock is right and only one network shows the error, a captive portal or security software that inspects HTTPS may be the cause.
If you own the site: the certificate expired
If everyone sees the error, check the live certificate from any computer:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
| openssl x509 -noout -datesIf notAfter is in the past, the certificate expired. Fix it in this order:
- Renew the certificate. On Let's Encrypt with Certbot:
sudo certbot renew. On cPanel or a managed host: run AutoSSL or reissue from the SSL section. For a paid certificate: reissue it from your certificate authority's dashboard. - Install it with the full chain. Use the full-chain file (
fullchain.pemfor Certbot), not just the site certificate, or some devices will reject it even after renewal. - Reload the web server.
sudo systemctl reload nginxorsudo systemctl reload apache2. Until it reloads, the server keeps serving the expired certificate. - Update everything in front of the site. Load balancers, CDNs, reverse proxies and any second server each hold their own copy of the certificate.
- Check again from outside with the command above or a fresh browser window.
Find out why it expired
Renewing fixes today. Finding the cause stops it happening again in 90 days — or sooner, as certificate lifetimes shrink.
systemctl list-timers | grep certbot
sudo certbot renew --dry-run- The timer or cron job is gone — common after a server migration or OS upgrade.
- Validation fails — a redirect, firewall, CDN or
.htaccessrule blocks/.well-known/acme-challenge/, or DNS moved to a new provider. - No reload after renewal — add a deploy hook, for example
--deploy-hook "systemctl reload nginx". - A manual certificate nobody tracked — someone installed it a year ago and the reminder went to an old inbox.
Prevent it next time
Two things together: automated renewal, and an independent check of the certificate each site is serving that warns you well before the expiry date. Let's Encrypt no longer sends expiry emails, so that warning has to come from you. See how to check SSL certificate expiry and why certificates are getting shorter.
Frequently asked questions
Is it safe to click "Proceed anyway" on NET::ERR_CERT_DATE_INVALID?
Avoid it, and never enter passwords or payment details on such a page. An expired certificate still encrypts, but the browser can no longer confirm you are talking to the real site.
Why does the error appear on only one device?
Almost always because that device's date or time is wrong (common after a dead CMOS battery or a manual time change). Set the date and time automatically and reload.
I renewed the certificate but the error is still there. Why?
The server is still serving the old certificate. Reload or restart the web server, update the certificate on every server, CDN and load balancer in front of the site, and clear any cached certificate on the proxy.