FixHub
Web & Browsers

"Your Connection Is Not Private" (NET::ERR_CERT_DATE_INVALID)? Check Your Clock First

Published June 10, 2026 · by The FixHub Team

Chrome (or Edge) blocks a site with “Your connection is not private” and a code like NET::ERR_CERT_DATE_INVALID or NET::ERR_CERT_AUTHORITY_INVALID.

The #1 cause people overlook: if it happens on every HTTPS site, it’s almost always your computer’s clock being wrong. TLS certificates are time-sensitive — a bad date makes valid certificates look “expired” or “not yet valid.” Fix the clock before anything else.

Fix 1: Correct the date, time, and time zone

  • Windows: right-click the taskbar clock → Adjust date and time → turn on Set time automatically and Set time zone automatically → Sync now.
  • A wrong year/timezone (common after a dead CMOS battery) instantly triggers NET::ERR_CERT_DATE_INVALID everywhere. Reboot and retest.

Fix 2: If it’s only one site

  • The site’s certificate may genuinely be expired or misconfigured — that’s the site owner’s problem, not yours. Don’t bypass the warning for a site you don’t trust.
  • Try it in Incognito (rules out a cached cert/extension).

Fix 3: Clear the SSL state and cache

  • Clear browsing data (cached images/files + cookies) in Chrome/Edge.
  • On Windows, clear the SSL cache: Internet Options (inetcpl.cpl) → Content → Clear SSL state.

Fix 4: Antivirus / firewall HTTPS scanning

Some AV (and corporate proxies) intercept HTTPS and present their own certificate, causing NET::ERR_CERT_AUTHORITY_INVALID. Temporarily disable the AV’s HTTPS/SSL scanning to test; on managed networks, the proxy’s root cert may need installing by IT.

Fix 5: Public Wi-Fi sign-in pages

On hotel/airport Wi-Fi, the captive portal can trigger this before you’ve logged in. Visit a plain http:// site to force the sign-in page, then retry.

FAQ

Is it safe to click “Proceed anyway”? Only for a site you trust where you understand the cause (e.g. your own dev server). For a bank/shop, don’t bypass it.

Every site broke at once. That’s the clock (Fix 1) or AV HTTPS scanning (Fix 4) — not the websites.

Sources: Google Chrome Help — Get help with common error messages in Chrome