Tag: Chrome error fix

How to Fix the “Your Connection Is Not Private” Error in Chrome

Seeing the “Your connection is not private” error in Chrome? Don’t panic — these 8 quick fixes clear the SSL error in minutes, no tech skills needed.

Introduction

You click a link and Chrome stops you cold: a big red warning reading “Your connection is not private.” Below it sits an error code like NET::ERR_CERT_DATE_INVALID. Your first thought might be: am I being hacked?

Almost certainly not. This error means Chrome couldn’t verify the security certificate for the website you’re trying to visit — and in the vast majority of cases, the fix lives on your own device and takes under two minutes. This guide walks you through eight proven fixes, starting with the most common cause.

Quick Answer

The “Your connection is not private” error in Chrome means Chrome can’t verify the site’s SSL certificate. The fastest fix: check that your device’s date and time are correct — a wrong clock is the most common trigger. If that doesn’t help, clear Chrome’s cache, update Chrome, or open an incognito window to pinpoint the cause.

What Does “Your Connection Is Not Private” Actually Mean?

SSL/TLS (the technology behind the padlock icon in your address bar) encrypts data between your browser and a website. Every secure site carries an SSL certificate — a digital ID proving the site is who it claims to be. Chrome checks this certificate on every connection. When something looks wrong, it blocks the page rather than quietly letting you through.

The error code beneath the main message tells you exactly what failed:

Error Code What It Means
NET::ERR_CERT_DATE_INVALID Certificate expired, or your device clock is wrong
NET::ERR_CERT_AUTHORITY_INVALID Certificate not trusted by Chrome
NET::ERR_CERT_COMMON_NAME_INVALID Certificate doesn’t match the website’s domain

8 Fixes for “Your Connection Is Not Private” in Chrome

Fix 1: Check Your Date and Time (Start Here)

A wrong device clock is the number one cause of this error. If your PC thinks it’s the wrong year, Chrome can’t check whether a certificate is still valid and blocks the connection immediately.

  1. Right-click the clock in your Windows taskbar and choose Adjust date and time.
  2. Turn on Set time automatically and Set time zone automatically.
  3. Click Sync now if that option appears.
  4. Reload the page in Chrome.

Pro tip: If your clock keeps resetting after syncing, the small CMOS battery on your motherboard may be dead. A local repair shop can replace it cheaply — usually just a few dollars.

Troubleshooting tip: If your date and time are already correct, skip straight to Fix 2 — the cause is something else.

Fix 2: Clear Chrome’s Cache and Cookies

Stale cached data can make Chrome check an outdated certificate snapshot instead of the live one. Clearing it forces Chrome to start fresh.

  1. Press Ctrl + Shift + Delete (Mac: Cmd + Shift + Delete) inside Chrome.
  2. Set the time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Clear data, then reload the page.

Fix 3: Update Google Chrome

An outdated Chrome build may not recognise newer certificate types or security protocols. Updating takes under a minute and often solves the problem immediately.

  1. Click the three-dot menu (⋮) in Chrome’s top-right corner.
  2. Go to Help > About Google Chrome.
  3. Chrome checks for and installs any available update automatically.
  4. Click Relaunch, then try the page again.

Fix 4: Try Incognito Mode

Incognito mode runs Chrome without any extensions. If the page loads fine in incognito but not in your normal window, a browser extension — often an antivirus add-on or ad blocker — is the culprit.

  1. Press Ctrl + Shift + N (Mac: Cmd + Shift + N) to open incognito.
  2. Visit the same website.
  3. If it loads without the error, go to chrome://extensions in your normal window and disable extensions one by one to find the problematic one.

Fix 5: Disable Your Antivirus HTTPS Scanning

Many antivirus programs scan encrypted HTTPS traffic by acting as a middleman between Chrome and the website. This well-meaning feature can interfere with certificate verification.

  1. Open your antivirus software’s settings.
  2. Look for an option called HTTPS scanning, SSL inspection, or Web Shield.
  3. Turn it off temporarily, then reload the page.
  4. If the error clears, add a trusted-site exception in your antivirus settings rather than leaving HTTPS scanning off permanently.

