How to Resolve Your Connection Is Not Private Error On Chrome?

your connection is not private

 It is the 21st century – the era of modernism and advancement. We are diving in the sea of technology. The technology put us at ease. Your connection is not private, but on the other hand, it also caused us many troubles. Our privacy is not any more secured completely. We are prone to hackers – data thefts.

When we open the browser, our screen pops up with an error message, “your connection is not private.” Your browser sends this message. It is prompt and informs you that your connection is not secure. If it is not private, then definitely your device will work as a gold mine for the hackers.

The connection between the clients and servers remains no more encrypted. Hence the hackers can see what users do on the website. When the client and server communicate if the encryption is not made, then texts are sent as plain text. However, not even the client can know whether he is connected to the right server. So, your browser sends you the prompt. 

There are some digital certificates installed on the servers to ensure privacy standards and safe website experience. If the browser will find any error with the digital certificate, your access is denied.

Such certificates are also named as public critical infrastructure. Identity certificates offer proof that the website is what they declared. These certificates protect confidential data like personal info, passwords, and payment information. Error in the SSL certificate is the main reason behind the prompt. 

SSL (Secure Socket Layer) certificate serves to secured HTTPS connections.

Errors occur when the connection is not secure. The following are the reasons behind the failure.

  • An expired or missing certificate
  • Outdated Browser
  • Date and Time settings or antivirus settings are off 
  • Server issue

If the fault is of the server, then we can only wait until the server solves it.

How Google Chrome sends you errors

The error doesn’t appear the same always, and it comes in variations. Variations sometimes occur because of the type of browser you are using or the version of the operating system. Sometimes, the configuration of the certificate is also validated by the error shown. The troubleshooting steps can be the same, but mistakes sometimes convey slightly different meanings.

In the case of Google Chrome, if an error occurs while validating the certificate, the screen pops up with “your connection is not private.” Hackers might be striving to steal the info from domain.com like examples, messages, credit cards, or passwords).

It is also accompanied by an error code message which aids to try and pinpoint the exact issue.

The most common error codes you can notice in Google Chrome are:

  • NET:: ERR_CERT_COMMON_NAME_INVALID (if certificate don’t match the domain registered) 
  • NET::ERR_CERT_DATE_INVALID
  • NET::ERR_CERT_AUTHORITY_INVALID
  • SSL certificate error
  • ERR_CERT_SYMANTEC_LEGACY
  • ERR_SSL_VERSION_OR_CIPHER_MISMATCH
  • NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
  • NTE:: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED 

 

Learn way about How to Resolve Your Connection is Not Private Error on Chrome

When your access is denied, and you see an error, you feel at in a vacuum. You fail to configure your first step after seeing the prompt. There could be two main reasons behind the origin of errors. Firstly, it can be a client-side issue (OS, browser, computer). Secondly, there is an issue with the certificate on the website (if its expired, wrong domain, trust issues with the organization). Let’s hit both one by one.

Below are recommendations on how to resolve the issue. 

Try Reloading the Page

It is an obvious but most comfortable way that you can try if you encounter “your connection is not private.” In this way, you are jointly and re-opening the browser and reloading the page. It explains that whether the server is reissuing its SSL certificate.

Manually Proceed (Unsafe)

If reloading doesn’t solve the issue, you can manually proceed. Well, it is not recommended unless you get this thing in mind that proceeding will not make everything encrypted. Kip to the below steps if you intend to enter in log-in credentials or payment details. This option must not be tried because error alarms you that someone is going to fool you.

It may be the case that the requested website has been compromised, and there is a malicious redirection. Stay more alarmed if you are in public – better not to bypass the screen.

But if you still want to try this, generally, “Proceed to domain.com” link can be hit at the bottom of the error screen. As per the type of browser you are using, this option is hidden under the “Advanced” option. The websites using HTTP Strict Transport Security (HSTS), don’t let you proceed. It merely shows that the HTTP header is implemented, and it never allows the non-HTTP connection.

Are You in a Cafe or Airport?

If you are at a café or airport and using Wi-Fi networks, this might occur. It typically occurs in such cases that “your connection is not private.” It happens because all of them do not run everything over HTTPS. Sometimes configuration issues arise as well. It usually refers to the portal screen.

On the portal screen, you accept the terms and agreements before signing in. Accessing the HTTPS site without taking the portal’s terms can again cause the error to occur.

You can get out of this by doing these things.

  • Accept the terms and conditions
  • Connect to a local Wi-Fi network 
  • Browse any non-HTTPS site. 

On the screen, a sign-in page will open. Before logging in, accept the terms. Once you are done establishing a connection, you can browse HTTPS sites. Try typing 1.1.1.1 in the browser if you get the sign-in page. You can protect your data more while using public Wi-Fi if you use a VPN. 

Check Your Computer’s Clock

When your computer clock is not working accurately, the error of “your connection is not private” can pop up the screen. Your browser undergoes synchronization to verify the SSL certificate.

This generally occurs if it is a new computer or laptop on Wi-Fi for the first time. Usually, after the first login, no automatic sync occurs. Set your date and time while selecting “Set time automatically” and optionally “Set time zone automatically.” After updating, close the browser and open again. Revisit the website. 

Try in Incognito Mode

