How Turn Off Chrome Your Connection Is Not Private

In this article, we will understand the solution of Your Connection Is Not Private. We have seen just about every kind of inaccuracy there is to see. From problems with the database connection to the white screen of death, ERR_CACHE_MISS, and problems with the browser or TLS.

For the average user, several of these can be quite annoying and even frightening at times. Depending on the kind of issue, it might also result in website downtime, which would cost you money. Alternatively, it might just be that your computer’s browser needs to be fixed.

“Error: Your Connection is Insecure”

When you access a website, your browser initiates a request to the server and then verifies the SSL certificate on the website to confirm it meets current privacy requirements. If the certificate is invalid, it will block your access to the site and may result in the “your connection is not private” error.

What does the error message “Your Connection is Not Private” mean?

The error message “your connection is not private” only applies to websites that use or should be using HTTPS. Your browser sends a request to the server of the website you visit. The browser needs to confirm that the website’s certificate meets the latest privacy requirements. Additional occurrences include the TLS handshake, validation of the certificate against the certificate authority, and decryption of the certificate.

In case the browser detects an invalid certificate, it will automatically attempt to block your access to the website. This function is incorporated into web browsers to safeguard the user. If the certificate is not configured properly, it indicates that data encryption is ineffective, making the site unsafe for access, especially for those requiring logins or handling payment details. Rather than the website loading, you will see an error message saying “Your connection is not private.”

What is the reason behind the appearance of the “Your Connection Is Not Private” error?

You might be encountering the “your connection is not private” error because your browser is unable to authenticate an SSL certificate, which is essential for security purposes.

An SSL certificate enables the establishment of a secure connection by being a text file on a web server containing details like the domain name it was issued for and the owner of the domain.

Taking everything into account, the error message “your connection is not private” can occur due to:

• The SSL certificate on the website is invalid or absent.
• The SSL certificate was configured improperly.
• The server displayed an SSL certificate meant for a different website.
• The SSL certificate does not include any changes to the domain name.

Variations of the “This Connection Is Not Secure” Error

Numerous versions of this error vary based on the web browser, operating system, and certificate configuration on the servers being used. Although certain errors may have varying meanings at times, many troubleshooting procedures remain consistent.

Google Chrome shows a warning that says “Your connection is not secure.”

If there is a problem verifying the certificate in Google Chrome, an error message will appear stating “your connection is not private” (as shown below).

Potential attackers could be attempting to acquire your personal information from domain.com, such as passwords, messages, or credit card details.

An error code message is also sent with this to aid in identifying the precise problem. Some of the most typical problem codes that you can see in Google Chrome are listed below:

• ERR_CERT_SYMANTEC_LEGACY
• NET::ERR_CERT_AUTHORITY_INVALID
• NET::ERR_CERT_COMMON_NAME_INVALID (this occurs when the certificate does not match the domain)
• NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
• NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
• NET::ERR_CERT_DATE_INVALID
• ERR_SSL_PROTOCOL_ERROR
• ERR_SSL_VERSION_OR_CIPHER_MISMATCH

The error message differs somewhat in Mozilla Firefox

The domain.com owner has set up their website incorrectly. Firefox has not connected to this website to prevent your information from being stolen.

Similar to Chrome, an error code notice appears along with it to aid in troubleshooting. A few of the most typical error codes that you can see in Mozilla Firefox are listed below:

• 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

Your Microsoft Edge Connection Isn’t Private

You will also get the error “Your connection isn’t private” in Microsoft Edge.

Hackers may be attempting to get your credit card information, passwords, and communications from domain.com.

A notification with an error code appears beside these as well. Just a few of the most typical error codes are listed below:

• NET::ERR_CERT_COMMON_NAME_INVALID (this occurs when the certificate does not match the domain)
• Error Code: 0
• DLG_FLAGS_INVALID_CA
• DLG_FLAGS_SEC_CERT_CN_INVALID

In Safari, This Connection Is Not Private

The error “Your connection is not private” will appear in Safari.

This website may be posing as “domain.com” to get your money or personal data. Return to the previous page, please.

How to Resolve the Error “Your Connection Is Not Private”

Whenever you see a “your connections are not private” problem, you might not even know where to start. According to our experience, these problems usually have two root causes: either a client-side issue (your browser, computer, or operating system) or an actual website certificate issue (expired, incorrect domain, or not trusted by the company). We will thus briefly discuss each.

