The “Your connection is not private” error hits you with a full-screen red warning and refuses to load the page you need. It looks alarming, but it simply means your browser detected a problem with the site’s SSL/TLS certificate — and in most cases, the cause is something on your device, not the website itself. A system clock that’s off by even a few hours is the single most common trigger.
The six fixes below cover every typical cause, ranked from quickest to most involved. Most people are back on the page within two minutes. These steps work in Chrome, Edge, Firefox, and Safari on Windows, Mac, Android, and iPhone.
Quick Answer
Check your device’s date and time first — a wrong clock causes this error more than anything else. If the clock is correct, clear your browser’s cache and cookies, then try the site in incognito mode. Still blocked? Disable your VPN or antivirus HTTPS scanning and retry. Most cases clear in under two minutes.
What the Error Codes Mean
Chrome and Edge show a sub-code below the main warning. Spotting yours points you straight to the right fix.
| Error Code | What It Means | Best Starting Fix |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID | Device clock is wrong, or the site’s cert expired | Fix 1 — correct date/time |
| NET::ERR_CERT_AUTHORITY_INVALID | Certificate issuer not trusted by your browser | Fix 4 — check antivirus HTTPS scanning |
| NET::ERR_CERT_COMMON_NAME_INVALID | Domain name doesn’t match the certificate | Try the www. or non-www. version of the URL |
| NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM | Site uses outdated encryption | Fix 6 — update your browser |
6 Fixes for “Your Connection Is Not Private”
Fix 1: Correct Your Device’s Date and Time
SSL certificates have a strict validity window. If your device’s clock is wrong — even by a few hours — browsers reject valid certificates because they appear expired or “not yet valid.”
- Windows: Right-click the taskbar clock → Adjust date/time → toggle Set time automatically off, then back on.
- Mac: Apple menu → System Settings → General → Date & Time → enable Set date and time automatically.
- iPhone: Settings → General → Date & Time → enable Set Automatically.
- Android: Settings → General Management → Date and Time → enable Automatic date and time.
- Reload the page after syncing.
Pro tip: If your Windows PC keeps resetting to the wrong time after every reboot, the CMOS battery on the motherboard is likely dead — a common failure on machines more than five or six years old. Replacing it costs a few dollars.
Fix 2: Clear Your Browser’s Cache and Cookies
Stale cached certificate data can conflict with an updated cert on the server. Clearing it forces a fresh TLS handshake.
- Press Ctrl+Shift+Del on Windows or Cmd+Shift+Del on Mac (works in Chrome, Edge, and Firefox).
- Set the time range to All time.
- Check Cached images and files and Cookies and other site data.
- Click Clear data, then reload the page.
Fix 3: Open an Incognito or Private Window
Browser extensions — especially ad blockers, VPN add-ons, and security tools — can interfere with certificate validation. Incognito mode disables most extensions by default.
- Press Ctrl+Shift+N in Chrome or Edge, or Ctrl+Shift+P in Firefox.
- Navigate to the same URL.
- If the page loads, an extension is the culprit. Disable them one at a time at chrome://extensions or Firefox’s about:addons to identify it.
Fix 4: Disable Your VPN or Antivirus HTTPS Scanning
Antivirus programs — including Avast, Kaspersky, ESET, and Bitdefender — intercept HTTPS connections and substitute their own certificate. If their certificate store is outdated, browsers flag every substituted cert as untrusted.
- Temporarily disable your VPN and reload the page.
- If it still fails, open your antivirus settings and find HTTPS scanning, Web Shield, or SSL filtering and turn it off.
- If the page loads, update your antivirus to the latest version before re-enabling HTTPS scanning.
Troubleshooting tip: On corporate or school networks, a firewall or proxy may perform the same SSL interception. If you’re on managed Wi-Fi and the error appears on every HTTPS site, contact your IT department — this is expected behavior and only they can resolve it.
Fix 5: Flush Your DNS Cache
A stale DNS record can route your browser to an outdated server IP, where the certificate no longer matches the domain. Flushing DNS forces a fresh lookup.
- Windows: Open Command Prompt as Administrator and run:
ipconfig /flushdns - Mac: Open Terminal and run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Reload the page after the command completes.
Fix 6: Update Your Browser
Browser updates ship with new root certificates. An outdated browser may not recognize certificates signed by newer or recently added certificate authorities.
- Chrome: Three-dot menu → Help → About Google Chrome — it checks and installs updates automatically.
- Edge: Three-dot menu → Help and feedback → About Microsoft Edge.
- Firefox: Hamburger menu → Help → About Firefox.
- Restart the browser after updating, then retry the page.
Common Mistakes to Avoid
- Clicking “Advanced” and proceeding on unfamiliar sites. The bypass is intended for developers testing local servers. Using it on a login, banking, or shopping page exposes your credentials to interception. Only proceed on sites you personally manage.
- Clearing the cache with a short time range. Choosing “Last hour” or “Last 7 days” often leaves old cached certificates in place. Always select All time.
- Assuming the website is broken before checking your device. The most common triggers — wrong clock, cached data, antivirus interference — are all local. Rule them out first before concluding the site is at fault.
- Permanently disabling antivirus HTTPS scanning. Turn it off only long enough to confirm it’s the cause, then re-enable it or update the antivirus right away.
- Dismissing the warning on public Wi-Fi. On open networks, a persistent “connection not private” error can signal a genuine man-in-the-middle attack. Don’t proceed on public Wi-Fi without a trusted VPN active.
Frequently Asked Questions
Is this error the same in Chrome, Firefox, and Edge?
Yes — Chrome and Edge show “Your connection is not private,” Firefox says “Your connection is not secure.” All three signal the same underlying TLS certificate issue.
Does this error mean I’ve been hacked?
Almost never. The vast majority of cases trace back to a local issue — wrong clock, stale cache, or antivirus interference. A real man-in-the-middle attack would typically show NET::ERR_CERT_AUTHORITY_INVALID on a site that normally loads without any warning.
Can the website owner cause this error for all visitors?
Yes. An expired, misconfigured, or revoked certificate will block every visitor until the site owner renews or corrects it. If all six fixes fail, try again in a few hours.
Is it ever safe to click “Proceed to site (unsafe)”?
Only on sites you personally manage for local development or testing. Never proceed on any page that asks for a password, payment details, or personal information.
Why does the error appear in Firefox but not Chrome?
Firefox maintains its own certificate store, while Chrome and Edge use the Windows or macOS system store. An antivirus certificate injected into the OS store may not be trusted by Firefox, making the error appear only there.
Conclusion
The “Your connection is not private” error is fixable in minutes without any specialist knowledge. Start with your device’s clock, clear the cache, test in incognito, and work through the remaining steps in order — that sequence resolves the error for nearly every user. If all six fixes fail, the certificate problem is on the server side and only the site owner can correct it.
For other browser headaches, see how to stop Chrome from crashing and how to cut Chrome’s RAM usage. If pages still won’t load after fixing the certificate error, our Wi-Fi connected but no internet guide covers the next layer of network fixes. For a plain-language explanation of how TLS certificates work, Let’s Encrypt’s documentation is an authoritative starting point.
Last updated: June 22, 2026