Next, clear the browser cache. Open the browser in incognito mode, without making the cache. You can also test other browsers but don’t rule out Chrome extensions. 

Check Subject Alternative Domain

Every issue certificate owns what they name as the Subject Alternative Name. It encompasses the details of the domain name variations. It is significant to consider that https://domain.com and https://www.domain.com are dealt with as two separate domains (just like a subdomain).

If you notice a complementary error code like SSL_ERROR_BAD_CERT_DOMAIN, then the certificate is not registered correctly. It is not applicable for present cases because now generally, sites use HTTPS redirects. It also happens if you changed the domain name but forgot to install an SSL certificate. Below error code appears on the screen.

NET::ERR_CERT_COMMON_NAME_INVALID

Clear Browser Cache and Cookies

If you consider that it might be your browser, clear the cache as it is better. Before going too in-depth troubleshooting, it is a good step.

Attempt to Clear the SSL State on Your PC

You can easily try clearing SSL state in Chrome. It is the same as you clear the browser cache. Follow the below-described steps.

  • Launch Google Chrome, navigate to the settings icon, and click on it.
  • Hit “Show advanced settings” under settings. 
  • Click on change proxy settings under the section network. A new dialog box will appear showing Internet Properties. 
  • Hit the Content tab. 
  • Now to clear SSL State, hit on ‘Clear SSL State’ and click OK.
  • After it re-launch your chrome. 

Change DNS Servers

If all of these solutions didn’t work than you can look for changing the DNS servers. If you are using Google Public DNS (8.8.8.8 and 8.8.4.4) and screen pops up with “your connections not private”. Rove it and reset to default settings (ISP’s DNS servers). To update DNS settings, go to the network connection properties and ensure ‘Obtain DNS server address automatically’ is opted. If Google’s Public DNS is added to your router, remove it from there as well.

Update Your Operating System

As the technology has been updated, so older O.S. has also gone outdated. Browser no more supports them and particular components in the SSL certificate will also not work. So, it is good to upgrading the O.S. like for windows, at least Windows 10.

Disable VPN and Antivirus Temporarily

It happens that the installed antivirus and VPNs override your network settings. They can block certain SSL certificates. Disable the running software or turn off their ‘SSL Scan’ feature. It can fix ‘your connection is not private’ in Chrome.  

Is the Certificate Issued by Symantec?

In January 2017, public awareness was created on Symantec’s part that how they issue certificates. Industry-standard CA/browser forum baseline requirements were unfulfilled.  Hence, browsers denied the certificates issued by Symantec. If the website still uses certificates issued by Symantec, the screen pops up with ‘your connection is not private’. On the screen following codes will appear,

NET:: ERR_CERT_SYMANTEC_LEGACY. 

Make Sure the Certificate Hasn’t Expired

Sometimes it happens that the SSL certificate expires without letting the owner know. It happens if the owner disabled auto-renew or it is enabled, but the payment method is not updated.  The owner of the website generally uses a free Let’s Encrypt certificate. The validity duration is 90 days. If this is the reason, then below code appears on the screen.

NET::ERR_CERT_DATE_INVALID 

To check the expiry date of the certificate, open Chrome DevTools while being on the site. Under the security section tap on ‘view certificate’ and then on the certificate, you will find ‘valid from’ date. Another quick way to access is that you click on the padlock in the address bar and tap on the certificate.

Is the Certificate SHA-1?

Error ‘your connection is not private’ pops up if any website is using SHA-1. A cryptographic algorithm – SHA-1 was used by SSL certificates on the web. It is not supported in the current browser now. Many of the SSL certificates now use the SHA-256 hash algorithm.

Run an SSL Server Test

An SSL server test can be performed. Intermediate certificates must be installed along with SSL/TSL certificates. If the setup is done incorrectly, you see it but also it depends on the browser and version. You can use any trustworthy SSL check tool. You need to input the domain into the hostname field and submit it. Scanning can take 60 or 120 seconds but reveal all the fine details.

Conclusion 

Troubleshooting a browser can get hard. If you are experiencing the error while accessing the websites, the above-described ways can help you. The error ‘your connection is not stable’ can be solved. The typical cause lies in the configuration on your device or in the site certificate.

FAQs 

Q) Why the chrome, again and again, pops up with the error message ‘your connection is not private’?

When chrome, again and again, shows you this message, then it means it is stopping you from accessing the untrusted site. It usually appears when the SSL certificates are not validated. You need to configure the issue and fix it soon. 

Q) What is meant by that ‘your connection is not private?

Your page-load request is rejected by the browser as the site is trying to serve the HTTP connection while accepting the user information. Such HTTP connections are not acceptable if web browsers run with strict privacy policy. As per your security concerns, browsers prompt you, otherwise, the attackers will harm your privacy.  

Q) What are the reasons that my browser is denying my access to the websites?

SSL (Secure Socket Layer) certificate serves secured HTTPS connections. Errors occur when the connection is not secure. The following are the reasons behind the error.

  • An expired or missing certificate
  • Outdated Browser
  • Date and Time settings or antivirus settings are off 
  • Server issue

If the fault is of the server, then we can only wait until the server solves it.

 

Leave a Reply

Your email address will not be published. Required fields are marked *