Troubleshooting tip: The feature name varies by antivirus brand. If you can’t find it, search your vendor’s support site for “HTTPS scanning” plus your product name.

Fix 6: Clear the SSL State in Windows

Windows keeps its own SSL certificate cache separate from Chrome. Clearing it forces a completely fresh certificate check the next time you visit the site.

  1. Open Control Panel (search for it in the Start menu).
  2. Click Internet Options.
  3. Select the Content tab.
  4. Click Clear SSL State, then click OK.
  5. Reload Chrome and try the page.

Fix 7: Disconnect Your VPN or Proxy

VPNs and proxies route your traffic through a different server, which can interfere with SSL certificate checks — especially on public Wi-Fi. Turn off your VPN, reload the page, and see if the error disappears. If it does, try updating your VPN app or contact your VPN provider’s support team. Public Wi-Fi can also cause connection problems more broadly — see our guide on fixing slow internet on Windows 11 for related troubleshooting.

Fix 8: Update Windows

Windows delivers root certificate updates through Windows Update. If your system hasn’t updated in months, it may no longer trust certificates from newer certificate authorities — causing this error on perfectly safe websites. Go to Settings > Windows Update, click Check for updates, install everything available, and restart your PC. For help if Windows Update itself isn’t working, see our guide: How to Fix Windows Update Not Working on Windows 11.

When the Error Is the Website’s Fault

Sometimes no fix on your end will work — because the problem is on the website itself. An expired or misconfigured SSL certificate on the server triggers the exact same warning, and it will show up on multiple devices and browsers.

If you can confirm the site loads fine on a completely different device and network, the site owner needs to renew their certificate. In the meantime, do not click “Proceed anyway” on any site where you enter a password, payment details, or personal information.

Common Mistakes to Avoid

  • Clicking “Proceed anyway” on sensitive sites. If this error appears on your bank, email, or any login page, stop — do not bypass the warning. The risk of real credential theft is highest here.
  • Assuming it’s always a hacker. The vast majority of cases are a clock problem, stale cache, or antivirus conflict — not an active attack. Diagnose first, panic later.
  • Ignoring it on a site you own. If this appears on your own website, your SSL certificate has likely expired. Log into your hosting control panel and renew it immediately — visitors are being turned away.
  • Leaving HTTPS scanning permanently disabled. It’s a real security layer. Switch it back on once you’ve confirmed it was the cause, and use a per-site exception instead.
  • Skipping the extension check. Browser extensions — especially security and privacy add-ons — are a surprisingly frequent trigger. The two-second incognito test rules them in or out instantly.
  • Falling behind on Windows Updates. Root certificate updates ship inside Windows Update. A long-unpatched system can start rejecting perfectly valid newer certificates without warning.

Frequently Asked Questions

Is “Your Connection Is Not Private” the same as being hacked?

Almost never. The error most often comes from a wrong system clock, stale cache, or an extension conflict. Genuine attacks that trigger this error are rare and mostly target users on unsecured public Wi-Fi networks.

Can I click “Proceed anyway” to get to the site?

Only on sites you fully trust and where you’re not entering any personal data. For anything involving login credentials, payments, or sensitive information, do not bypass the warning.

Why does this error only appear in Chrome and not Firefox or Edge?

Each browser maintains its own certificate cache and runs different extensions. If another browser loads the page without error, start by clearing Chrome’s cache and testing in incognito mode to rule out an extension.

Why does this happen on my laptop but not my phone?

Your laptop’s clock, antivirus settings, or installed Chrome extensions are the most likely culprits. Work through Fix 1 and Fix 5 specifically on the affected device.

What if none of the eight fixes work?

If the error persists across multiple sites after trying everything, scan your PC for malware — some malicious software intercepts SSL traffic and can cause this error. Run a free scan with Windows Security (built into Windows) or Malwarebytes.

Conclusion

The “Your connection is not private” error looks alarming but is almost always fixable in minutes. Start with your date and time, clear Chrome’s cache, and test in incognito — those three steps alone clear the vast majority of cases. Work down the list from there and you’ll be back online fast.

Still having trouble with Chrome? Our guide on Google Chrome using too much memory covers more browser fixes worth bookmarking.