Fix Your Connection Is Not Private Error In Google Chrome

A useful guide to fix Your Connection Is Not Private error in Google Chrome.

The Internet is a good thing in our life. It brings us great resources to learning, working or shopping through computers or mobile devices. But it's also a powerful thing, which hackers can use to exploit users' information and then stealing from them.

There is much information that attackers can collect when users access the Internet through insecure connections. The privacy and personal information are important things. We need to protect ourselves from attackers by using secured connections.

When you visit a website with an SSL secure method (or also known as https) and an error message show up as below, then please carefully take a look at the website address again and make sure it's correct.

Your connection is not private

Attackers might be trying to steal your information from www.example.com (for example, passwords, messages, bank information or credit cards).

NET::ER_CERT_COMMON_NAME_INVALID

Your Connection Is Not Private Error In Google Chrome

Your Connection Is Not Private

Typically, the above error message appears in your Google Chrome browser because there is a problem with the SSL connection, and your browser can't verify the SSL certificate. SSL is a secure method to encrypt data from your computer (in this case, it's your browser) and send to the server, help to keep the information private and safe while transmitting - and opposite.

With this SSL error, it means your computer or current internet connection prevents the Google Chrome browser to load the requested website with a private and secure method.

Why SSL Errors Appearing In Your Chrome Browser?

There are many causes that could lead to this SSL error, such as unknown SSL certificates, expired SSL certificates or the connection between your computer and server isn't secured. But here are three main reasons why SSL warnings appear:

  • The SSL connection between your computer and the server isn't secured.
  • The SSL certificate is expired, set up in a wrong way or does not belong to the requested domain (NET::ER_CERT_COMMON_NAME_INVALID). Check out the example here to learn more about it.
  • The SSL certificate isn't issued by a trusted organization. You know, it's very easy to issue an SSL certificate and install on your website, no need to purchase from elsewhere. However, this SSL certificate isn't created by a trusted company or organization. Most of the internet browsers only recognize trusted SSL certificates. So if you create an SSL certificate and install in your website by yourself, these browsers will show a warning because they can't be sure the connection is secure and private. Don't have much money to spend to purchase an SSL certificate? Check it out the free SSL certificate from CloudFlare or purchase one from NameCheap.com for $10.

Valid SSL Certificate

Fix Your Connection Is Not Private Error

As I mentioned above, there are many reasons can cause this SSL connection error. But you can only fix the SSL error when it came from your computer or your device. There is no way to fix it if the SSL certificate is unknown, expired or a wrong setup from the server side until the owner fixes it, or someone who has the right to do.

In this guide today, I will tell you a few reasons that can lead to this error in your Chrome browser, and show you ways to fix it, or bypass it if there is no solution available.

Check The Date And Time Of Your Computer

check date and time on your computer

In most cases, the wrong date & time on your computer is the main reason that prevents the Google Chrome browser to verify the SSL certificate. That's why the SSL error message showed up.

To resolve this SSL connection error, you need to adjust the date & time of your computer or any devices, which are receiving this error. After updating the date & time of those devices, the SSL error will be gone.

Check Your Antivirus Software Or Firewall

Sometimes, antivirus software blocks strange SSL certificates or connections. The best way to fix this SSL error is to turn off the https scan feature in your antivirus or firewall software.

If you think your antivirus or internet security blocked SSL connections, and there is nowhere to turn off "SSL Scanning" feature, you can try to disable the program temporarily to test. If the issue is gone after disabling the program, I would suggest you switch to another antivirus / internet security program.

RELATED ARTICLES
Top 10 Best Free Adware Removal Tool For Windows
Choose any free adware removal tool from the top 10 best free tools below to scan and remove adware from… [Read Article]
Panda Free Antivirus
Best Free Antivirus Software For Windows
Download the best free antivirus programs to secure your online privacy and your files With the growth of the Internet,… [Read Article]

If you have installed and are using the Avast antivirus software to protect your computer from threats, you can go to Settings > Active Protection > Web Shield > Customize.

Avast Antivirus SSL / HTTPS Scanning

Avast Antivirus - HTTPS Scanning Feature

In the next screen, unselect the "Enable HTTPS scanning" feature and click the "OK" button.

Disable HTTPS / SSL Scanning

Disable HTTPS / SSL Scanning

But if you have installed Bitdefender as your antivirus program on your computer, you can go to Settings > Privacy Control > Antiphishing and then just turn the "Scan SSL" feature off.

You also need to disable the built-in firewall or third party firewall programs to make sure they aren't a cause.

Disable The Warning Message

If you don't want to see the "Your connection is not private" or "Net::ERR_CERT_DATE_INVALID" error message anymore, just turn off it in your Google Chrome browser.

  • Type "chrome://flags" in your Google Chrome browser address bar and press the Enter key.
  • Find "Remember decisions to proceed through SSL errors for a specified length of time", and then select the period you want to remember this selection.

