Is your browsing screen covered with “your connection is not private?” Google features security measures to protect users from suspicious sites. It comes into action when users are about to commit a mistake.
The “your connection is not private Chrome” error serves as a warning when they try to browse an unsecured website. Here, Chrome comes in and restricts the connection until you are able to sort out things.
Most of the time, this error is a part of security measures taken up by Chrome. However, sometimes, Chrome even blocks trusted sources.
Here, we are going to discuss some effective ways that you can use for fixing the “your connection is not private” error.
Also, read about what actually causes this issue and how you can prevent it from happening in the future. Before that, let’s see what this error is about!
What does “your connection is not private” mean?
The error “your connection is not private” pertains only to websites that run over HTTPS. When users visit these websites, their browsers send a request to the server that hosts the site.
After that, the browser needs to validate the installed certificate on the website for ensuring that it is updated as per the recent privacy standards.
Apart from that, other things that occur include TLS handshake, checking of the certificate by the certificate authority, and also the certificate decryption.
If your browser detects that the certificates are not valid, it automatically tries to prevent users from browsing the website. It is an in-built feature in various browsers for protecting users.
If these certificates are not set up accurately, this shows that data could not be encrypted correctly, and thus, the website is not secure to visit, particularly ones involving logins or payment processing.
So, instead of loading the website, you come across errors like “your connection is not private Chrome.”
In Google Chrome, this error appears as “your connection is not private,” and also, “attackers might be trying to steal your information from domain.com (for example, passwords, messages, or credit cards.” It is even accompanied by error code messages that help you in pinpointing the accurate problem.
Here are some of the common errors that you might experience in Chrome:
- SSL certificate error
- NET::ERR_CERT_COMMON_NAME_INVALID (it shows up when certificates do not match domains)
- ERR SSL VERSION OR CIPHER MISMATCH
So, if you are seeing the “your connection is not private” error on Windows PC in Google Chrome, you are not alone. Most Windows users have experienced this issue before. Luckily, there are various fixes to get rid of this issue, which are very easy to follow.
PS: Click to learn more about how to fix Chrome Being Slow easily.
Different Solutions to Resolve “Your connection is not private Chrome”
Several users do not know where they should begin if they come across the error, “Your connection is not private.” Usually, errors like this occur due to two things, which include client-side issues (like your computer, browser, OS) and problems related to the website’s certificates (like wrong domains, expired, untrusted by organizations).
Here, we are going to deal with both of these problems. So, below are various recommendations and tricks that you can follow for fixing this connection error. Note that you do not need to try all of these fixes, just work down from the top until you arrive at the one that works for you!
Besides, here, you will figure out how to fix YouTube keeps buffering.
1. Reload the Page to Fix ‘Your Connection Is Not Private’
This is the first and easiest thing that you need to try on encountering the error “your connection is not private Chrome” on your browser. Firstly, you need to close your browser and then open it for reloading that very page.
Alternatively, you can even refresh the webpage by pressing the ‘Refresh‘ tab or the ‘F5‘ key. It is possible that the site owner might be presently reissuing the SSL certificate. Or else, something was not functioning well in Chrome.
2. Proceed Manually
Another thing that you need to try is to proceed manually. However, this method is not recommended unless you understand nothing would be encrypted if followed. In case you are going to enter some payment details or login credentials, it is best to move on to the next method. We include this method so that you understand the consequences of performing this action.
Experiencing this error can mean that someone is trying to dupe or steal information that you offer to that server. In that case, you need to immediately close the website. It is even possible that these sites have been compromised due to some malicious redirections. If you happen to be in a public area, do not try to bypass the screen.
Users who still like to proceed should go with the link “Proceed to domain.com” that you will find at the screen’s bottom. Sometimes, this option turns out to be under the option ‘Advanced.’ In case the site is employing the HSTS, then you would not see this option as they implement an HTTP header that does not enable non-HTTP connections.
3. Locations like Airports or Cafes
It sounds a bit odd, but the airport and cafe Wi-Fi networks turn out to be the most popular locations, where users come across the error “your connection is not private Chrome.”
This is so because lots of them do not run all things over HTTPS, or they are not correctly configured. Usually, this pertains to the screen, where you have to accept terms and conditions for signing in.
When you try connecting to secure HTTPS sites before you accept these terms, the issue pops up. Below are several simple steps for getting around it.
- a. Try connecting to the Wi-Fi of airports or cafes.
- b. Browse non-HTTPS websites
- c. When the sign-in page opens up, accept the agreement, and try logging in. As the terms consist of a checkbox, do not be concerned if it runs over HTTPS. When connected, browse websites over HTTPS. If you come across no sign-in window, then type 184.108.40.206 into the browser.
- d. Whenever you use public Wi-Fi, VPNs could protect you by hiding the traffic. Some popular VPNs are NordVPN, TunnelBear, Private Internet Access, etc.
4. Examine the Clock
This is another common reason behind “your connection is not private” could be the messed-up clock of your computer. Most browsers rely on the clock for syncing up correctly to examine SSL certificates.
It could occur when you buy a new laptop or computer. They do not sync up after the first login automatically. Here are a few steps for updating the clock on your system. Please note that this issue can even occur on smartphones.
a. Right-tap on time at the bottom task tray.
b. Choose the ‘Adjust date/time‘ option.
c. Click ‘Set time automatically‘ and even ‘Set time zone automatically.’ It will update as per the NTP servers of Microsoft. Cross-check your time for making sure it is accurate. If not, tap on the tab ‘Change‘ to choose the time zone manually.
d. Close the browser and open it again. Now, revisit the site to see if your issue has been fixed or else, move onto the next method.
5. Try Incognito Mode
It is recommended to clear the cache of your browser. However, it is very easier for us to say than to do so. If you like to examine if the error “your connection is not private Chrome” is happening due to the browser cache, then you should try opening up the incognito mode in your browser.
To perform this action, press the keys ‘Ctrl+Shift+N‘ simultaneously on the keyboard of your system for opening an incognito mode. Now, enter the site that you want to visit. If that webpage opens up fine, it means that there must be some extension due to which this issue is occurring.
For this, tap on the icon ‘Menu’ present in the right corner and choose ‘Settings.’ Now, click on ‘Extensions‘ for opening up a list of Chrome extensions.
If you see some extensions interfering with the SSL connection, then find it and un-check the box next to the ‘Enable‘ option for disabling that extension. Or else, try other browsers and check if the issue still persists. Do not even rule out the extensions of Chrome.
6. Clear Cookies and Cache of Your Browser
If you actually think that the error “your connection is not private Chrome” is due to the browser, then clearing the cache of your browser seems to be a great troubleshooting option before you dive into more troubleshooting ideas.
One can clear cookies and cache from the ‘Settings‘ of your browser. After clearing the cache and cookies of your browser, check if the error has been wiped off or not.
7. Clear the Browsing History
Another thing that you can do is to clear the browsing history. For this, open your Chrome browser and tap on the three dots at the right. From there, choose ‘Settings‘ and then scroll down to get to the option ‘Show Advanced Settings.’
Next, navigate to the section ‘Privacy‘ and tap on the tab ‘Clear browsing data.’ Choose the data that you like to delete and press the tab ‘Clear browsing data.’ Lastly, restart the browser and check if the issue persists.
8. Clear the System’s SSL State
Users overlook clearing the system’s SSL state. However, it comes handy and is very simple to try. It helps when things go out of sync. This process is pretty similar to clearing the cache of your browser.
To clear the SSL state, go through the instructions as follows:
- a. Open Google Chrome and tap on the icon ‘Settings.’ After that, select ‘Settings.’
- b. Tap on ‘Show Advanced Settings.’
- c. Within the ‘Network‘ tab, choose ‘Change Proxy Settings.’ Now, a dialog box for Internet Properties will appear on the screen.
- d. Select the tab ‘Content.’
- e. Next, choose ‘Clear SSL State‘ and press O.K.
- f. Now, restart Google Chrome
Hopefully, you would not see the error “your connection is not private Chrome” on your system anymore while browsing the website. If no relief, the next method is what you need to follow for fixing the error “your connection is not private” on your Chrome browser.
9. Modify DNS Servers
Another thing that you can try to fix the error ‘your connection is not private’ is modifying the DNS servers. This issue occurs when you use Public DNS (220.127.116.11 and 18.104.22.168) of Google or DNS (22.214.171.124 and 126.96.36.199) of Cloudflare. Sometimes, you can fix the error by removing these servers and restoring the default DNS servers of your ISP.
For doing this, visit the network connection properties and ensure to select ‘Obtain DNS server address automatically.’ Steps for the same are listed as follows:
a. Open the Control Panel on your Windows system.
b. After that, navigate to the tab ‘Network and Sharing Center.’
c. Now, choose the option ‘Change Adapter Settings‘ from the listed options.
d. Then, right-tap on your network and select the option ‘Properties.’
e. When a new window pops up, visit the tab ‘Networking.’
f. Tick mark the box against ‘Internet Protocol Version 6 (TCP/IPv6)‘ or ‘Internet Protocol Version 4 (TCP/IPv4)‘. When it’s done, tap on ‘Properties.’
g. When another window shows up, mark the box against ‘Obtain DNS Server Address Automatically‘ under the tab ‘General.’ Now, check if your issue has been resolved or not.
10. Temporarily Disable Antivirus and VPN
Sometimes, Antivirus and VPNs could override or conflict with the network settings, comprising blocking several SSL connections or certifications.
If any of them is running, disable them or turn off the feature ‘SSL Scan‘ to check if the “your connection is not private” issue resolves in Chrome or not.
Also, one more thing that users can try is to modify some settings in their antivirus programs. If you are sure that the website that you like to visit is completely free of certain viruses, spam, or malware, they can try modifying some settings, such as switching off the scan SSL, for visiting those sites.
If you could not find these settings, you can disable over-sensitive antivirus software for a specific time period. It is advisable to go for this open when you truly believe the sites are pretty safe to browse.
11. Ensure the Certificate Has Not Expired
The expiration of SSL certificates occurs without the knowledge of the website owner at all times. Most of the sites even forget to renew their SSL certifications every now and then.
It occurs when the owner does not enable the auto-renew feature with the SSL certificate provider or domain registrar. So, this ends up in the ‘NET::ERR_CERT_DATE_INVALID‘ error code.
One can check the expiration date of a certificate by opening ‘Chrome DevTools‘. Then, tap on the tab ‘Security‘ and click ‘View Certificate.’ Now, choose the dates ‘Valid from‘ to see the certificate information.
There’s another simple and quick way to get the SSL certification information. Here, you need to tap on the padlock within the address bar and tap on the ‘Certificate‘ option.
12. Examine Subject Alternative Domain
Every certificate features the Subject Alternative Name. It comprises all domain name variations that tell about for which that certificate is valid and issued.
Please note that https://www.domain.com and https://domain.com are separate domains. If you come across accompanying error codes like ‘SSL_ERROR_BAD_CERT_DOMAIN,’ it means that the certificate isn’t registered on both the variations.
It could even occur when you change the domain names. For instance, when you acquire a new address and move from the old domain. So, if you forget to install the SSL certification on the new domain, then the error ‘NET::ERR_CERT_COMMON_NAME_INVALID‘ could occur.
13. Is Your Certificate SHA-1?
SHA-1 refers to a cryptographic hash algorithm, which SSL certifications commonly use on the internet. Due to some weaknesses, various browsers do not support this algorithm.
If some website is using this, then you can face the “your connection is not private Chrome.” Several certificates employ SHA-256 algorithms, which you can check within the tab ‘Details‘ while inspecting the website’s certificate.
14. Symantec-Issued Certificates
Symantec does not comply with the standard browser forum requirements. Due to this, various browsers do not support Symantec-issue certificates.
If some websites are using these certificates, then you can probably come across the ‘your connection is not private’ error. When this issue occurs, you will see the ‘NET::ERR_CERT_SYMANTEC_LEGACY‘ error code.
15. Run SSL Server Tests
If you are not sure whether everything on your or someone else’s website is set up accurately, it is best to run SSL server tests. TLS/SSL certificates need not just the main certificate, but you also have to install intermediate certificates.
When you do not set them up accurately, visitors will get warnings in their web browsers, which are definitely going to blow them away. Based on the version and browser, you might see the warning yourself if certificates are incorrectly set up.
Thus, we recommend you employ free SSL check tools. When you will open any free SLL tool, put in the domain in the provided field and tap on ‘Submit.’ Plus, you can even choose an option for hiding public results. This scan will take a few minutes and provide you with fine information related to the site’s TLS/SSL configuration.
16. Update the Operating System
It is another impressive method to resolve the error “your connection is not private Chrome.” The operating systems become outdated with time when newer technologies like TLS 1.3 or the recent cipher suites emerge.
Certain components in SSL certificates will stop working too. So, it is best to update your OS to the latest version, such as Windows 10.
17. Restart the System
If none of these above-mentioned methods work for you, you need to simply restart the computer. Sometimes, restarting your system and the router helps you in resolving errors like “your connection is not private Chrome.”
Most users have lots of applications and tabs open at times, and thus, this option seems pretty right. Also, rebooting systems will clear out lots of junk files and temporary cache.
18. Reach out to Help
Are you still struggling with the “your connection is not private” error? Then, do not step back from reaching out and asking for help.
You can even take the help of Google Chrome Help Forums, where hundreds of users might have experienced a similar issue or bug. So, go ahead and look for solutions!
19. Disable ‘Chrome Checking SSL Certificates’
Users can even disable the ‘Chrome Checking SSL Certificates‘ option. This method is just meant for development and testing purposes. It is recommended to follow this procedure if you are completely sure what you are doing.
First, go for ‘Allow invalid certificates from localhost.’ Here, if you are locally testing, you need to employ the flag of Chrome for allowing the localhost’s insecure connections.
In Google Chrome, browse for Chrome://flags/ and then, look for ‘insecure.’ Now, you will see the option for ‘Allow invalid certificates from localhost.’ You need to enable this option and start the browser again.
Now, it is time to ‘Disable Chrome Checking All SSL Certificates.’ Here, you will ask Chrome to stop checking SSL certificate errors at launch. For this, right-tap on the launcher’s Properties and add ‘ignore-certificate-errors‘ in the target column. Lastly, start Google Chrome again.
Browser errors are not at all fun and can be too difficult to handle at times. Hopefully, one method out of all mentioned above will assist you in fixing the error “your connection is not private” effectively and quickly.
Just remember that errors like these usually happen when there is something misconfigured with the website’s certificates or on your computer. Now, use these different solutions to get rid of this annoying issue as soon as possible!