The “this connection is not private” error message is a fairly common issue that internet users encounter, but most people aren’t aware as to why it happens, and more importantly, how to fix it.
What does the error message “This connection is not private” mean?
Every secure HTTPS website uses an SSL certificate, which establishes an encrypted connection between web servers and browsers using a standardized data security protocol.
When you try to access a website, your browser sends a request to your hosting server asking for the approval of the certificate. Your server then checks whether the certificate of the target site complies with current data protection standards.
If the certificate is not set up correctly, this data will not be encrypted properly, and the browser cannot check whether the visit to the website is secure. In this case, the “connection is not private” error message will be displayed to alert you to the problem.
When you see this error, your browser is simply trying to prevent you from accessing an unsafe website; otherwise, your personal information could be vulnerable to online threats.
What does the “This connection is not private” error look like on different browsers?
The “this connection is not private” message is displayed in different ways depending on the browser, the operating system and the certificate configuration.
Google Chrome
If Google Chrome is unable to authenticate a certificate, a large red exclamation mark is displayed telling you that “Your connection is not private”.
Attackers could try to steal your information like passwords, messages or credit cards. If you click on the “Advanced” button on the left, you will see some error codes that can help you pinpoint the problem, including:
- ERR_CERT_SYMANTEC_LEGACY
- ERR_SSL_VERSION_OR_CIPHER_MISMATCH
- NET::ERR_CERT_AUTHORITY_INVALID
- NET::ERR_CERT_COMMON_NAME_INVALID (this happens if there is a mismatch between the certificate and the domain)
- NET::ERR_CERT_DATE_INVALID
- NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHMT
- NTE::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
- SSL certificate error
Mozilla Firefox
If you discover an invalid certificate in Mozilla Firefox, you will see a message with a crossed-out red lock like this.
Some common error codes are also available in the advanced option of Mozilla Firefox.
- MOZILLA_PKIX_ERROR_ADDITIONAL_POLICY_CONSTRAINT_FAILED
- SEC_ERROR_EXPIRED_ISSUER_CERTIFICATE
- SEC_ERROR_EXPIRED_CERTIFICATE
- SEC_ERROR_UNKNOWN_ISSUER
- MOZILLA_PKIX_ERROR_MITM_DETECTED
- ERROR_SELF_SIGNED_CERT
- SSL_ERROR_BAD_CERT_DOMAIN
Microsoft Edge
Interestingly, the error “Your connection is not private” looks exactly the same in Microsoft Edge and Opera as it does in Google Chrome.
This usually appear with an error code like:
- NET::ERR_CERT_COMMON_NAME_INVALID (this happens when the certificate and domain do not match)
- Error code: 0
- DLG_FLAGS_INVALID_CA
- DLG_FLAGS_SEC_CERT_CN_INVALID
Safari
If an incorrect certificate has been set up, the error message “This connection is not private” is displayed as in our title. This website may be impersonating “websiteurl.com” to steal your personal or financial information. You should return to the previous page.
Unfortunately, unlike other browsers, Safari does not display error codes that you can use to isolate the problem.
Now that you know what the error message looks like in different browsers, it’s time to move on to troubleshooting the issue.
How to fix the “This connection is not private” error as a visitor
Try reloading the page
First, try reloading the page to fix the “This connection is not private” error message. Your SSL certificate may have been reissued, or something may have gone wrong with your browser.
Complete the public WiFi login process
When using public WiFi networks, you might encounter the “This connection is not private” error if you haven’t completed the network’s login process, as any public networks require you to accept terms and conditions before allowing secure (HTTPS) connections. Make sure that you’ve completed the login process in full.
Try incognito mode
Opening the site in incognito or private browsing mode can help determine if the issue is related to your browser’s stored data. Incognito mode starts with a clean slate—no cookies, cached files, or saved settings that might interfere with the connection process.
If the site loads correctly in incognito mode but not in regular browsing, this suggests the problem is with your browser’s stored data.
Clear your browsing data
When your browser cache and cookies become outdated or corrupted, they can interfere with secure connections. Clearing your browsing data often resolves the “This connection is not private” error:
- Open your browser’s settings
- Find the privacy or browsing data section
- Select options to clear cookies, cache, and browsing history
- Restart your browser and try accessing the site again
Check your computer’s date and time settings
If you have the wrong date or time on your device it can also cause certificate validation failures, as your browser uses your system’s clock to verify if an SSL certificate is valid.
For Windows:
- Go to Settings then select Time & Language > Date & Time
- Click “Set time automatically” and “Set time zone automatically”
- Verify that you’ve got the right date and time
- Restart your browser
For macOS:
- Scroll up to the Apple menu and click System Settings
- Select Date & Time
- Click the “Set date and time automatically” checkbox
- Switch to the Time Zone tab and activate “Set time zone automatically based on current location”
- Restart your browser and try again
Temporarily disable security software
Antivirus software or VPNs can interfere with secure connections by intercepting and scanning encrypted traffic. This can cause certificate validation issues. To make sure this isn’t an issue:
- Temporarily disable your antivirus software
- If you’re using a VPN, try disconnecting from it
- Visit the website again to see if the error persists
- If the site loads correctly, adjust the settings in your security software to whitelist the site
- Remember to re-enable your security software afterward for protection
Bypass the warning (not recommended)
If all other methods have failed and you’re confident the website is trustworthy, you can proceed at your own risk. Be aware that bypassing certificate warnings removes an important security protection.
In Google Chrome, you can click the “Advanced” button and select “Proceed to [website]” to temporarily bypass the warning for that site.
Important: Only do this for sites you absolutely trust and when you understand the potential risks. Never bypass these warnings on banking sites, online stores, or any site where you enter personal or financial information.
Conclusion
While browsers display these warnings to protect you, encountering them can be frustrating when you’re trying to access content you need.
Most “This connection is not private” errors are temporary or can be resolved using the methods above. If the error persists across multiple browsers and devices, the issue is likely with the website itself, and you should contact the site owner to inform them of the problem.
Remember that security warnings exist for good reasons. Whenever possible, wait for the website owner to fix their certificate issues rather than trying to bypass them.