remember ssl error on Google Chrome

  • After that, you only need to view this SSL error one time and just click on "Process to <website address> (unsafe)". There is no more warning in the future.

Updated: I have received some reports from users telling me that this option is not available in Google Chrome flags anymore. They can't find it by entering chrome://flags. I have tried myself, and it seems this option is disappeared. But some users still have it in their Chrome browser. So if you can't find this option, try to use other methods.

Process To The Website With An Insecure Connection

In case you can't fix this error because it's a website error - you can choose to "Process to <website address> (unsafe)", with your own risk. To do so, click on the "Advanced" link.

Click on the Advanced link

Click on the Advanced link to show "Proceed to website" link.

And then hit on "Process to <website address> (unsafe)".

Fix Your connection is not private Error

Bypass the "Your connection is not private error" in Google Chrome with two simple clicks.

However, only use this method if you are sure the website you attempt to visit is safe.

This method is just for temporary, and nothing you can do to make this error disappears, except bypass or ignore it and wait for the owner or webmaster to repair. Until then, don't provide any important information when the website asked because it's not safe.

Ignore The SSL Certificate Error From Google Chrome Shortcut

This method is just a way to ignore and bypass the SSL connection error as I mentioned above. It can't use to fix the problem permanently. However, it can make all warnings that related to SSL errors in your Chrome browser disappear for good, until you choose to show it again.

On your desktop, right-click on the Google Chrome shortcut and select "Properties".

Add more parameters as you see in the picture below and click the OK button. After doing this, the error will be ignored all time, and there would be no error message in the future.

How To Fix Your Connection Is Not Private Error In Chrome

You should know that if this error comes with the error code: NET::ERR_CERT_COMMON_NAME_INVALID, then in most cases, it's a fault from the server side. All you can do in this situation is only bypass the error message by clicking "Proceed" link or use --ignore-certificate-errors-- tag in Google Chrome shortcut.

Updated: The correct ignore tag in Google Chrome shortcut is:

--ignore-certificate-errors

To show you how this error will appear on your Chrome browser, I have created a test page which is now available at https://test-error.usefulpcguide.com/ - just visit it in Chrome browser and the error will show up.

"Your Connection Is Not Private Error" In Android Or iOS Device

Basically, if the "Your connection is not private" error is appearing in your mobile devices, such as an Android or iOS smartphone or tablet, then it's caused by those above causes.

The first thing to do is check and make sure the date & time on your mobile device is correct. If you have recently installed any new security software, I would recommend to disable them.

If you can visit the same HTTPS website with other browsers on your mobile devices, such as Firefox or Opera - then something just happened to your Google Chrome browser. You should try to remove all cookies, history and cached files on your browser.

To remove all these files, go to Settings > Privacy > Clear Browsing Data > choose what you want to remove and then click on the "Clear Browsing Data" button. Sometimes, this method is worked with desktop version too.

Clear Google Chrome Browsing Data On Android Or iOS

Clear Google Chrome browsing data on iOS or Android.

Resetting or reinstall Google Chrome would be helped, but only do it if above methods didn't work.

That's it!

I hope this information and methods can help you understand more about SSL and its common errors as well as how to resolve issues when it occurs.

You may also face this SSL connection error on Google Chrome browser in other platforms, such as macOS or Linux. And this guide is still helpful.

If you found other ways to fix this SSL error: Your Connection Is Not Private, in Google Chrome, feel free to share with me. I will update the article with your solutions to make it more useful.

Have any questions wanted to ask or need helps to resolve this issue? Please leave your comment below.



Simple Guide: Fix "Your Connection Is Not Private" Error In Google Chrome
  • It's a simple and useful guide which helped me to fix this issue in Google Chrome browser.
  • It's a helpful article with great tips.

Summary

This article is a simple guide to tell you what is the "Your connection is not private" error in Google Chrome as well as how to resolve it when it occurs in your Chrome browser. Many causes lead to this SSL connection error, but you can apply above methods which mentioned in this article to fix it.

4.8
User Rating 4.97 (31 votes)
Sending

