What NET::ERR_CERT_DATE_INVALID means
Chrome shows NET::ERR_CERT_DATE_INVALID under "Your connection is not private" when the site's SSL certificate is not valid for the date your device thinks it is. Almost always one of two things causes that: the certificate really has expired (or is not valid yet), or your device clock is wrong. Chrome's own help says an inaccurate date or time on your device can trigger it and tells you to correct the clock.
The fix depends on which one you have, so check that first. If many HTTPS sites fail on one device, suspect your clock. If one site fails on every device, the certificate has expired and only the site owner can fix it.
Quick-fix checklist
- Look at your device's date, time and time zone. If any is wrong, turn on automatic date and time and reload the page.
- Open the same site on another device or on mobile data. If it fails everywhere, the certificate is the problem, not your device.
- Click Not secure in the address bar, open the certificate details and read the validity dates (issued on and expires on).
- If you own the site, check the live certificate from a terminal:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -dates - Owners on a VPS: run
sudo certbot renew --dry-run, then reload the web server. Owners on cPanel: check SSL/TLS Status for AutoSSL errors.
How to tell an expired certificate from a wrong clock
Every certificate carries two dates, notBefore and notAfter. Your browser compares them with the device clock. Compare them yourself:
| What you see | Likely cause | Who fixes it |
|---|---|---|
| Chrome says "Your clock is behind" or "Your clock is ahead" | Device date or time is wrong | Visitor |
| Many unrelated HTTPS sites fail on one device | Device clock, an outdated root certificate store, or antivirus or proxy software that scans HTTPS | Visitor |
| One site fails on every device and network | The site's certificate has expired | Site owner |
| Expires-on date is in the past and your clock is right | Expired certificate | Site owner |
| Issued-on date is later than your device's date | Device clock is behind | Visitor |
On the visitor side, the usual culprits are a clock reset by a flat motherboard battery, a phone restored with the wrong time, or a manually set time zone.
Visitor side: fix your device
Set the clock automatically
- Windows 11: Settings > Time & language > Date & time. Turn on Set time automatically and Set time zone automatically, then click Sync now.
- macOS: System Settings > General > Date & Time. Turn on automatic date and time.
- Android: Settings > System > Date & time. Turn on automatic time and time zone (menu names vary by maker).
- iPhone: Settings > General > Date & Time. Turn on Set Automatically.
Reload the page after the clock changes. If a desktop loses the time after every restart, replace the motherboard battery.
Update the operating system
Browsers trust certificates through root certificates stored on the device. Let's Encrypt lists the minimum versions that trust its ISRG Root X1 root, including Android 7.1.1, iOS 10 and macOS 10.12.1, and notes that Windows needs automatic root certificate updates turned on. Older devices may reject current certificates even with the right time. Install system updates and use a current browser.
Do not click through the warning on a site where you log in or pay. Chrome's help also warns that installing a certificate on your own is usually a security risk.
Site owner side: renew the certificate
Confirm what the server is sending
Check the certificate your server actually serves, not just the file on disk:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
| openssl x509 -noout -dates -subject -issuer
notAfter is the expiry date. If it is in the past, renew. If the file on disk is newer than what is served, the renewal worked but the web server was never reloaded.
Let's Encrypt with Certbot
List the certificates Certbot manages with their expiry dates, then test renewal without issuing anything:
sudo certbot certificates
sudo certbot renew --dry-run
If the dry run fails, the message names the problem: usually port 80 blocked for the HTTP-01 challenge, DNS no longer pointing at this server, or a changed web root. Fix that, then run sudo certbot renew.
Most Certbot installs come with a scheduled task that runs certbot renew on its own. Check it exists:
systemctl list-timers --all | grep -i certbot
grep -r certbot /etc/cron.d /etc/crontab 2>/dev/null
Depending on how Certbot was installed, the timer is usually certbot.timer or snap.certbot.renew.timer. If you find neither, add a cron entry that runs twice a day, as Certbot's documentation suggests. This line includes the root user field, so put it in a file such as /etc/cron.d/certbot or in /etc/crontab, not in crontab -e. Our guide to cron jobs explains the syntax:
17 3,15 * * * root certbot renew -q
Pick your own minute rather than 17 so that renewals from many servers do not all arrive at once; Let's Encrypt asks clients to renew at random times.
Reload the web server after renewal
Nginx and Apache read certificate files when they start or reload, so a renewed file is ignored until then. Add a deploy hook, which Certbot runs only after a certificate is successfully issued or renewed. A --dry-run skips deploy hooks unless you add --run-deploy-hooks. Any executable in /etc/letsencrypt/renewal-hooks/deploy/ is run as one:
sudo tee /etc/letsencrypt/renewal-hooks/deploy/reload-web.sh >/dev/null <<'EOF'
#!/bin/sh
systemctl reload nginx
EOF
sudo chmod +x /etc/letsencrypt/renewal-hooks/deploy/reload-web.sh
For Apache, use systemctl reload apache2 on Ubuntu and Debian or systemctl reload httpd on AlmaLinux. Reload any other service that uses the certificate, such as a mail server, in the same script.
Serve the full chain
Point the server at fullchain.pem, not cert.pem. Certbot's documentation says fullchain.pem holds the server certificate followed by the intermediates, while cert.pem holds the server certificate alone. Also check the config points at the files under /etc/letsencrypt/live/: a copy made by hand elsewhere never gets renewed. In Nginx:
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
Then run openssl s_client -connect example.com:443 -servername example.com -showcerts and look for Verify return code: 0 (ok) near the end of the output.
cPanel and AutoSSL
In cPanel, open SSL/TLS Status. cPanel's documentation says this page shows when AutoSSL last ran for each domain and any AutoSSL errors, and lets you filter for expired or expiring certificates. The common errors are a domain that does not resolve to the server and a CAA record that does not allow the issuer.
With WHM access, go to Manage AutoSSL. The Logs tab holds the AutoSSL logs, Run AutoSSL for all users starts a run straight away, and the Manage Users tab lets you check a single account. On shared hosting you do not have WHM, so send your host the domain and the error shown in SSL/TLS Status.
How long Let's Encrypt certificates last
Let's Encrypt's FAQ says its default certificates are valid for 90 days, with optional six-day certificates. It has announced shorter lifetimes: an opt-in 45-day profile from 13 May 2026, then the default profile moving to 64 days on 10 February 2027 and to 45 days on 16 February 2028. Each change applies to certificates issued after that date, so you get the shorter lifetime at your next renewal. Let's Encrypt warns that renewing on a fixed 60-day interval will not be enough, discourages manual renewal and recommends ACME Renewal Information (ARI) where your client supports it.
Certbot 4.0 and later treats a certificate as due for renewal when less than a third of its lifetime remains (half for certificates shorter than 10 days), so it adapts to shorter certificates. Older versions used a fixed 30 days. From Certbot 4.1, certbot renew also checks ARI and may renew earlier when Let's Encrypt suggests it. Check yours with certbot --version.
Monitor expiry so it does not happen again
- Run the
openssldate check above from a daily cron job on a different machine and alert when fewer than 14 days remain. - Add
-checkend 1209600to theopenssl x509command; it exits with a non-zero status if the certificate expires within 14 days, which is easy to script. - Use an external monitor that checks certificate expiry, so a broken server cannot hide its own failure.
- Recheck the renewal timer and deploy hook after every OS upgrade or move to a new host.
SSL expiry on Bigdomainhost
On Web & cPanel hosting and WordPress hosting, Let's Encrypt certificates are issued automatically for every domain and subdomain and renew without any action from you. Renewal happens 30 days before expiry, and if it fails it retries daily and we are alerted. You can check the status under cPanel > SSL/TLS Status. A certificate can be issued only while the domain resolves to our server, and a CAA record that omits the issuer blocks it, so check your DNS at your own registrar first. The SSL documentation covers this.
On a KVM VPS you have full root access, so you run Certbot and the commands above yourself. The firewall's default policy denies inbound traffic except SSH on port 22, so add rules for ports 80 and 443 in the panel or HTTP-01 renewals will fail. For help, call +91 75994 50220 (answered by the NOC in IST hours), WhatsApp the same number any time, or email support@bigdomainhost.com.
Sources (checked )
- Google Chrome Help: Get help with common error messages in Chrome
- Let's Encrypt: FAQ
- Let's Encrypt: Decreasing Certificate Lifetimes to 45 Days
- Let's Encrypt: Certificate Compatibility
- Certbot: User Guide
- cPanel Docs: Manage AutoSSL