The “Your connection is not private” warning means your browser could not verify the website’s HTTPS certificate. In most cases the cause is simple: the computer clock is wrong, the browser cache is stale, a public Wi-Fi login page is interrupting HTTPS, or security software is scanning encrypted traffic. Less often, the website’s certificate is actually expired or a network tool is intercepting your connection.
| Error | Your connection is not private / Your connection isn’t private |
| Common browsers | Chrome, Edge, Safari, Firefox, Android Chrome, Chromebook |
| Common codes | NET::ERR_CERT_DATE_INVALID, NET::ERR_CERT_AUTHORITY_INVALID, ERR_CERT_COMMON_NAME_INVALID, ERR_SSL_PROTOCOL_ERROR |
| Safe first action | Do not enter passwords or payment details until you know why the warning appears. |
| Fastest fixes | Check date/time, try another network, complete Wi-Fi login, clear site data, update browser, disable HTTPS scanning temporarily. |
“Your Connection Is Not Private” Error Fix: 9 Safe Steps
Try these in order. Stop when the site loads normally.
- Check the website address. Make sure you did not mistype the domain.
- Refresh the page. A temporary certificate or network hiccup can clear on reload.
- Fix the date and time. Turn on automatic time and sync the clock.
- Try Incognito or another browser. If it works there, an extension, cookie, or cached certificate state is likely involved.
- Complete public Wi-Fi login. Open a plain HTTP page such as
http://neverssl.comto trigger the captive portal, then return to the HTTPS site. If the portal looks suspicious, use the public Wi-Fi safety checklist before entering credentials. - Clear cache and cookies for the affected site. Avoid wiping everything until you test a targeted cleanup.
- Update Chrome, Edge, Safari, Firefox, and the operating system. Old root certificates and outdated browser builds can break HTTPS.
- Temporarily disable VPN, proxy, or antivirus HTTPS scanning. Turn it back on after testing.
- Do not bypass the warning for banking, email, shopping, crypto, work portals, or login pages.
What the Warning Actually Means
HTTPS uses certificates to prove that the site you opened is really the site it claims to be. Your browser checks the certificate’s domain name, issuer, expiration date, encryption settings, and trust chain. If something does not match, the browser shows a privacy warning before any sensitive information is exchanged.
That does not always mean the website is malicious. It can also mean your PC clock is wrong, the site owner forgot to renew the certificate, a school or company network is filtering traffic, or a VPN/security product is intercepting the connection. The goal is to find which case applies before you type anything private.
Error Codes and What They Usually Mean
| Error code | Likely cause | Best first fix |
NET::ERR_CERT_DATE_INVALID |
Your clock is wrong, or the site’s certificate is expired/not valid yet. | Sync date/time first. If the clock is correct and only one site fails, the site owner may need to fix the certificate. |
NET::ERR_CERT_AUTHORITY_INVALID |
The certificate issuer is not trusted, or traffic is being intercepted by antivirus, proxy, school/work filter, or malware. | Test another network, disable HTTPS scanning temporarily, and check whether the error appears on many sites. |
ERR_CERT_COMMON_NAME_INVALID |
The certificate is issued for a different domain than the one you opened. | Check for typos, try the correct domain, and avoid entering credentials if the warning remains. |
ERR_SSL_PROTOCOL_ERROR |
Browser, network, firewall, or server cannot agree on a secure connection. | Update browser/OS, disable VPN/proxy for testing, and try a different network. |
ERR_CERTIFICATE_TRANSPARENCY_REQUIRED |
The certificate does not meet Chrome’s transparency requirements. | Usually a website-side issue. Do not bypass it for sensitive sites. |
Fix 1: Check the Address and Reload
Start with the simple checks. Make sure the domain is exactly right. A typo such as an extra letter, missing hyphen, or wrong top-level domain can land you on a different site with a mismatched certificate.
Then reload the page. If the issue was a temporary network or certificate validation problem, a normal refresh can be enough. If the warning returns, continue below.
Fix 2: Correct Date and Time on Windows, Mac, Android, and iPhone
Wrong date and time is one of the most common causes of NET::ERR_CERT_DATE_INVALID. Certificates are valid only during a specific time window. If your computer thinks today is in the past or future, normal certificates can look invalid.
Windows
- Right-click the clock in the taskbar.
- Choose Adjust date and time.
- Enable Set time automatically and Set time zone automatically.
- Click Sync now.
- Restart the browser and open the site again.
Mac
- Open System Settings.
- Go to General > Date & Time.
- Enable automatic date and time.
- Restart the browser.
Android and iPhone
On Android, open Settings > System > Date & time and enable automatic time. On iPhone, open Settings > General > Date & Time and enable Set Automatically.
Fix It on Android, iPhone, and Chromebook
On mobile devices and Chromebooks, the same warning is usually caused by the clock, public Wi-Fi, a cached site state, VPN/proxy settings, or an outdated browser build. Use this shorter path before changing deeper certificate settings.
- Switch networks. Try mobile data or another Wi-Fi network. If the site opens there, the original Wi-Fi or captive portal is likely involved.
- Turn on automatic date and time. Wrong time can make valid certificates look expired or not valid yet.
- Update Chrome, Safari, or the Chromebook system. Old browser/root-certificate stores can fail on modern HTTPS sites.
- Clear site data for the affected website. Start with the single site instead of wiping all browser data.
- Disable VPN or private DNS temporarily. Turn it back on after testing, and avoid entering passwords until the warning is gone.
Fix 3: Test Incognito Mode and Browser Extensions
Open the page in Incognito or InPrivate mode. If the warning disappears there, the problem is probably tied to normal browser data or an extension.
- Disable recently installed extensions.
- Pay attention to shopping helpers, coupon tools, VPN extensions, downloaders, and unknown security extensions.
- Restart the browser after disabling them.
- Enable extensions one by one to find the one causing the error.
If the error appears in Incognito, another browser, and on multiple sites, the cause is more likely clock, network, VPN/proxy, antivirus HTTPS scanning, or system-level certificate interception.
Fix 4: Clear Cache, Cookies, and SSL State
Bad cached data can cause a site to keep failing even after the original problem is gone. Start with the affected site if possible, then clear wider browser data if needed.
Chrome
- Open Settings > Privacy and security.
- Choose Delete browsing data.
- Select cookies and cached images/files.
- Clear data and restart Chrome.
Firefox
Open Settings > Privacy & Security, then clear cookies and cached web content.
Microsoft Edge
Open Settings > Privacy, search, and services > Choose what to clear, then clear cookies and cache.
Fix 5: Public Wi-Fi, Captive Portals, and Router Problems
Public Wi-Fi often redirects you to a login or terms page before allowing full internet access. That redirect can break HTTPS and trigger “Your connection is not private”.
- Disconnect and reconnect to the Wi-Fi network.
- Open
http://neverssl.comto force the Wi-Fi login page to appear. - Accept the terms or sign in.
- Return to the HTTPS site.
If the problem happens at home on all devices, restart your router and modem. If it happens only on one device, focus on that device’s clock, browser, VPN, proxy, and security software.
Fix 6: VPN, Proxy, Firewall, or Antivirus HTTPS Scanning
Some VPNs, proxies, firewalls, and antivirus products inspect encrypted traffic. To do that, they may install a local certificate and sit between your browser and the website. If that certificate is expired, misconfigured, or not trusted by the browser, privacy errors appear.
- Disconnect VPN temporarily and reload the site.
- Turn off proxy settings if you do not intentionally use a proxy.
- In antivirus settings, look for HTTPS scanning, encrypted connection scanning, web shield, or similar options.
- Disable that feature only long enough to test, then turn protection back on or update the security product.
- If this is a company or school device, ask the administrator before changing certificate or proxy settings.
If disabling HTTPS scanning fixes the error, update the security product and check whether its root certificate is installed correctly. Do not leave important security features disabled permanently without replacing them with a safer configuration.
Fix 7: Update Browser, Operating System, and Root Certificates
Old browsers and unsupported operating systems may not trust current certificates. Update the browser first, then install OS updates.
Chrome
Open Settings > About Chrome. Let Chrome check for updates, then relaunch.
Windows and macOS
On Windows, open Settings > Windows Update. On Mac, open System Settings > General > Software Update.
Should You Bypass “Your Connection Is Not Private”?
Usually no. Bypassing the warning tells the browser to load a page it could not verify. That may be acceptable only for a device you own on a private network, such as a router admin page, NAS, local development server, or internal test system where you expect a self-signed certificate.
Do not bypass the warning for:
- Banking or payment pages
- Email and social media logins
- Online stores
- Crypto wallets and exchanges
- Government, tax, health, or identity portals
- Any site asking for passwords, card data, recovery codes, or personal documents
If a search result or ad tells you to type a hidden bypass command, treat that as a last-resort developer workaround, not a normal fix. For everyday browsing, the safe answer is to fix the cause or leave the site.
When the Website Owner Must Fix It
Sometimes there is nothing wrong with your device. The website may have an expired certificate, a certificate for the wrong domain, missing intermediate certificates, unsupported TLS settings, or a misconfigured redirect between www and non-www versions.
You can suspect a website-side issue when:
- Only one website fails.
- The same site fails on your phone using mobile data.
- Other people see the same warning.
- The error says the certificate expired or belongs to another domain.
In that case, do not force the page open. Contact the site owner or wait until they renew or repair the certificate.
If you own the affected website, check the SSL/TLS setup before asking visitors to bypass the warning:
- Renew the certificate and confirm it covers the exact hostname, including
wwwor non-www. - Install the full intermediate certificate chain, not only the leaf certificate.
- Make sure HTTP-to-HTTPS and
www/non-wwwredirects land on the same valid HTTPS hostname. - Check CDN, hosting-panel, and reverse-proxy SSL modes after certificate renewal.
- Fix mixed-content warnings if the page loads insecure scripts, images, or forms after HTTPS works.
Malware Check: When the Error Appears on Many Sites
If the warning appears on many unrelated sites, especially banking, search, email, and shopping sites at the same time, check for unwanted software. Browser hijackers, malicious extensions, rogue VPNs, adware, and traffic-filtering malware can tamper with DNS, proxies, certificates, or browser settings.
Look for these signs:
- The homepage or search engine changed by itself.
- Unknown extensions return after removal.
- Proxy settings keep turning back on.
- Security warnings appear on nearly every HTTPS site.
- Ads, redirects, or fake support pages appear alongside certificate errors.
Check for browser hijackers, rogue certificates, and unwanted proxy changes.
If date, browser, Wi-Fi, VPN, and antivirus checks do not explain the warning, scan the system for adware, unwanted extensions, and malware that can interfere with secure connections.
FAQ
Why does Chrome say “Your connection is not private”?
Chrome shows the warning when it cannot verify the site’s HTTPS certificate. The cause can be a wrong clock, expired certificate, public Wi-Fi login page, VPN/proxy, antivirus HTTPS scanning, browser cache, or a real website certificate problem.
How do I fix NET::ERR_CERT_DATE_INVALID?
Check the device date, time, and time zone first. Turn on automatic time sync and reload the page. If your clock is correct and only one website shows the error, the site certificate may be expired or not valid yet.
Why does the error happen on every website?
If every HTTPS site fails, the cause is usually local: wrong date/time, VPN/proxy, antivirus HTTPS scanning, missing root certificates, network filtering, or malware. Test another network and another browser to narrow it down.
Can I bypass the privacy warning?
Do not bypass it for sites where you log in, pay, shop, bank, or enter personal information. Bypassing may be acceptable only for known local devices or development pages where you expect a self-signed certificate.
Why does public Wi-Fi cause this error?
Public Wi-Fi often needs a login or terms page before internet access. That portal may interrupt HTTPS traffic. Open a plain HTTP page to trigger the login screen, complete it, then return to the secure site.
Can antivirus software cause “Your connection is not private”?
Yes. Some security products scan encrypted connections. If their local certificate is broken, expired, or not trusted, browsers can show privacy errors. Temporarily disabling HTTPS scanning can confirm the cause.
How do I fix “Your connection is not private” on Android or Chromebook?
Switch to another network, enable automatic date and time, update Chrome or ChromeOS, clear site data for the affected website, and temporarily disable VPN, proxy, or private DNS. Do not sign in or enter payment details until the warning disappears.
Is “Your connection is not private” a virus?
The warning itself is not a virus. It is a browser safety check. However, if it appears on many unrelated sites together with redirects, unknown extensions, changed proxy settings, or fake support pages, scan the device for adware, browser hijackers, or unwanted network-filtering software.
Bottom Line
“Your connection is not private” is a browser safety warning, not just an annoyance. Fix the clock, cache, browser, Wi-Fi login, VPN/proxy, and HTTPS scanning first. If the warning affects only one site, the site owner may need to fix the certificate. If it affects many sites and comes with redirects or unknown extensions, scan for unwanted software before entering any private information.