141 Comments

  1. Karen June 3, 2016
    • Smith K June 5, 2016
    • raff January 2, 2017
    • noone April 5, 2017
      • Tony Tran April 5, 2017
        • Ben April 12, 2017
  2. Kevin J. June 10, 2016
  3. Larry T June 10, 2016
  4. Tim Berty June 12, 2016
    • Tony Tran June 12, 2016
      • Tim Berty June 12, 2016
        • Tony Tran June 12, 2016
          • binoj January 7, 2017
  5. Robert Dillion June 12, 2016
  6. Tommy July 1, 2016
  7. Devon July 2, 2016
  8. Roz Henry July 6, 2016
    • Tony Tran July 6, 2016
    • Lilid July 24, 2016
  9. David Bart July 10, 2016
    • Tony Tran July 12, 2016
  10. Alex July 21, 2016
    • Tony Tran July 22, 2016
  11. Stirling July 31, 2016
    • Stirling July 31, 2016
    • Tony Tran July 31, 2016
  12. Ed August 4, 2016
    • Tony Tran August 5, 2016
  13. Norizan August 10, 2016
    • Tony Tran August 10, 2016
  14. Platinum August 20, 2016
  15. Akshat August 31, 2016
  16. JP97392 September 5, 2016
  17. Dave Slomer September 11, 2016
    • Dave Slomer September 11, 2016
  18. JP Banks September 17, 2016
  19. Chris Lentq September 20, 2016
  20. Jimmy September 24, 2016
  21. joe September 26, 2016
    • Tony Tran September 28, 2016
  22. Dyna Remafello October 7, 2016
  23. Mr Trevor Barraclough October 8, 2016
    • Tony Tran October 8, 2016
  24. V October 20, 2016
    • Tony Tran October 20, 2016
      • alex December 6, 2016
  25. ken l October 24, 2016
    • Tony Tran October 24, 2016
  26. Carl October 27, 2016
  27. Amol November 1, 2016
  28. rajesh November 9, 2016
  29. Alan Anderson November 26, 2016
    • Tony Tran November 26, 2016
  30. Belinda December 1, 2016
    • Tony Tran December 1, 2016
      • Belinda December 1, 2016
      • Belinda December 1, 2016
  31. Tamara McClelland December 5, 2016
  32. Joey December 5, 2016
    • Tony Tran December 6, 2016
  33. michelle December 12, 2016
  34. frank December 13, 2016
    • Tony Tran December 15, 2016
  35. shawn December 13, 2016
    • Tony Tran December 15, 2016
  36. Abidha December 26, 2016
  37. David December 29, 2016
    • Tony Tran December 29, 2016
  38. David December 30, 2016
    • Tony Tran December 30, 2016
  39. David December 31, 2016
    • Tony Tran December 31, 2016
  40. kevan December 31, 2016
  41. David January 1, 2017
    • Tony Tran January 1, 2017
  42. Eli January 5, 2017
  43. Katia January 9, 2017
    • Tony Tran January 9, 2017
  44. Khalid January 11, 2017
    • Tony Tran January 11, 2017
  45. brown t January 14, 2017
    • Tony Tran January 14, 2017
      • brown t January 15, 2017
        • Tony Tran January 15, 2017
          • brown t January 17, 2017
          • brown t January 17, 2017
          • Tony Tran January 19, 2017
  46. Christine January 24, 2017
    • Tony Tran January 24, 2017
      • Christine January 24, 2017
      • christine January 24, 2017
        • Tony Tran January 24, 2017
          • christine January 25, 2017
          • Tony Tran January 25, 2017
          • Tony Tran January 25, 2017
          • christine January 25, 2017
  47. Christine January 25, 2017
  48. brown t January 26, 2017
  49. Nathan February 5, 2017
    • Tony Tran February 6, 2017
  50. Timo February 6, 2017
    • Tony Tran February 6, 2017
  51. Beth Jansma February 7, 2017
    • Tony Tran February 7, 2017
      • Beth February 8, 2017
        • Tony Tran February 9, 2017
  52. Beth February 10, 2017
    • Tony Tran February 10, 2017
      • Beth February 10, 2017
        • Tony Tran February 11, 2017
  53. Chris February 10, 2017
    • Tony Tran February 10, 2017
  54. Bill February 12, 2017
  55. Bill February 12, 2017
  56. Zia February 19, 2017
    • Tony Tran February 19, 2017
  57. perfectstorm February 21, 2017
    • Tony Tran February 22, 2017
  58. Satish Ahuja February 23, 2017
    • Tony Tran February 23, 2017
  59. Lucius March 12, 2017
    • Tony Tran March 13, 2017
  60. Lucius March 19, 2017
    • Tony Tran March 19, 2017
      • Lucius April 1, 2017
        • Tony Tran April 2, 2017
          • Lori April 7, 2017
          • Tony Tran April 8, 2017
  61. Michael Cornea March 21, 2017
  62. Dan L. March 26, 2017
    • Tony Tran March 26, 2017
  63. Jim April 4, 2017
  64. Lori April 7, 2017
  65. Suzanne April 8, 2017
    • Tony Tran April 8, 2017
  66. Fazira April 10, 2017
  67. sherran April 19, 2017
    • Tony Tran April 19, 2017

Leave a Reply