← Back to home

How to Fix "Your Connection is Not Private" Error

You're trying to open a website and suddenly see a big red warning: "Your connection is not private" with the error code NET::ERR_CERT_AUTHORITY_INVALID or NET::ERR_CERT_DATE_INVALID. Your browser is blocking access and you don't know why. This guide covers 8 proven fixes that work on Chrome, Firefox, and Edge on Windows 10 and Windows 11.

⚠️ Important: If you see this error on a banking or shopping site you've used before, do NOT click "Advanced" and proceed. The warning could indicate a real attack. First try the fixes below.

What Causes "Your Connection is Not Private"?

This error means your browser cannot verify the SSL/TLS certificate of the website. The most common causes are:

Fix 1: Check Your Computer's Date and Time

This is the most common cause and takes 30 seconds to fix. SSL certificates have expiry dates — if your system clock is wrong, certificates appear invalid.

  1. Right-click the clock in the bottom-right corner of your taskbar
  2. Select "Adjust date/time"
  3. Turn on "Set time automatically" and "Set time zone automatically"
  4. Click "Sync now" under "Synchronize your clock"
  5. Reload the website

💡 Quick check: If the year on your PC is 2020 or earlier, this is definitely your problem. Sync the clock and the error will disappear immediately.

Fix 2: Clear Browser Cache and Cookies

Old cached certificate data can trigger this error even when the website's certificate is valid.

In Google Chrome:

  1. Press Ctrl + Shift + Delete
  2. Set time range to "All time"
  3. Check "Cached images and files" and "Cookies and other site data"
  4. Click "Clear data"
  5. Restart Chrome and try again

In Mozilla Firefox:

  1. Press Ctrl + Shift + Delete
  2. Select "Everything" from the time range dropdown
  3. Check all boxes and click "Clear Now"

In Microsoft Edge:

  1. Press Ctrl + Shift + Delete
  2. Set time range to "All time"
  3. Select cached data and cookies, then click "Clear now"

Fix 3: Disable Antivirus SSL Scanning

Many antivirus programs (Avast, AVG, Kaspersky, ESET) scan HTTPS traffic by replacing SSL certificates with their own. This can cause the "connection not private" error.

To test if your antivirus is the cause:

  1. Temporarily disable your antivirus
  2. Reload the website
  3. If the error disappears, the antivirus SSL scanning is the problem

To fix it permanently without disabling your antivirus:

Fix 4: Update Windows

Windows updates include new root certificates that browsers use to verify SSL. An outdated system may be missing certificates for newer websites.

  1. Press Win + I to open Settings
  2. Go to Windows Update
  3. Click "Check for updates" and install all available updates
  4. Restart your computer and reload the website

Fix 5: Flush DNS Cache

A corrupted DNS cache can sometimes cause connection verification errors.

  1. Press Win + R, type cmd, press Ctrl + Shift + Enter to run as administrator
  2. Type: ipconfig /flushdns and press Enter
  3. You should see "Successfully flushed the DNS Resolver Cache"
  4. Also run: netsh winsock reset and restart your PC

Fix 6: Change DNS Servers

Your ISP's DNS servers may be slow or misconfigured. Switch to Google's or Cloudflare's public DNS:

  1. Press Win + R, type ncpa.cpl, press Enter
  2. Right-click your active network connection → Properties
  3. Double-click "Internet Protocol Version 4 (TCP/IPv4)"
  4. Select "Use the following DNS server addresses"
  5. Enter: Preferred DNS: 8.8.8.8 / Alternate DNS: 8.8.4.4 (Google)
  6. Click OK and reload the website

Fix 7: Reset Browser Settings

If none of the above worked, a corrupted browser profile may be to blame. Resetting restores default settings without deleting bookmarks.

Chrome:

  1. Open Chrome settings (three dots → Settings)
  2. Scroll down and click "Reset and clean up"
  3. Click "Restore settings to their original defaults"
  4. Confirm with "Reset settings"

Firefox:

  1. Open Help menu → "More troubleshooting information"
  2. Click "Refresh Firefox"

Fix 8: Check if It's a Website Problem

Sometimes the error is not on your end — the website's SSL certificate may be genuinely expired or misconfigured. To check:

⚠️ Never proceed to banking, payment, or email sites through the error. If your bank shows this error, call them directly.

Still Seeing the Error?

If you've tried all 8 fixes and the error persists, the issue may be deeper — a corrupted Windows certificate store, malware redirecting traffic, or a misconfigured proxy. These require advanced diagnostics.

Error Still Won't Go Away?

I'll diagnose and fix the connection error on your computer remotely.
Most cases resolved in 20–30 minutes via AnyDesk.

Get Help — $20

Conclusion

The "Your connection is not private" error is almost always fixable in a few minutes. Start with Fix 1 (check the date and time) — it solves the problem in 9 out of 10 cases. If that doesn't work, go through the list in order. Still stuck? Feel free to reach out — I'll fix it remotely.