When you try to go to a website, you might get a message that says, “Your Connection Is Not Private.” This means that the browser couldn’t ensure that your device and the website were safe to connect to.
A message like “Your Connection Is Not Private” can be caused by SSL (Secure Sockets Layer) problems on the server-side or issues with the client. If you’re the website’s owner or a visitor, there are many ways to fix this error screen.
What Is the “Your Connection Is Not Private” Error Message?
First of all, don’t be afraid when this error message comes up. It means that Google Chrome or another browser blocks you from visiting an untrusted website.
“Your Connection Is Not Private” is a usual error message that comes up when your browser has trouble setting up a secure connection or can’t verify the certificate. Among other things, an unauthorized certificate authority could be to blame for it.
A website with a valid SSL certificate runs on HTTPS, which is more secure than HTTP when it has a valid certificate. Websites that have problems with SSL connections aren’t trustworthy because they can have issues with security.
For example, websites that don’t have valid SSL certificates make it easier for hackers to steal data. Hackers may be able to see your personal information, like your login credentials or payment information if you enter it on these kinds of websites.
However, the issue may not always be with the SSL certificate. Visitors’ browsers, WiFi networks, or OS systems may also be responsible.
Use public WiFi that isn’t safe, change the date and time on your computer, or have your antivirus software run an SSL or HTTPS scan. You might have this problem if you do any of these things.
As long as the problem is on the visitor’s side, the “Your Connection Is Not Private” error should be easy to fix. This is good news.
How Different Browsers Display the “Your Connection Is Not Private” Error
A message like “Your Connection Is Not Private” can also be found on browsers other than Google Chrome. The following sections show the same error on Mozilla Firefox, Microsoft Edge, and Opera.
Mozilla Firefox
Suppose the SSL certificate of the website you’re attempting to visit is not valid. In that case, you’ll see the message “Warning: Potential Security Risk Ahead” when using Mozilla Firefox to access it.
In the description, Firefox tells users that it has found a “potential security threat.” It says, “The issue is most likely with the website, and there is nothing you can do to resolve it.”
To get more information about the problem and the error code, click Advanced. By figuring out the problem, you can fix it more quickly.
Some of the error codes that you might see are the following:
SEC_ERROR_EXPIRED_ISSUER_CERTIFICATE
SEC_ERROR_UNKNOWN_ISSUER
SEC_ERROR_EXPIRED_CERTIFICATE
SSL_ERROR_BAD_CERT_DOMAIN
Microsoft Edge
A wrong SSL certificate on Microsoft Edge will send you to the “Your connection isn’t private” page, almost like Chrome users see. If you look at the address bar, there will also be a red “Not secure” sign.
Aside from that, Microsoft Edge notifies users that “Attackers might be trying to steal your information” from the website you are trying to visit.
They look a lot like the error codes that you might see on Chrome:
NET::ERR_CERT_COMMON_NAME_INVALID
NET::ERR_CERT_AUTHORITY_INVALID
Error Code: 0
DLG_FLAGS_INVALID_CA
Opera
Opera’s version of the error message is “Your Connection Is Not Private,” which is the same as Chrome’s. In addition, it shows the error code next to the error description.
Clicking “Help me understand” gives more information about the problem. According to Opera, the error is caused by “a misconfiguration or an attacker intercepting your connection.”
You may see the same error codes that other browsers show when you use Opera, like this:
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
NET::ERR_CERT_INVALID
NET::ERR_CERT_AUTHORITY_INVALID
SSL certificate error
The Solution to “Your Connection Is Not Private” for Website Owners
Is the error message “Your Connection Is Not Private” shown on your website when someone visits it? There may be issues with your SSL certificate. This section will walk you through four methods for resolving this error message on your website.
1 – Check the Expiration Date of Your SSL Certificate
Check to see if your website’s SSL certificate is still valid. Your SSL certificates may not be up to date.
There are free SSL certificates from Let’s Encrypt that last 90 days. However, if they weren’t renewed automatically, you must renew them manually. If your website is hosted with Rovity, our system will renew SSL certificates automatically. So, you won’t miss it and won’t experience this issue.
If you want to check the expiration date of an SSL certificate on Google Chrome, do the following:
1 – Click on the padlock icon in the website’s address bar that isn’t working.
2 – Click on the Connection is secure toggle. This option may look slightly different depending on what website you are on.
3 – Now, click on the Certificate is valid label.
There will be a new window that opens up. The SSL certificate’s expiration date will be next to Valid from in the new window.
If you find that your SSL certificate is still valid, try the following steps to determine what’s wrong. An expired certificate is most likely the cause of the error.
At Rovity, we will reissue SSL certificates before their expiry date. The process of renewing an SSL certificate will be different depending on which web hosting service you use and which certificate authority you choose to use. In general, it goes through three steps:
1 – Generate a Certificate Signing Request (CSR) for your SSL certificate.
2 – Activate the new SSL certificate.
3 – Install it on your website.
2 – Verify That Your Certificate Was Issued Correctly
Your website’s SSL certificate might not have been generated correctly, which would cause the error. It is critical to issue your SSL certificate properly, to avoid SSL issues.
For example, you might be having problems with your subdomain on your website(s). There’s an SSL certificate on the parent domain name, but it doesn’t cover the subdomains. Each domain should have its SSL certificate, or you can use a multi-domain wildcard SSL to make sure all of them work.
It’s also possible that the SSL certificate you use came from a fake certificate provider. It’s crucial to get a root certificate from a reputable certificate authority.
To learn more about the organization that issued your certificate, do this:
1 – Visit the problematic website and click on the padlock icon in the address bar.
2 – Click on Connection is secure. This option may appear differently depending on the status of the SSL.
3 – Now, click on the Certificate is valid label.
4 – You can find the organization’s name that issued the certificate next to Issued by.
3 – Perform an SSL Server Test
An SSL server test can check if a website’s SSL certificate is still valid. Many of them offer tips and guides to help you figure out any problems with your SSL and fix them.
The SSL Server Test by Qualys, for example, will look at a website’s SSL and give it a score. The only thing you need to do is enter your website’s domain name into the free tool.
It will take a while to look at your website’s SSL configuration. Then, you will get a report and a grade. To see a quick summary of the report and the SSL scan’s detailed results, click on one of the servers in the list.
If you got an A grade, the test found no problems with your SSL certificate, so you should be good to go. If you got any lower scores, you should look into the found issues and fix them.
If your website is hosted with Rovity, you will mostly get an A+ grade here. Because we value your security the most, we will always use the latest and greatest certificate options, that too for free.
For example, the test could show one or more of the following:
1 – The server’s certificate is not trusted.
2 – The server only accepts certain types of cipher with older protocols.
3 – The server is vulnerable to certain kinds of attacks.
4 – The server only supports older versions of TLS.
To fix the problems that have already been found, look at the full report and follow the steps that the SSL server test gives you. The test page links to articles that explain the missteps and how to fix them. This will help you learn more about them and overcome them.
4 -Get in Touch With Your Host
If you have tried the three methods above and none worked, you should contact your web host. A problem with the host could be to blame for the error. If Rovity is your hosting partner, you can contact us via our Live Chat feature or create a support ticket here.
The Solution to “Your Connection Is Not Private” for Website Visitors
Even though a website SSL configuration mistake is usually the leading cause of this problem, sometimes it can be caused by a client’s side.
If you’re sure that you’re the only one getting the “Your Connection Is Not Private” issue when trying to access a particular website, try one of the following 10 quick fixes.
1 – Try Reloading the Page
To begin with, you can try reloading the page.
As simple as this might seem at first, it does work most times! The SSL certificate is likely being reissued, or your browser didn’t connect to the web server in an encrypted way.
2 – Avoid Using Public WiFi
Users often get this error when connecting to a public network, like a coffee shop or an airport.
These days, HTTPS is a must for any website that collects private information, especially if it’s on the web. Because public networks usually use HTTP instead of HTTPS, this isn’t a good thing.
If you do business on a public network, the information you put in won’t be encrypted like on HTTPS. This network will send it in plain text, and anyone on the same WiFi network will get your personal information if they know what they are doing. Your browser will show the message “Your Connection Is Not Private” because it wants to make sure that you know.
You can load the site on your home WiFi or mobile data instead of using public WiFi to connect to the internet.
3 – Clean Up Your Browsing Data
You can try clearing the data your browser has stored, such as cookies, images, and files, to see if that helps.
You can clean the Chrome cache by following these steps:
1 – Click the three dots at the top-right corner and then select History.
2 – Click on the Clear Browsing Data option on the left.
3 – Check the boxes under the Basic tab to clear your browser’s cache and cookies, or you can navigate to the Advanced tab for more options.
4 – From the Time range drop-down menu, choose All time.
5 – Once you’re ready, press the Clear data button.
4 – Switch to Incognito Mode
Check to see if your browser cache and cookies are to blame by going into Chrome’s incognito mode and seeing if that helps. When you use this mode, your browser won’t store any data from the site on your computer.
To use Chrome’s incognito mode, click the three dots at the top-right corner and choose New Incognito Window. Now, go back to the same website you tried to get to before and see if the error still happens.
5 – Check the Date and Time on Your Computer
Your computer’s date and time may be out of date, which could cause the “Your Connection Is Not Private” error message to show up.
Your browser utilizes the time and date settings on your system to evaluate the validity of an SSL certificate. If they are inaccurate, the validation process may be affected. The certificate may appear to be invalid while it is still valid.
To solve the connection error, you should ensure that your computer’s timer and date are set up correctly. Here’s how to quickly check and change the date and time settings on your Windows computers.
1 – Go to Settings > Time & Language > Date & Time.
2 – Turn on the Set time automatically and Set time zone automatically options if they’re turned off. Confirm that the time and date are up-to-date.
3 – Reload the page you’re trying to access.
6 – Check Your Antivirus and Internet Security Software
Some antivirus programs and web security applications will block SSL certificates or connections that aren’t genuine. If you want to fix the “Your Connection Is Not Private” message, you’ll need to turn off the SSL scanning tool.
If you can’t find it, you might try disabling your antivirus and reopening the site in your browser. If the error notice has disappeared, we can assume that this is the source of the problem.
7 – Turn Off Your VPN Temporarily
When you connect to the internet over a VPN (Virtual Private Network), your internet connection is encrypted and rerouted through a remote web server. This hides your Internet Protocol (IP) address, boosts your web anonymity, and protects your personal information.
It’s a shame, but extra security layers can block some SSL certificates, which means “Your Connection Is Not Private.”
Disabling your VPN for a short time could help you determine if your VPN is to blame for the error.
8 – Use a Proxy to Access the Website
When you use a proxy, your internet traffic goes through a web server in another country. This is similar to how a VPN works. When you use a proxy, your connection isn’t encrypted. You can only set it up at the application level.
Other people may access the same website without trouble. The “Your Connection Is Not Private” message may only show on your computer.
You can use a proxy to see if the website works on another network. It’s like utilizing your neighbor’s WiFi to see if the website you’re trying to access is accessible.
You can use free services like Hidester or hide.me to get into a website through a proxy. The only thing you need to do is paste the URL of the website you want to visit.
It’s also possible to use your browser to set up your proxy server’s address and port number.
9 – Restart Your WiFi Router
If you have WiFi at home, you may already know that restarting your router is the most common way to resolve many connection errors. If you get the “Your Connection Is Not Private” problem, it’s worth a shot.
A router has its CPU, memory, and OS, and there are times when it gets too hot or has problems. Quickly and easily, you can restart your router.
Please take a few seconds to turn your router off and turn it back on. Routers have capacitors that may keep running even after you turn them off.
When your router is turned on again, the capacitor will be empty, allowing your router to clear its memory and start over with failed tasks thoroughly.
10 – Proceed Manually With an Unsafe Connection (Unsafe)
If all else fails, keep in mind that the “Your Connection Is Not Private” warning will not prohibit you from browsing the website. You are still welcome to visit the site at your own risk.
Such websites may contain flaws that attackers can use to steal important information such as your full name, address, passwords, and credit card details. While viewing the site, avoid making online payments or disclosing any personal information.
To get to the site manually in Chrome, go to Advanced > Proceed to (the website’s domain name) at the bottom of the message.
Conclusion
SSL certificate issues are the most common cause of the “Your Connection Is Not Private” error message. However, client-side faults in some scenarios may cause it.
While it is simply one of many typical connectivity issues, it can be challenging to identify a solution. This tutorial has explored numerous methods for resolving this issue as a website owner or visitor.
I hope this post has helped you in troubleshooting this error. Please leave them in the comment box below if you have any questions or suggestions.
Suppose you’re looking for a robust infrastructure with high-quality A+ SSL certificates. In that case, I invite you to try Rovity, which has both. You and your website need to have a modern and error-free web hosting infrastructure, and our cutting-edge solution is the best way to get that.