1. Attempt to refresh the page.

It may be evident to some, but a simple solution to the “your connection is not private” error is to close and reopen your browser before reloading the page. The reason might be that the website owner is currently renewing their SSL certificate or there was a problem with your browser.

2. Proceed without automated assistance (Potentially dangerous)

Your choice is to just continue manually. Nevertheless, we strongly advise against attempting this unless you are fully aware that no encryption will occur if you continue. If you will be providing login information or payment details, feel free to proceed to the following steps.

We include this option solely to articulate the complete consequences of taking this action. Observing this error may indicate an attempt to deceive or steal your information, so it’s advisable to promptly exit the website. The website may have also been hacked, leading to a malicious redirection. In a public setting, always avoid attempting to go around this screen.

If you wish to continue, typically you can find a link labeled “Proceed to domain.com” at the bottom of the error screen. This can be concealed under the “Advanced” option in certain browsers. If the website employs HSTS, the feature described will not be accessible because HSTS enforces an HTTP header that prohibits non-HTTPS connections.

3.  Are you currently situated in a cafe or an airport?

It may seem strange, but coffee shops and airport Wi-Fi networks are often where users encounter the “your connection is not private” error most frequently. What is the reason for that? Many of them are not yet using HTTPS for everything, or if they are, it’s not set up properly. This typically refers to the login screen where you must agree to the terms and conditions to access the portal. This error may appear if you attempt to access an HTTPS site without first agreeing to the portal’s terms. Here are a few simple actions to navigate through it.

1. Access the Wi-Fi network at either the café or the airport.
2. Navigate to a website that does not utilize HTTPS, for example, http://www.weather.com.
3. Next, the login page will appear. You have the option to agree to the terms before logging in. Because terms typically only require a checkbox, it is not a major concern if the connection is not running over HTTPS. After you have established a connection, you can navigate to websites through HTTPS. If you are unable to access the sign-in page, you might want to consider entering 1.1.1.1 in your browser as an alternative option (source).

Don’t forget, that when using public Wi-Fi, a VPN can provide extra protection by concealing your online activity. Below are a few well-liked options that you may be interested in exploring:

• Private Internet Access.
• TunnelBear VPN service
• NordVPN offers secure internet connection services.

4. Verify the Clock on Your Computer

A frequently seen cause of the “your connection is not private” issue is a malfunctioning computer clock. For browsers to validate the SSL certificate, things have to line up appropriately. If you have bought a new computer, especially a laptop that is connected to Wi-Fi for the first time, this might easily happen. Not every time you log in, they immediately synchronize. The instructions to change your computer’s time are listed below. Note: Mobile devices may also experience this.

Windows

1. In the task tray in the lower right corner, right-click the time.
2. Choose “Change the date/time.”

3. Choose the options “Set time automatically” and “Set time zone automatically,” if desired. This will be updated based on an NTP server maintained by Microsoft. Make sure the time in the task tray on the bottom right is accurate by checking it again. If not, you may manually choose a time zone by clicking the “Change” button.

4. Shut down your browser and open it again. Next, attempt to revisit the website.

Mac

1. Select “System Preferences” from the Apple menu.
2. Select the Date & Time icon. In case the padlock is located at the bottom of the window, you may have to click on it and input your administrator username and password.
3. Choose the option for “Automatically set date and time.” This will automatically synchronize with an Apple NTP server.
4. Choose the tab for the Time Zone. If it doesn’t automatically detect your location, just uncheck it to set it manually. Choose your time zone area and city on the map.
5. Shut down your browser and then open it again. Returning to the website.

5. Attempt using the Incognito Mode.

Our usual advice would be to clear the cache of your browser next. Nonetheless, many of us find it challenging to do so. 😉 To determine if it could be your browser cache, you can simply open your browser in incognito mode without clearing the cache. Try using a different browser to determine if you continue to encounter the “your connection is not private” message. Also, don’t dismiss Chrome extensions. However, this will assist you in testing it.

“New private window” is how Mozilla Firefox refers to its incognito mode. We call it “New InPrivate Window” in Microsoft Edge.

6. Delete Cookies and Cache from Browser

It’s always a good idea to clear your browser’s cache if you suspect that the problem is with your browser before moving on to more detailed troubleshooting. Here are the steps to follow in each of the different browsers:

