Seeing the message “Your connection is not private” in Chrome is alarming, especially when you only wanted to open a normal website. The warning means Chrome could not verify the site’s security certificate, so it stops you before any data is sent. The cause is often simple, such as a wrong clock or a temporary network issue, and you can usually fix it in a few minutes. This guide explains what the error means, how to read the error code, and nine fixes you can try in order.
What does “Your connection is not private” mean?
When you open a website that uses HTTPS, Chrome checks the site’s SSL/TLS certificate. It confirms that the certificate is issued by a trusted authority, has not expired, and matches the site name. If any check fails, Chrome shows a full-page warning with the heading “Your connection is not private” and an error code below it.
The warning does not always mean the site is dangerous. It means Chrome cannot be sure the connection is safe. The problem can be on your device, on your network, or on the website itself.
Read the error code first
Click Advanced on the warning page and look at the code under the heading. It tells you where to start.
| Error code | What it usually means | Best first fix |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID | Your clock is wrong, or the site’s certificate has expired or is not valid yet | Check date and time |
| NET::ERR_CERT_AUTHORITY_INVALID | Chrome does not trust the company that issued the certificate | Try another network, check antivirus HTTPS scanning |
| NET::ERR_CERT_COMMON_NAME_INVALID | The certificate does not match the address you typed | Check the address, try with or without www |
| ERR_SSL_PROTOCOL_ERROR | Chrome and the site could not agree on a secure connection | Update Chrome, disable VPN or proxy |
9 fixes for the “Your connection is not private” error
Fix 1: Reload the page and check the address
Press Ctrl + R (Windows) or Cmd + R (Mac) to reload. Then look at the address bar. A typing mistake, an old bookmark, or a link that uses http instead of https can trigger the warning. Type the address again, using the official domain.
Fix 2: Correct your date and time
A wrong clock is one of the most common causes, especially for NET::ERR_CERT_DATE_INVALID. Certificates are valid for a specific period, so if your device thinks it is a different date, every certificate looks expired.
- Windows: Settings > Time & language > Date & time, then turn on Set time automatically.
- Mac: System Settings > General > Date & Time, then turn on automatic time setting.
- Android: Settings > System > Date & time, then enable automatic date and time.
- iPhone: Settings > General > Date & Time, then turn on Set Automatically.
Reload the page after you change the setting.
Fix 3: Test in an Incognito window
Press Ctrl + Shift + N (Windows) or Cmd + Shift + N (Mac) to open Incognito. If the site opens there, something stored in your normal profile, such as an extension, cached data or cookies, is causing the problem. Fixes 4 and 5 will solve it.
Fix 4: Clear cache and cookies
Old cached data can conflict with a site’s new certificate. Open Settings > Privacy and security > Delete browsing data, choose Cached images and files and Cookies and other site data, then clear them. Our step-by-step guide on how to clear cache in Google Chrome covers Windows, Mac, Android and iPhone.
Fix 5: Turn off extensions
Some extensions, especially ad blockers, security tools and VPN add-ons, can interfere with HTTPS connections. Type chrome://extensions in the address bar, switch all extensions off, and reload the site. If the error disappears, turn extensions back on one by one to find the culprit.
Fix 6: Check public Wi-Fi and captive portals
Airports, hotels, cafes and offices often ask you to sign in before you can browse. Until you do, the network redirects your traffic, which breaks HTTPS and triggers this warning. Open a plain http page such as a login prompt, finish the sign-in, then try again. If you cannot tell whether a network is safe, switch to your mobile data instead.
Fix 7: Pause VPN, proxy or antivirus HTTPS scanning
Some antivirus and firewall programs scan encrypted traffic by placing their own certificate between you and the site. If Chrome does not trust that certificate, you see the warning. Temporarily turn off the HTTPS or web scanning feature, or disconnect your VPN or proxy, and test again. If that fixes it, look for an option in the security software to install its certificate properly or exclude Chrome. Re-enable your protection straight afterwards.
Fix 8: Update Chrome and your operating system
Outdated browsers and systems can miss newer root certificates. Open Settings > About Chrome and let Chrome update, then restart it. Also install pending Windows, macOS, Android or iOS updates. This is also good security hygiene, as explained in our guide to macOS security and dealing with malware.
Fix 9: Restart the router or change DNS
Restart your modem and router, wait a minute, and reconnect. If the problem continues on every site, try a different DNS server such as your provider’s default or a public DNS service. Changing DNS can also help when the network is returning a wrong address for the site.
What if the problem is the website?
If the error appears on one site only, appears on every device and network you try, and the code points to an expired or mismatched certificate, the website owner needs to fix it. You cannot repair it from your side.
Site owners should check three things: the certificate has not expired, it covers both the www and non-www versions of the domain, and the server sends the full certificate chain. Renewing or reinstalling the certificate in the hosting control panel normally resolves it.
Should you click “Proceed to site (unsafe)”?
Chrome lets you continue after clicking Advanced, but treat that as a last resort. Proceeding is reasonable only when you fully trust the site and you are not entering passwords, card numbers or personal data, for example when you are testing your own website. Never bypass the warning on banking, shopping, email or social media sites. If the warning appears for a major site on a public network, assume someone may be interfering with the connection and leave.
While you are cleaning up browser behavior, you may also want to turn off the pop-up blocker in Google Chrome for sites that need pop-ups, though keep it on for everything else.
Quick checklist
- Reload and retype the address.
- Make sure date, time and time zone are automatic.
- Try Incognito and another network.
- Clear cache, cookies and disable extensions.
- Pause VPN, proxy and HTTPS scanning, then update Chrome and your system.
- If only one site fails, wait or contact the site owner.
For more official guidance, see the Chrome Help Center.
Fixes by device: what to check first
The same warning can come from different causes depending on where you see it, so start with the most likely one for your device.
- Windows PC: wrong clock, antivirus HTTPS scanning, or a proxy set by a program. Check the date and time first, then your security software.
- Mac: wrong date and time, a VPN profile, or outdated macOS. Update the system and test with the VPN off.
- Android: wrong date setting, captive-portal Wi-Fi, or an old Chrome version. Switch to mobile data to test quickly.
- iPhone: date and time not set automatically, or a content filter app. Check Settings > General > Date & Time first.
If the error appears on every device on your home network, restart the router and look at its security settings. If it appears only on one phone or laptop, the fix is almost always on that device.
Frequently Asked Questions
Why does Chrome say my connection is not private?
Chrome shows this message when it cannot verify the website’s security certificate. The cause may be a wrong device clock, a network that interferes with HTTPS, security software, or an expired or misconfigured certificate on the site.
Is it safe to ignore the warning?
Usually no. Ignoring it can expose anything you type to attackers if the connection really is intercepted. Only continue on a site you fully trust, and never enter sensitive information.
Why does the error show only on one device?
If other devices on the same network open the site fine, the problem is local. Check that device’s date and time, browser extensions, antivirus and operating system updates.
Does the error mean my device is hacked?
Not by itself. In most cases it comes from a wrong clock or a network setting. It is still worth running a security scan if the warning appears on many different sites at once.
How do I fix it on Android or iPhone?
Set the date and time to automatic, update Chrome from the app store, clear Chrome’s data, and switch from public Wi-Fi to mobile data to test.
Conclusion
The “Your connection is not private” error looks scary, but it is usually fixable. Start with the error code, correct your date and time, test in Incognito, clear the cache, and then check extensions, networks and security software. If nothing works and only one site is affected, the site’s certificate is likely at fault, and the owner has to fix it. Stay cautious, and never push past the warning on sites where you handle money or personal information.
