Nothing kills your flow quite like opening a website you trust and being greeted by a full screen warning instead. Chrome refuses to load the page, shows a red warning icon, and tells you your connection is not private. Your first thought is usually that something is wrong with the website. Sometimes it is. More often, the problem sits on your own computer, your network, or your clock, and it takes only a few minutes to sort out.
This guide walks you through what the warning means, why it appears, and the fixes that work, in the order you should try them. Most people solve it within the first three steps, so work down the list and stop as soon as the page loads normally again.
What the Warning Actually Means
When you visit a website over HTTPS, Chrome checks the site's security certificate before it shows you anything. That certificate proves the site is who it claims to be and that your connection to it is encrypted. If anything about the certificate looks wrong, Chrome blocks the page and shows the "Your connection is not private" warning.
The most common causes are an expired certificate, a certificate issued for a different domain name, or a certificate Chrome simply cannot verify. None of these automatically mean the site is dangerous, but Chrome cannot prove it is safe, so it refuses to take the risk for you. The warning also appears when your own device is the problem, for example when your system clock is wrong, because certificates are only valid between two dates. If your clock says it is 2021, every certificate issued since then looks like it comes from the future.
First, Check Whether It Is Just One Website
Before changing anything on your computer, open a different well known site such as google.com or bbc.co.uk. If those load fine and only one site shows the warning, the problem is almost certainly with that site's certificate, not your device. The site owner needs to renew or fix their certificate, and there is very little you can do except wait or contact them.
If every HTTPS site shows the warning, the fault is on your side, and the fixes below will sort it. If the warning appears only on public Wi-Fi, such as in a cafe, hotel, or airport, the network itself may be intercepting your connection. Many public networks use a captive portal that you must sign in to before real internet access begins, and until you do, Chrome sees a certificate that does not match the site you asked for.
Try the same site in an incognito window too. If it loads there, a browser extension or some cached data is the likely cause, which narrows your search straight away.
Fix 1: Correct Your Date and Time
A wrong system clock is the single most common cause of this error on laptops, and it is also the quickest to fix. Certificates carry a valid from and valid to date. If your clock is set days, months, or years out, Chrome decides the certificate is not yet valid or has already expired.
On Windows, right click the clock in the taskbar, choose Adjust date and time, and turn on both Set time automatically and Set time zone automatically. On a Mac, open System Settings, go to General, then Date and Time, and turn on Set time and date automatically. Then close Chrome completely and reopen it.
This fix also explains why the error sometimes appears after a laptop battery has died completely or after a CMOS battery failure on an older desktop. When the machine loses power for a long time, the clock can reset to the factory date, and every secure site suddenly looks broken. If your clock keeps drifting after you correct it, the CMOS battery may need replacing, which is a cheap repair at any computer shop.
Fix 2: Clear Your Browsing Data and SSL State
Corrupt cached certificates and stale browsing data can trigger the warning even when nothing else is wrong. Clearing them forces Chrome to fetch fresh copies.
In Chrome, press Ctrl plus Shift plus Delete to open the Clear browsing data panel. Select Cached images and files and Cookies and other site data, set the time range to All time, and click Clear data. Restart Chrome and try the site again. If the page loads, the problem was stale data and you are done.
Windows also keeps its own store of SSL certificates, and clearing it can help when the browser clear alone does not. Open the Control Panel, search for Internet Options, go to the Content tab, and click Clear SSL state. Confirm, close the window, and restart Chrome. This takes less than a minute and is worth trying before moving on to deeper fixes.
Fix 3: Check Your Wi-Fi Network and Router
Network problems cause this warning more often than people expect. A router that is struggling, a DNS server that is misbehaving, or a public network that intercepts traffic can all break the certificate check.
Start by restarting your router. Switch it off at the power socket, wait a full 30 seconds, and switch it back on. Wait until all the lights settle, then try the site again. If you are on public Wi-Fi, look for a sign in page. Many networks open one automatically, but if yours does not, try opening a plain HTTP site such as example.com, which often triggers the portal to appear. Once you have signed in to the network, secure sites should load normally.
If the problem affects only one network, try switching to another, such as your phone hotspot. If sites load fine on the hotspot, your home network is the issue, and the router or your internet provider is the next place to look. You can also try changing your DNS server to a public one such as Google DNS at 8.8.8.8 or Cloudflare at 1.1.1.1, which sometimes clears the error when your provider's DNS is returning bad results.
Fix 4: Turn Off Extensions and Antivirus SSL Scanning
Browser extensions can interfere with secure connections, especially VPN extensions, ad blockers, and security toolbars that inspect your traffic. Open an incognito window, where most extensions are off by default, and try the site. If it works there, disable your extensions one by one in chrome://extensions until you find the one causing the trouble. You can usually keep the extension and simply update it or change its settings.
Antivirus software is another frequent culprit. Many security suites scan encrypted traffic by inserting their own certificate, and if that certificate is out of date or misconfigured, Chrome rejects it. Open your antivirus settings and look for an option called HTTPS scanning, SSL scanning, or encrypted connection scanning. Turn it off temporarily and test the site. If the warning disappears, either leave the feature off or update the antivirus, which normally refreshes its certificate. This is a safe test because Chrome still checks the real site certificate on its own.
Fix 5: Update Chrome and Your Operating System
An old version of Chrome may not recognise newer certificates or current security standards. Click the three dot menu, go to Help, then About Google Chrome, and let it check for updates. Install anything it finds and restart the browser. The same applies to your operating system, because Windows and macOS updates also refresh the trusted certificate store your browser relies on.
While you are here, check that your computer has not been set to an unusual date in the past by a dual boot setup or a virtual machine, and make sure your time zone matches where you actually are. These small details matter more than they seem, because certificate checks are strict about time.
If you want the full step by step walkthrough with screenshots, this guide on how to fix your connection is not private in Chrome covers every fix above in detail.
When It Is Safe to Proceed and When to Walk Away
Chrome lets you click Advanced and then Proceed to the site anyway, but you should only do this when you are certain the site is legitimate and you understand the risk. It can be reasonable on your own router admin page or a local device page where you know the certificate is self signed. It is never a good idea on a banking site, an email login, or any page where you will enter a password or payment details.
If the warning appears on your bank, your email, or a shopping checkout, stop and use another device or network to check whether the warning follows you. If it appears everywhere, your device or network needs fixing first. If it appears only on that one site, the site itself has a certificate problem, and you should contact them or use their official app instead.
The Bottom Line
The "Your connection is not private" error looks alarming, but it is usually a small problem with a quick fix. Start by checking whether it affects one site or all of them, then correct your date and time, clear your browsing data, and restart your router. Those three steps solve the large majority of cases. Extensions, antivirus SSL scanning, and outdated software cover most of the rest.
Work through the fixes in order, test after each one, and stop as soon as the site loads. If the warning keeps appearing on important sites after everything above, get your computer checked for malware or ask your internet provider whether something on their network is interfering. Your browser is trying to protect you, and once the underlying cause is fixed, it will happily let you through.
Top comments (0)