• How to Force Refresh a Single Page for All Browsers
• How to Clear Browser Cache for Google Chrome
• How to Clear Browser Cache for Mozilla Firefox
• How to Clear Browser Cache for Safari
• How to Clear Browser Cache for Internet Explorer
• How to Clear Browser Cache for Microsoft Edge
• How to Clear Browser Cache for Opera

7. Consider Using Your Computer to Clear the SSL State

Although it’s simple to attempt and frequently goes unnoticed, clearing the SSL state in Chrome may be quite helpful. This can be helpful if anything goes out of sync, much as clearing the cache on your browser. To clear the SSL status on Windows Chrome, take the following actions:

1. After selecting the Google Chrome – Settings (Settings) icon, select Settings.
2. To view the advanced settings, click Show.
3. Click Change Proxy Settings under Network. The dialog box for Internet Properties opens.
4. Select the Content tab.
5. After selecting “Clear SSL state,” click OK.
6. Restart Chrome.

8. Swap DNS servers

Changing your DNS servers is the next thing you can attempt. We’ve observed that utilizing Cloudflare’s DNS (1.1.1.1 and 1.0.0.1) or Google’s Public DNS (8.8.8.8 and 8.8.4.4) might result in the “your connection is not private” issue. Removing this and reverting to your ISP’s DNS servers will occasionally cure DNS issues. Unfortunately, neither Google nor Cloudflare are flawless all the time, and occasionally problems arise.

To accomplish this on Windows, make sure that “Obtain DNS server address automatically” is checked under Network Connection Properties. You might also need to take it down from your router if you added Cloudflare’s or Google’s Public DNS to it.

9. Turn off your antivirus and VPN temporarily.

VPNs and antivirus programs occasionally clash with or override your network configurations, which may include preventing specific SSL connections or certificates. Whether any are open, try shutting them down or temporarily deactivating their “SSL Scan” function to see whether it fixes the Chrome problem “your connection is not private.”

10. Verify that the certificate is still valid.

Unbeknownst to the website owner, SSL certificates frequently expire. Quite a bit more, than you may imagine. Even to Fortune 500 businesses! In just a few seconds, we were able to locate the tweet below. It’s only that Huntington Bank neglected to renew their SSL certificate, nothing major.

Usually, one of the following causes this to occur:

• Neither the SSL certificate supplier nor the domain registrar have auto-renew enabled for the owner of the website.
• The user has neglected to change their payment method, resulting in payment failure even when auto-renew is set. Throughout the year, users usually switch credit cards more often than they go into their domain registrar’s dashboard.
• The owner of the website utilizes a free certificate from Let’s Encrypt, which expires often. They either forget to renew it or don’t have a script in place to do so. Cloudflare SSL can be used at Kinsta to automatically safeguard WordPress websites, eliminating the need for clients to worry about their free SSL certificates expiring.

As a result, the following error code is produced: ERR_CERT_DATE_INVALID in NET.

When using Chrome DevTools, you may quickly find out when a certificate expires by opening it while on the website. Select the “View certificate” option after selecting the security tab. The certificate information will display the “Valid from” dates.

In Chrome, clicking on the padlock in the address bar offers an additional fast and simple method to view a website’s SSL certificate information. Next, choose “Certificate.”

11. Verify the Subject’s Alternate Domain

The Subject Alternative Name is a feature that is unique to each certificate. This covers every domain name variant that the certificate is valid for and is issued to. The distinction between https://domain.com and https://www.domain.com—which functions similarly to a subdomain—must be noted.

A certificate that is not correctly registered on both domain versions may be the cause of an associated error code, such as SSL_ERROR_BAD_CERT_DOMAIN. These days, this is less frequent because most websites have HTTPS redirects in place.

This might occur even if you simply switched domain names. For instance, maybe you recently obtained that new .com domain and transitioned away from your previous one. Forgetting to add an SSL certificate to your new domain will likely result in a NET::ERR_CERT_COMMON_NAME_INVALID error.

12. Does the Certificate utilize SHA-1 encryption?

The SHA-1 algorithm used to be popular among SSL certificates on the internet for security purposes. Due to the weakness exhibited by SHA-1, it is no longer supported in any modern browser. If a website continues to use a certificate with this outdated algorithm, the “your connection is not private” error message will be displayed.

