The error notice “your connection is not private” means what it says. It’s a warning notice from your browser indicating the connection isn’t secure.
It Implies that if you don’t use an antivirus or encryption, hackers will find your gadget a gold mine.
In this article, we will teach you how you can solve this error.
- 1 What Is the Meaning of the Error “Your Connection Isn’t Private”?
- 2 What does the phrase “Your connection is not private” mean?
- 3 How to Resolve the Your Connection Isn’t Private Error.
- 3.1 Try refreshing the page.
- 3.2 Proceed Manually (Unsafe)
- 3.3 Are you in a restaurant or an airport?
- 3.4 Confirm Your Computer’s Clock
- 3.5 Windows
- 3.6 Mac
- 3.7 Experiment with Incognito Mode
- 3.8 Delete the Browser’s Cache and Cookies
- 3.9 Attempt to Clear the SSL State on Your Computer
- 3.10 Alter DNS Servers
- 3.11 Temporarily disable VPN and Antivirus
- 3.12 Make Sure the certificate hasn’t expired
- 3.13 Examine Subject Alternate Domain
- 3.14 Is the certificate SHA-1?
- 3.15 Carry out an SSL Server Test
- 3.16 Reboot Your Computer
- 3.17 Disable Chrome’s SSL Certificate Validation
- 3.18 Allow Unauthorized Certificates from localhost.
- 3.19 Disable Chrome’s checking of all SSL certificates
- 4 CONCLUSION
What Is the Meaning of the Error “Your Connection Isn’t Private”?
The “your connection is not private” error will be displayed only on HTTPS-enabled sites. When you view a website, your browser sends a request to the server that hosts it. The browser must check the certificate loaded on the site to ensure its authenticity.
It complies with current privacy regulations. The TLS handshake is one of the other things that happen. The certificate is validated against the certificate authority and decrypted.
Suppose the browser determines that the certificate is invalid. It will attempt to block you from accessing the site automatically.
It safeguards the user; web browsers include this function. If the certificate isn’t correctly set up. It implies that it cannot be adequately encrypted data.
As a result, visiting the site is risky, rather than loading the website. It will show an error message. Such as, “Your connection is not private.”
What does the phrase “Your connection is not private” mean?
Your browser examines a website’s digital certificates before entering them to make sure they satisfy the criteria. And will keep your personal information protected.
Contact information, passwords, and payment methods, for example, are generally encrypted.
The Secure Sockets Layer (SSL) certificate is usually blamed for the “your connection is not private” issue. It is necessary for HTTPS-enabled sites (connection security) if your browser cannot validate an SSL certificate.
It prohibits you from visiting the site by presenting an error message stating that “Your connection is not private.”
The reasons for an SSL certificate’s inability to be validated vary. The certificate might be missing entirely, expired, or improperly set up. It means the site isn’t doing an excellent job of protecting your personal information.
Regardless of what caused the SSL hiccup. It is the responsibility of the website’s owner to correct the problem. Your browser or device settings may be causing you problems.
Furthermore, you are unable to communicate with the website you are trying to visit.
Fortunately, you can usually solve this problem on your own. And for each browser, the processes are essentially the same.
Error Variations: Your Connection Isn’t Private
Depending on the circumstances, there are many distinct versions of this mistake.
What web browser do you use, and what operating system do you have installed? And even the certificate setup on the servers.
While some of these blunders have slightly different meanings, the troubleshooting steps are frequently the same.
If there is a problem verifying the certificate in Google Chrome, the error message will read, “Your connection is not private.”
It is also followed by an error code notice, which aids in determining the specific cause of the problem. The following are a few of the most frequent error codes that you may see in Google Chrome:
ERR CERT SYMANTEC LEGACY
NET::ERR CERT AUTHORITY INVALID
NET::ERR CERT COMMON NAME INVALID (This happens when the certificate doesn’t 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
In Mozilla Firefox, the error message is somewhat different, and instead of “your connection is not private,” you’ll get “your connection is not secure.”
Firefox displays a warning that your connection is not secure (Image source: Firefox Help)
An error code notice accompanies it, much as in Chrome, to help you figure out what’s wrong. The following are a few of the most frequent error codes that you may encounter in 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
In Microsoft Edge, the error message is “Your connection isn’t private.”
These are accompanied by an error code notice as well. Here are some of the most common error codes:
NET::ERR CERT COMMON NAME INVALID
Error Code: 0
DLG FLAGS INVALID CA
DLG FLAGS SEC CERT CN INVALID
In Safari, the error message will be “Your connection is not private.”
How to Resolve the Your Connection Isn’t Private Error.
You might not even know where to begin at times. If you receive an error stating that “your connections are not private.” These mistakes, in our experience, are generally caused by two factors.
The first is a problem on the client’s end. The second is that there is a genuine issue with the website’s certificate. So we’ll do a little bit of both.
Try refreshing the page.
Some may think this is self-evident. When experiencing a “your connection is not private” issue, one of the simplest and first things you should do is close and reopen your browser.
Also, try refreshing the page. The website owner may be in the process of reissuing their SSL certificate. Or something was wrong with your browser.
Proceed Manually (Unsafe)
The second option is to proceed manually. We never recommend something unless you are well aware that nothing will be encrypted if you move.
Suppose you’re going to input login information. If you don’t want to input payment information, you may skip to the following steps below.
We only provide this option so that we can fully explain the implications of doing so. We see this mistake might indicate that someone is attempting to deceive you.
Alternatively, they can steal whatever information you submit to the server. In most cases, you should also instantly close the webpage. It’s also conceivable that the website is hacked. There is also a harmful redirection.
Never try to circumvent this screen in a public area.
If you still want to go, a link typically says “Proceed to domain.com.” You may do this by clicking at the bottom of the error screen. Depending on the browser, this may be buried under the “Advanced” tab.
Are you in a restaurant or an airport?
It may appear strange. However, cafés and airport Wi-Fi networks are among the most popular. Where users get the “your connection is not private” issue. Why?
Because many of them are still not running anything over HTTPS, or if they are, they are not secure. It’s not set up appropriately. It is generally applicable to the gateway screen. To sign in, you must accept the terms and conditions.
Suppose you are attempting to connect to an HTTPS (secure) site. This error may appear before accepting the portal’s conditions. Here are several simple measures to take to get around it.
- Connect to the Wi-Fi at the cafe or the airport.
- Navigate to a non-HTTPS site like http://www.weather.com.
- The sign-in page should now appear. You can log in after accepting the conditions because the terms are often only a checkbox.
You shouldn’t be overly concerned if it’s not using HTTPS. Once connected, you may use HTTPS to access websites.
Suppose you are unable to open the sign-in page. Alternatively, you may enter 18.104.22.168 into your browser (source).
Remember that anytime you use public Wi-Fi, a VPN may help safeguard you even more by concealing your traffic. Here are a few popular ones you might want to look into:
Confirm Your Computer’s Clock
Another typical cause of the “your connection is not private” problem is that your computer’s clock is out of sync. Browsers rely on these to be correctly synchronized to validate the SSL certificate.
It is something that can quickly happen if you’ve recently acquired a new computer. Especially laptops that are connecting to Wi-Fi for the first time. They do not always sync instantly after your initial login.
The procedures to change the time on your computer are outlined here. You should note that this can also occur on mobile devices.
1. Right-click the time in the task tray’s bottom right corner.
2. Choose “Adjust date/time.”
3. Choose “Set time automatically” and, if desired, “Set time zone automatically.” It will do an update based on one of Microsoft’s NTP servers.
Check the time in the bottom right-hand task tray again to ensure it is correct. If not, you may manually pick a time zone by clicking the “Change” button.
4. Reopen your browser after closing it. Then try viewing the page again.
1. Select “System Preferences” from the Apple menu.
2. Select the Date & Time option if you see a padlock at the bottom of the window. You may need to click it and enter your administrator account and password.
3. Select “Automatically set date and time.” It will do an update based on one of Apple’s NTP servers.
4. Navigate to the Time Zones tab. If it does not automatically detect your location, simply uncheck it so you may manually configure it. Choose your time zone, area, and city from the map.
5. Reopen your browser after closing it. Then went back to the webpage.
Experiment with Incognito Mode
Our typical next suggestion is to delete your browser’s cache. However, for many of us, it is easier said than done. Suppose you want to test it without having to wipe your cache. You may always use incognito mode in your browser.
Alternatively, try another browser to check if you still get the “your connection is not private” warning. Chrome addons are another option. However, this will assist you in putting it to the test.
In Mozilla Firefox, incognito mode is known as “New private window.” It’s known as “New InPrivate Window” in Microsoft Edge.
Delete the Browser’s Cache and Cookies
If you suspect it is your browser. Before delving into further in-depth troubleshooting, clearing your browser cache is always an intelligent troubleshooting step.
Attempt to Clear the SSL State on Your Computer
Clearing the SSL state in Chrome is a task that is sometimes forgotten. However, it may be handy and is simple to implement.
It, like clearing your browser’s cache, might be helpful if things go out of sync.
To clear the SSL status in Chrome on Windows, perform the following steps:
1.Click the Google Chrome – Settings icon (Settings) to open the Settings menu. Then choose Settings.
2. Click the Show advanced settings button.
3. Change proxy settings; you may find it under Network. The Internet Properties dialogue box is shown.
4. Navigate to the Content tab.
5. Click OK after selecting “Clear SSL state.”
6. It should restart Chrome.
Alter DNS Servers
The next option is to change your DNS servers. We’ve seen the “your connection is not private” issue occur. When utilizing Google’s Public DNS (22.214.171.124 and 126.96.36.199) or Cloudflare’s DNS before (188.8.131.52 and 184.108.40.206).
Removing this and reverting to your ISP’s DNS servers will occasionally resolve DNS issues. Google and Cloudflare aren’t ideal all of the time. And problems do arise from time to time.
Go to your network connection properties in Windows to do this. Also, ensure that “Obtain DNS server address automatically” is checked.
Suppose you’ve configured your router to use Google’s Public DNS or Cloudflare’s DNS. It may also be necessary to delete it from there.
Temporarily disable VPN and Antivirus
VPNs and antivirus software can sometimes clash with or override your network settings, including banning specific SSL certificates or connections.
If you have any operations, consider temporarily deactivating (closing) them or disabling their “SSL Scan” feature to see what happens. If it resolves the “your connection is not private” problem on Chrome.
Make Sure the certificate hasn’t expired
SSL certificates expire all the time without the website owner’s awareness. In truth, there’s a lot more to it than you would imagine. Even Fortune 500 corporations! Within a few seconds, we were able to locate the tweet.
Typically, this occurs for the following reasons:
- The website owner’s domain registrar or SSL certificate provider does not have auto-renew enabled.
- Although auto-renew is enabled, the payment fails. As a result of the user’s failure to change their payment method.
Throughout the year, users generally change payment cards more frequently than check their domain registrar’s dashboard.
- The website owner makes use of a free Let’s Encrypt certificate that expires in 90 days. And they either don’t have a script in place or fail to renew it.
This results in the following error code: NET::ERR CERT DATE INVALID.
By using Chrome DevTools while on the site, you can simply verify a certificate’s expiration date. To view a certificate, go to the Security tab and then to the “View certificate” button.
The certificate information will include the “Valid from” dates.
Clicking on the padlock in the address bar is another quick and easy way to obtain a site’s SSL certificate information in Chrome. Then choose “Certificate.”
Examine Subject Alternate Domain
The Subject Alternative Name is a name assigned to each certificate. It covers all domain name variants for which the certificate was issued and is still valid. It’s worth noting that https://domain.com and https://www.domain.com are considered distinct domains.
Suppose you see an error code such as SSL ERROR BAD CERT DOMAIN. It’s conceivable that a certificate hasn’t been registered adequately on both domain variants.
It is less frequent anymore because most websites use HTTPS redirection.
It might also occur if you just changed domain names. For example, suppose you’ve recently purchased a gleaming new.com address and have relocated from your previous domain.
If you fail to install an SSL certificate on your new domain, you will most likely receive a NET::ERR CERT COMMON NAME INVALID error.
Is the certificate SHA-1?
SHA-1 is a cryptographic hash technique that was previously widely utilized by SSL certificates on the internet. SHA-1, on the other hand, has exhibited symptoms of weakening. As a result, it is no longer supported by any modern browser.
If a website still uses a certificate with this outdated method, an error message stating “your connection is not private” will display.
- In Chrome 56, Google Chrome dropped support for SHA-1 (January 2017)
- In Firefox 51, Mozilla Firefox announced the deprecation of SHA-1 (February 2017)
- Microsoft has declared that it would no longer accept SHA-1 certified TLS certificates (January 2017)
The majority of certificates currently use the SHA-256 hash methods. It is accessible via the “Details” tab. When examining a website’s certificate.
Carry out an SSL Server Test
Suppose you’re not sure if everything on your website is set up correctly. Or maybe it’s someone else’s. An SSL server test may always be performed. SSL/TLS certifications require more than just your primary certificate.
However, it must install intermediate certificates (chain) if you don’t have them correctly configured. Visitors’ browsers may display a warning.
It may push them away. And it also depends on the browser and version. If your certificate is improperly configured, you may or may not receive this warning.
We recommend utilizing Qualys SSL Labs’ free SSL check tool. It is dependable.
Simply go to their SSL check tool, enter your domain into the Hostname column, and click “Submit.”
You may even choose to hide public results if you want. The scan may take a minute or two. However, it will show you all delicate information about a site’s SSL/TLS settings.
Reboot Your Computer
We understand how inconvenient it is, but it must be mentioned. If none of the above solutions works, restart your computer and even your router.
We understand that many of you have hundreds of tabs or programs open. As a result, we made this one of the final alternatives.
However, restarting devices clears off a lot of temporary cache and glitches.
Disable Chrome’s SSL Certificate Validation
You may also prevent Chrome from verifying SSL certificates. However, we cannot emphasize this enough. It is only intended for testing and development.
If you don’t know what you’re doing, don’t use the following choices.
When testing locally, you may utilize the Chrome option to accept unsafe connections from localhost. Navigate to chrome:/flags/ in Chrome.
If you search for “insecure,” you should find an option to “Allow invalid certificates for resources loaded from localhost.” Enable that option and reload your browser.
Disable Chrome’s checking of all SSL certificates
By providing the following command line argument to Chrome at launch, you may instruct it to disregard any SSL certificate problems.
If you’re using Windows, simply right-click on the launcher and select Properties. Then, in the Target box, add —ignore-certificate-errors. Then, relaunch Chrome.
Browser problems are never enjoyable, and they may be tough to resolve at times. Hopefully, one of the suggestions above will assist you in determining the “your connection is not private” problem as soon as possible.
Remember that a misconfigured setting on your machine usually causes them. Alternatively, you can find the certificate on the website itself.
A thorough review of the procedures connected with the numerous strategies to avoid this mistake would be pretty beneficial. You’re perusing the web at the same time. Try to look at each one separately.