When Chrome on Windows throws “Your connection is not private” (or an SSL/certificate warning), it’s Chrome telling you the website’s identity can’t be verified for this connection. Sometimes that’s a real risk. Often it’s a local problem: time, Wi‑Fi sign-in, antivirus scanning, or a network device handing out the wrong certificate.

Cracked padlock symbolizing a broken secure connection

Here’s the “fastest to deepest” ladder: start at step 1 and stop as soon as it’s fixed.

Quick safety note: don’t click through to “Proceed” on banking, email, work logins, or anything sensitive.

1. Confirm it’s not just one site (and note the exact code)

First, figure out whether this is a site-specific problem or a connection/device problem.

  • Try 2–3 well-known HTTPS sites (for example: a search engine, a major news site, and a software vendor).
  • If only one site fails, the site may be misconfigured or temporarily broken.
  • If many sites fail, it’s almost always your device, network, or security software.
  • On the warning page, look for the error code. Common ones: NET::ERR_CERT_DATE_INVALID (time issue), NET::ERR_CERT_AUTHORITY_INVALID (untrusted issuer), NET::ERR_CERT_COMMON_NAME_INVALID (name mismatch).

If the warning appears on multiple sites, move to step 2.

2. Fix Windows date/time/time zone (most common cause)

Certificates are only valid within specific dates. If your clock is wrong (even by hours), Chrome can’t validate them.

  • Open Windows Settings → Time & language → Date & time.
  • Turn on Set time automatically and Set time zone automatically (or pick the correct time zone manually).
  • Click Sync now if it’s available.
  • Close and reopen Chrome (or restart the PC if it was very wrong).

Analog clock representing incorrect system time causing SSL errors

If your time keeps drifting, that can point to a failing CMOS battery (older desktops/laptops) or an NTP/network policy issue.

3. Check for captive portal / “sign in to Wi‑Fi” interception

On hotel, airport, school, hospital, and some office networks, you must accept terms or sign in. Until you do, the network may intercept HTTPS in ways that trigger SSL warnings.

  • Disconnect and reconnect to Wi‑Fi.
  • Open a site that often triggers captive portals (for example, try visiting http://neverssl.com).
  • If a Wi‑Fi login/terms page appears, complete it, then reload your original site.
  • If you’re on a managed network, ask whether HTTPS inspection or filtering is enabled.

If this only happens on one Wi‑Fi network but not on your phone hotspot, that’s a strong clue the network is involved.

4. Temporarily disable VPN/proxy (and remove leftover proxy settings)

A VPN or proxy can present different certificates, route you to a filtering service, or break certificate checks when it’s misconfigured.

  • Turn off any VPN app you use (work VPN, consumer VPN, security suite VPN).
  • Windows Settings → Network & internet → Proxy → ensure Use a proxy server is off (unless you intentionally use one).
  • If you’re in a workplace with required proxy, don’t remove it permanently—just test off-network (like a hotspot) to compare.

Shield metaphor for antivirus HTTPS scanning and certificate trust

If turning off the VPN immediately fixes it, the fix is usually updating the VPN app, switching protocol/region, or reinstalling it cleanly.

5. Antivirus “HTTPS scanning” and installed root certificates (common on Windows)

Many antivirus and “web protection” tools inspect encrypted traffic by installing their own trusted root certificate, then re-signing websites on the fly. If that component breaks (after an update, expired certificate, or corrupted store), Chrome may show certificate authority errors.

  • In your antivirus, look for settings like HTTPS scanning, encrypted connections scanning, or web shield.
  • Temporarily disable that one feature (not necessarily the whole antivirus) and test again.
  • If it fixes the problem, re-enable it and then update the antivirus, or keep HTTPS scanning off if your environment allows it.
  • If you recently installed a “security” app, parental control, ad blocker with system filtering, or corporate monitoring tool, test by uninstalling it (not just disabling) and rebooting.

On managed work/school PCs, do not remove security agents—contact IT. They may need to refresh certificates or policies.

6. Reset the trust chain: update Windows, clear SSL state, and check your DNS/router

If you’ve ruled out time, captive portal, VPN/proxy, and antivirus inspection, treat it like a deeper trust-chain or network integrity problem.

  • Update Windows: Settings → Windows Update → install pending updates (root certificates and crypto components are updated via Windows).
  • Clear SSL state: Control Panel → Internet Options → Content tab → Clear SSL state, then restart Chrome.
  • Restart network gear: power-cycle modem/router (unplug 30 seconds).
  • Change DNS temporarily: set DNS to a known public resolver (for example 1.1.1.1 or 8.8.8.8) to test whether DNS hijacking is involved.
  • Test another network: phone hotspot is ideal. If hotspot works but home Wi‑Fi doesn’t, focus on router, DNS, or ISP-level filtering.

If the warning mentions a certificate from an unexpected company/organization, or it happens only on one network, assume interception until proven otherwise.

Final thoughts

SSL warnings are worth taking seriously, but the cause is often boring: incorrect time, a Wi‑Fi sign-in page, or security software doing HTTPS inspection.

If you’re on a work/school network or device and multiple sites are affected, the quickest safe path is usually to collect the exact error code and contact IT rather than clicking through.