"Your connection is not private" — what it means and how to fix it

Every secure site carries a certificate proving its identity, with an expiry date. This warning (codes like NET::ERR_CERT_DATE_INVALID or NET::ERR_CERT_COMMON_NAME_INVALID) means a check on that certificate failed. The surprise: the most common cause is not the site — it’s a wrong clock on your device, which makes every valid certificate look expired or not-yet-valid.

The fix, in order

  1. Check your device’s date and time first. Set it to automatic (Windows: Settings → Time & language → Date & time → “Set time automatically”; phones: the equivalent under Date & time). A clock off by days breaks certificates everywhere.
  2. Reload the page — once, after fixing the clock. Certificates are checked fresh on each load.
  3. If you’re on hotel, airport or café Wi-Fi, open a plain http site (for example http://neverssl.com) to trigger the sign-in page. Until you sign in, the network intercepts secure pages and every certificate looks wrong.
  4. Try a private/incognito window. If the warning disappears, an extension was interfering.
  5. Update the browser and the operating system. Very old systems don’t know newer certificate authorities and fail checks on healthy sites.
Do not click through this warning on banking, email, shopping, or anything asking for a password. Clicking “Advanced → Proceed” ignores the one check that proves you’re really talking to that site. If the warning appears on a site you use daily and your clock is right, contact the site through a different channel — its certificate may genuinely be broken or, rarely, something is intercepting your connection.

If the site is yours

Check that the certificate hasn’t expired (most hosts renew automatically — a failed renewal is the usual story), that it covers every name you serve (root and www), and that visitors aren’t being sent between http and https versions mid-journey. A certificate for the wrong name triggers ERR_CERT_COMMON_NAME_INVALID even when it’s valid.

If it still happens

If exactly one device in the house warns on every secure site, its clock, its antivirus web-scanning feature, or its system certificate store is at fault — test with the antivirus shield paused, and run the system’s own updates.

Common questions

Why did this suddenly start on a site I use every day? Either their certificate expired (their problem, usually fixed within hours) or your device’s clock drifted or was reset (your problem, fixed in step 1). The clock check takes ten seconds, so do it first.

Is “your connection is not private” a virus warning? No. It’s the browser reporting a failed identity check on the connection. It can occasionally be caused by malware intercepting traffic, which is one more reason not to click through it on sensitive sites.

Related errors

DNS_PROBE_FINISHED_NXDOMAIN · ERR_CONNECTION_REFUSED · Fake Apple security warning (scam)