"Your Connection Is Not Private": What It Means & How to Fix It

What the warning actually means

When a website loads over HTTPS, it presents a digital TLS certificate — a small file that proves the site is who it claims to be and lets your browser encrypt the connection. Your browser checks that certificate against a few rules: is it issued by a trusted authority, does it match the domain you're visiting, and is today's date inside its valid window?

If any check fails, the browser stops and shows "Your connection is not private" (Chrome/Edge), "This Connection Is Not Private" (Safari), or "This site can't provide a secure connection." It's important to read this calmly: the warning does not usually mean the site is malicious or trying to steal from you. In the large majority of cases it means something on your side — your clock, your network, or software on your device — broke the verification.

That's good news, because the things on your side are the things you can actually fix. Let's start with the cause behind most of these warnings.

The #1 cause: a wrong clock

Every certificate has a "valid from" and "valid until" date. Your browser compares those against your device's own clock. If your computer or phone thinks it's the wrong day — or even the wrong time zone by enough hours — a perfectly good certificate looks either expired or not yet valid, and you get the warning on almost every site at once.

This is incredibly common after travelling. You land in a new country, your laptop never re-synced the time, and suddenly the whole web is "not private." A dead CMOS battery on an older desktop causes the same thing — the clock resets to a date years in the past on every reboot.

The fix is to turn on automatic time sync so the device pulls the correct time from the internet:

• Windows 11/10: Settings → Time & language → Date & time → turn on Set time automatically and Set time zone automatically, then click Sync now.
• macOS: System Settings → General → Date & Time → turn on Set time and date automatically.
• iPhone/iPad: Settings → General → Date & Time → turn on Set Automatically.
• Android: Settings → System → Date & time → turn on Set time automatically.

After the clock corrects itself, fully close and reopen the browser, then reload the page. If the warning vanishes everywhere, that was it — you're done. If it only happens on one site, your clock is fine and the cause is elsewhere.

Other causes and their fixes

If your clock is correct and you still see the warning, work through these in order. They run from most to least common.

1. A captive portal you haven't logged into. Hotel, airport, and café Wi-Fi often makes you accept terms or enter a room number before it lets you online. Until you do, the network intercepts your traffic and the certificate check fails. Try visiting a plain http:// page (like http://neverssl.com) to force the login screen to appear. Our guide on hotel and café Wi-Fi that won't connect walks through this in detail.

2. Antivirus or a VPN scanning HTTPS. Some security suites (and some corporate VPNs) inspect encrypted traffic by inserting their own certificate in the middle. If that feature glitches or isn't trusted properly, every site throws the warning. Temporarily disable "HTTPS scanning," "SSL/TLS inspection," or "secure connection scanning" in your antivirus, or pause the VPN, and reload. If the page loads, you've found the culprit — re-enable it and update the software.

3. Corrupted browser cache. Old, broken cached certificate data can keep the error alive even after the real problem is gone. Clear your cached images and files (Ctrl+Shift+Delete on Windows, Cmd+Shift+Delete on Mac), restart the browser, and try again.

4. Out-of-date browser or operating system. Certificate authorities and root trust lists change over time. A browser or OS that hasn't been updated in a year or two may no longer trust certificates that everyone else accepts. Install pending browser and system updates.

5. The wrong DNS. A misconfigured or hijacked DNS server can send you to a server whose certificate doesn't match the domain. Switching to a reputable resolver such as Cloudflare (1.1.1.1) or Google (8.8.8.8) often clears it.

6. The certificate really has expired. Occasionally it genuinely is the site — a small operator let their certificate lapse. If a single, otherwise-trustworthy site shows only a date error and everything else on your device works, this is likely, and there's nothing you can safely do but wait for them to renew.

7. A proxy or man-in-the-middle on untrusted Wi-Fi. On public networks, the warning can mean someone is genuinely intercepting your traffic. This is the one cause that is a real security risk — see the "when to proceed" section before clicking anything.

Decode the error code

Chrome and Edge print a specific code in grey under the warning. That code tells you exactly which check failed, which narrows the cause immediately.

Error code	What failed	Most likely cause & fix
NET::ERR_CERT_DATE_INVALID	The date is outside the certificate's valid window	Your device clock is wrong (or the site's cert truly expired). Fix automatic time first.
NET::ERR_CERT_AUTHORITY_INVALID	The certificate isn't from a trusted authority	Antivirus/VPN HTTPS scanning, a captive portal, or a possible man-in-the-middle. Disable the scanner or log into the portal.
NET::ERR_CERT_COMMON_NAME_INVALID	The certificate doesn't match the domain	A redirect, DNS issue, or visiting via the wrong address (e.g. an IP). Check the URL and DNS.
ERR_CERT_REVOKED / ERR_SSL_VERSION_OR_CIPHER_MISMATCH	The cert was pulled, or browser and server can't agree on encryption	Update your browser and OS; the site may also be misconfigured.

Safari is less specific — it usually just says the connection isn't private and offers details — but the underlying causes map to the same list.

When it's safe to click through — and when it's not

Every warning page offers a way past it: Advanced → Proceed to (site) (unsafe) in Chrome/Edge, or Show Details → visit this website in Safari. Sometimes that's reasonable; often it is a serious mistake. Use this rule.

It can be reasonable to proceed only when all of these are true: you're on a network you trust (home or office, not public Wi-Fi), the error is clearly ERR_CERT_DATE_INVALID, you've confirmed it's the site's certificate that lapsed (not your clock), and the page holds no sensitive information — no login, no payment, no personal data. A static blog or reference page run by a hobbyist is a typical example.

Never click through when you're on public, hotel, or café Wi-Fi; when the site involves banking, email, shopping, or any login or password; or when the code is ERR_CERT_AUTHORITY_INVALID on a site that's normally fine. In those situations the warning may be the only sign that someone is intercepting your connection, and bypassing it hands them your data. When in doubt, don't proceed — fix the underlying cause instead.

Fix it in Chrome, Edge & Safari

Here's the quickest end-to-end sequence per browser once you've ruled in your clock.

Chrome & Edge (Windows, Mac, Android):

1. Confirm the date/time is correct and auto-synced (steps above).
2. Reload the page. If it's a captive portal, log in first.
3. Open an Incognito/InPrivate window and try the site — this bypasses cache and most extensions.
4. If Incognito works, clear browsing data (Ctrl+Shift+Delete) and disable suspect extensions or your antivirus's HTTPS scanning.
5. Update the browser (Menu → Help → About) and restart.

Safari (Mac & iPhone):

1. Set Date & Time to automatic.
2. On Mac, clear history via Safari → Clear History, or use a Private window to test.
3. Pause any VPN or content-blocker and reload.
4. Install pending macOS/iOS updates, since Safari's trust store ships with the system.

If you've worked through your clock, the cache, your antivirus or VPN, and updates and the warning still appears on multiple sites, the problem is almost always in the network layer — DNS, a proxy, or a router setting — and that's worth a closer look.

Our team handles Wi-Fi and network problems and security concerns remotely, worldwide, same day — flat $149.99 USD with No Fix, No Fee.