•  Chrome 56 (January 2017) saw Google Chrome discontinuing support for SHA-1.
• Firefox 51 (February 2017) will no longer support SHA-1, as announced by Mozilla Firefox.
• In January 2017, Microsoft declared that they would be preventing the use of SHA-1 signed TLS certificates.

The majority of certificates currently employ SHA-256 hash algorithms. You can locate this information by clicking on the “Details” tab while examining a certificate on a website.

13. Is Symantec the Issuer of the Certificate?

The public was made aware of several unethical actions by Symantec regarding the issuance of certificates back in January 2017. In essence, they did not meet the fundamental CA/Browser forum standards that are industry standard. It also found out that this was something they had known for a while. Browsers decided to stop supporting Symantec-issued certificates as a result. An error message stating “your connection is not private” may show up if a website is still utilizing a certificate that was issued by them.

The following chronology is currently being developed:

• Google Chrome Symantec timeline
• Symantec timeline for Mozilla Firefox
• Microsoft has not yet released an official comment, but it is quite probable that they will follow suit.

Using a Symantec certificate can result in the accompanying error code: NET::ERR_CERT_SYMANTEC_LEGACY.

14. Conduct a test on a server running SSL.

If you are uncertain about the configuration of a website, you can conduct an SSL server test to verify everything is set up correctly. To set up SSL/TLS certificates, it is necessary to install not only the primary certificate but also the intermediate certificates (chain). If these are not configured correctly, visitors may receive a browser warning, potentially causing them to leave. Depending on the browser and its version, you might not receive a warning about your incorrectly set up certificate.

We suggest utilizing the SSL check tool provided by Qualys SSL Labs for free. We rely on it heavily for verifying certificates for all Kinsta clients due to its high level of reliability. Just go to their SSL verification tool, enter your domain in the Hostname section, and press “Submit.” If you want, you have the choice to conceal public results. The scan could last up to a minute or two but it will reveal all the intricate information about a site’s SSL/TLS setup.

See our comprehensive guide for a few things to look out for while doing an SSL test.

15.  Make sure to keep your operating system up to date.

Aging operating systems become obsolete as newer technologies like TLS 1.3 and the most recent cipher suites are no longer supported by browsers. Certain elements in the most recent SSL certificates will cease functioning abruptly. Google Chrome ceased support for Windows XP in 2015. We suggest upgrading to the latest operating system when feasible, like Windows 10 or the newest Mac OS X version.

Ensure that your device is current on either Windows, Mac or any other operating system.

16. Reboot your computer

It may be frustrating, but we have to point out that if none of the previous choices are effective, consider restarting both your computer and your router. 😬 We understand that many of you may have numerous tabs or applications running, which is why we placed this as one of the final choices. However, restarting devices effectively eliminates many temporary cache and hiccups.

17. Seek assistance when needed

Are you still encountering the “your connection is not private” error message? Do not hesitate to seek assistance by reaching out and asking for help. If you come across this on your website, you are welcome to submit a ticket to our Kinsta support team. We can assist you in figuring out the reason for this occurrence and whether it is a problem originating from your website.

The Google Chrome Help Forums are also particularly useful! You can be certain that there are users who have faced the same error or bug before, and they are willing to assist.

Do the following instructions for the same outcome by using the same language and maintaining the word limit of

18. Turn off Chrome’s SSL certificate verification feature.

You can disable SSL certificate checking in Chrome as well. Nevertheless, it is important to emphasize that this is solely intended for testing and development purposes. Only use the provided options if you are completely familiar with their functions.

Permit Null Certificates from the local host.
You may be able to utilize the Chrome setting to merely accept insecure connections from localhost while testing locally. Go to chrome://flags/ in Chrome. You should be able to choose “Allow invalid certificates for resources loaded from localhost” after searching for “insecure.” After turning on that feature, restart your browser.

Turn off Chrome to Verify Every SSL Certificate.

You may give the following at the command line on launch to instruct Chrome to disregard all SSL certificate issues. Just do a right-click to access the launcher’s properties if you’re using Windows. Then, in the target box, add –ignore-certificate-errors. Next, restart Chrome.

Conclusion

Troubleshooting browser issues can be challenging at times and is never enjoyable. Hopefully, one of the aforementioned solutions will enable you to swiftly fix the “your connection is not private” problem. Recall that they are usually the result of a misconfigured certificate on the website or anything wrong with your PC.

You can also read our related article: 

How Old is Google?