How to Fix “NET::ERR_CERT_DATE_INVALID” in Google Chrome

The NET::ERR_CERT_DATE_INVALID error in Google Chrome indicates that the browser has blocked a connection because the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) certificate presented by the web server is either expired or not yet valid according to your operating system clock. Because web security relies on strict cryptographic time validation, Chrome refuses to establish an encrypted session whenever a timestamp mismatch occurs. Resolving this issue involves verifying local system time synchronisation, clearing corrupted local certificate caches, and updating operating system trust stores.

Understanding the Causes of NET::ERR_CERT_DATE_INVALID

Modern web security mandates that every digital certificate possesses an absolute validity window marked by “Not Before” and “Not After” timestamps. When Chrome evaluates a server certificate, it compares those boundary timestamps directly against the current time provided by your workstation or mobile device. If your system clock drifts by even a few minutes, Chrome flags the certificate as expired or premature.

The underlying causes generally fall into three distinct areas:

• Local Clock Discrepancies: An incorrect date, time zone, or failed Network Time Protocol (NTP) synchronisation will cause Chrome to reject valid certificates.
• Corrupted Operating System SSL State: Stale Intermediate Certificate Authority (CA) chains or cached revocations stored in the local certificate cache can prevent fresh validation.
• Outdated Root Certificates: Discontinued operating systems or devices that have missed security updates may lack the updated root CA certificates required to validate modern certificates.
• Genuine Server-Side Expiration: The website administrator may have failed to renew the domain’s certificate before its designated expiry date.

Component	Role in Validation	Common Failure State
System Time (RTC/NTP)	Provides the reference point for certificate start and end dates	CMOS battery failure or unsynchronised time server
CryptoAPI / SSL Cache	Caches validated chains and OCSP responses locally	Outdated certificate revocation lists or stale caches
Root Certificate Store	Anchors trust to recognised Certificate Authorities	Expired root authorities (e.g., legacy cross-signed roots)
Third-Party Antivirus	Inspects encrypted web traffic via local SSL proxying	Mismatched internal proxy certificate or broken certificate injection

Step 1: Synchronise the Operating System Date and Time

The primary reason users encounter NET::ERR_CERT_DATE_INVALID is an unsynchronised operating system clock. Even minor offsets can invalidate short-lived 90-day certificates issued by automated authorities like Let’s Encrypt. For a comprehensive walkthrough on fixing clock alerts, see our dedicated guide on fixing your clock is ahead or behind in Google Chrome.

Synchronising on Windows 11

1. Press Windows Key + I to open the Settings application.
2. Navigate to Time & language > Date & time.
3. Ensure that Set time automatically and Set time zone automatically are toggled On.
4. Under the Additional settings section, click Sync now. Wait for the confirmation tick to appear next to the button.

Synchronising on macOS

1. Click the Apple menu and select System Settings.
2. Select General in the sidebar, then click Date & Time.
3. Ensure the toggle for Set time and date automatically is enabled.
4. Verify that the designated server is set to time.apple.com.

Step 2: Clear the Operating System SSL State

Windows maintains an operating system-level SSL state cache that stores session tokens and intermediate certificate chains. If a website recently renewed its certificate, your computer might still attempt to validate the connection against an older, cached certificate that has expired.

1. Press Windows Key + R to launch the Run dialogue box.
2. Type inetcpl.cpl and press Enter to open Internet Properties.
3. Navigate to the Content tab.
4. Under the Certificates section, click the Clear SSL state button.
5. A confirmation prompt stating “The SSL cache was successfully cleared” will appear. Click OK.
6. Restart Google Chrome and attempt to reload the affected webpage.

Step 3: Clear Chrome Cache and Disable Conflicting Extensions

Corrupted local browser data or third-party extensions that intercept web traffic (such as VPN extensions or ad blockers) can interfere with SSL handshakes. Testing the connection in an isolated environment helps isolate the cause.

1. Open Google Chrome and press Ctrl + Shift + N (or Cmd + Shift + N on macOS) to launch an Incognito window.
2. Navigate to the URL displaying the error. If the page loads without warning, an installed extension or corrupted cache is responsible.
3. To clear the cache, press Ctrl + Shift + Delete.
4. Set the Time range to All time, tick Cookies and other site data and Cached images and files, then click Clear data.
5. If the issue persists in normal browsing, open chrome://extensions and disable all extensions temporarily to isolate any offending software.

Step 4: Check for Conflicting Antivirus SSL Scanning

Many commercial security packages incorporate HTTPS scanning or SSL inspection features. These utilities intercept encrypted network packets by inserting their own root certificate into the local store. If the security software’s internal certificate fails to renew or mishandles the target site’s cipher suite, Chrome immediately displays NET::ERR_CERT_DATE_INVALID.

1. Open your antivirus or endpoint security console (such as Avast, Bitdefender, or Kaspersky).
2. Locate the Web Shield, Network Protection, or Real-time Protection settings.
3. Look for an option labelled Enable HTTPS scanning, Scan encrypted connections, or Check SSL.
4. Temporarily disable this feature and reload Google Chrome. If the error disappears, reinstall the antivirus application or update its internal root certificates.

Step 5: Inspect the Remote Certificate in Chrome DevTools

If client-side adjustments fail to resolve the error, the website’s certificate may have genuinely expired. You can verify this directly within Chrome:

1. On the warning page, click the red Not secure indicator in the address bar.
2. Click Certificate is not valid to view the certificate details dialogue.
3. Review the Valid from and to dates listed in the General tab.
4. If the expiration date has passed, the issue resides entirely with the website administrator, who must regenerate and deploy a renewed certificate on their web server.