How to Fix ERR_CERT_DATE_INVALID (Your Connection Is Not Private)
What ERR_CERT_DATE_INVALID means
Every HTTPS certificate carries two dates: a "valid from" date and a "valid to" date. When you visit a site, Chrome compares today's date against that window. If today falls outside it, Chrome stops with ERR_CERT_DATE_INVALID and the familiar "Your connection is not private" warning — even though the connection itself might have worked fine yesterday.
Two very different problems produce this identical message, and telling them apart is the key to fixing it. In most cases your own device is at fault: its clock is wrong (often after a CMOS battery dies, a dual-boot timezone mix-up, or automatic time being switched off), which makes a perfectly good certificate look expired. In the remaining cases the website itself is at fault: the certificate actually expired because the owner forgot to renew it, or the site was migrated to a new server and an old certificate is still being served. The good news is that both causes are easy to diagnose — the clock check takes thirty seconds, and the certificate check takes another minute.
Common causes
- Wrong date or time on your device: the single most common cause — a skewed clock makes valid certificates look expired.
- The site's certificate has genuinely expired: the owner missed a renewal, often on free Let's Encrypt certificates that need renewing every 90 days.
- Certificate not yet valid: the server is presenting a certificate whose "valid from" date is in the future, or your clock is set ahead of the real time.
- Outdated browser or operating system: old devices no longer trust newer root certificates, so perfectly valid certificates fail validation.
- Intercepted traffic: antivirus HTTPS scanning, corporate proxies, or captive Wi-Fi portals substitute their own certificates and trigger date or trust errors.
How to fix ERR_CERT_DATE_INVALID — step by step
Work through these fixes in order. The clock check (step 1) resolves the majority of cases.
- Sync your device's date and time. An incorrect clock is the most common cause of this error, because Chrome checks the current date against the certificate's validity window. On Windows, open Settings, go to Time & language, then Date & time, and turn on Set time automatically and Set time zone automatically, then click Sync now. On a Mac, open System Settings, go to General, then Date & Time, and turn on Set time and date automatically. On Android, open Settings, go to System, then Date & time, and enable Automatic date & time. On an iPhone, open Settings, go to General, then Date & Time, and turn on Set Automatically. Reload the page after syncing — this fixes the majority of ERR_CERT_DATE_INVALID cases.
- Update Chrome and your operating system. Outdated browsers and operating systems can misread modern certificates, especially ones issued with newer root certificates that old systems do not trust. On desktop, open Chrome, click the three-dot menu, go to Help, then About Google Chrome, and let it update. Then install your operating system updates: on Windows, open Settings, go to Windows Update, and click Check for updates; on a Mac, open System Settings, go to General, then Software Update. Very old phones and computers that no longer receive updates may fail certificate checks permanently, because their trusted root stores can never be refreshed.
- Check the certificate's expiry date. Before changing anything else, find out whose fault the error actually is. If you can open the page details, look for the Not secure or certificate icon in the address bar and view the certificate's Valid from and Valid to dates. If today's date falls outside that window, the certificate is expired or not yet valid, and the problem is on the website's side — no change on your device will fix it. If the certificate is valid for today's date, the problem is on your device and the clock, updates, or cached data are the likely culprits. You can also paste the domain into a free online SSL checker to confirm the expiry date from an independent source.
- Clear the SSL state and browsing data. A corrupted cached certificate can keep this error alive long after the real problem is gone. On Windows, search the Start menu for Internet Options, open it, go to the Content tab, and click Clear SSL state. Then in Chrome, press Ctrl + Shift + Delete (Cmd + Shift + Delete on a Mac), set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Close Chrome completely and reopen it so the next visit starts a fresh certificate check instead of reusing the broken cached state.
- Disable extensions and pause antivirus HTTPS scanning. Some extensions and antivirus tools sit between Chrome and the site and substitute their own certificates, which triggers date and trust errors. Type chrome://extensions in the address bar and toggle off every extension, then reload the page; re-enable them one by one to find the culprit. Next, check your antivirus: programs like Avast, AVG, Kaspersky, and ESET scan encrypted traffic with their own certificates. Open your antivirus settings and turn off HTTPS scanning temporarily as a test — if the page loads, add the site to the antivirus exclusion list or turn the HTTPS scanning feature off, then restore your protection.
- If you own the site: renew and reinstall the certificate. When visitors see this error, your certificate has expired or is not yet valid, and the fix is entirely yours. Log in to your hosting panel or certificate provider and renew the certificate — with Let's Encrypt, renewals are free and can be automated. After renewal, install the new certificate including the full chain of intermediate certificates, then check that your server is serving the new one by reloading the domain in an SSL checker. Also make sure auto-renewal is enabled and that renewal reminder emails go to an address someone actually reads, so this does not happen again in ninety days.
Did this fix it? Quick checklist
- Your device clock is synced to automatic date and time
- Chrome and your operating system are fully updated
- The site's certificate is genuinely valid for today's date
- The page loads with extensions off and antivirus HTTPS scanning paused
If the error appears on one website only while every other site loads fine, your device is almost certainly not the problem — that site's certificate is expired, and only the site owner can renew it. If the error appears on every HTTPS site, your device clock or operating system is the cause: get the clock syncing automatically and install the pending updates, and the errors will clear together. If nothing here helps, try a different network — some public Wi-Fi portals and corporate proxies inject certificates that fail date checks, and the error disappears the moment you leave that network.
Frequently asked questions
What does ERR_CERT_DATE_INVALID mean?
It means Chrome checked the website's SSL certificate and found the current date outside the certificate's validity period. Every certificate has a Valid from and Valid to date. The most common reason is that the certificate has expired because the site owner did not renew it, but an incorrect clock on your own device can make a perfectly valid certificate look expired too.
Is it safe to click Proceed and bypass this error?
Usually not. This error means Chrome cannot verify that the site is who it claims to be, and an expired or invalid certificate is one of the classic signs of an attack intercepting your connection. Only proceed if you fully trust the site and understand the risk — and never enter passwords, payment details, or other sensitive information on a page with certificate errors.
Why does this error only show on one website?
That is actually a helpful clue. If every other site loads fine, your clock and browser are almost certainly correct, and the single site's certificate is genuinely expired or misconfigured. The problem belongs to the site owner, not to your device — no amount of clearing caches on your side will fix it, and the only real resolution is for them to renew their certificate.
How do I check when a website's certificate expires?
Click the padlock or Not secure icon in Chrome's address bar and open the certificate details, where you will see the Valid from and Valid to dates. Alternatively, run the domain through a free online SSL checker such as the Qualys SSL Labs test, which shows the expiry date, the full certificate chain, and whether the server is sending intermediate certificates correctly.