Stay informed on our news

Why does Chrome Keep Saying Your Connection is Not Private and Secured?

Why does Chrome Keep Saying Your Connection is Not Private and Secured?

How to Fix Your Connection is Not Private/Secured Error in Google Chrome

Today we’re going to dive into the “your connection is not private on chrome” error and walk you through some ways to get things working again. Read more below about what causes this error and what you can do to prevent it in the future.

What is the Your Connection is Not Private Error on Chrome?

The “your connection is not private” error only pertains to sites that are running over HTTPS (or should be running over HTTPS). When you visit a website, your browser sends a request to the server where the site is hosted. The browser then has to validate the certificate installed on the site to ensure it is up to current privacy standards. Other things that also take place include the TLS handshake, the certificate being checked against the certificate authority, and decryption of the certificate.

 

On your taskbar, right-click the time and select Adjust Date/Time. Go to Date & Time > Set Time Automatically and switch it to the On position. Reload your browser and revisit the site. See if the connection not private error is still there.

Check time on MAC:

Go to the Apple Menu > System Preferences. Click the Date & Time. Choose to set the date and time automatically then select a time zone. Revisit the site to see if this fix worked.

Clear your Cache:

Clearing the cache is a go-to solution for common browser-related concerns. You could stop getting your connection is not private notifications through the Clear Browsing Data functionality.

First, check if the error persists in Incognito Mode. To the unfamiliar, this mode lets you browse without saving information like browser history and cookies. If the site is able to load while incognito, your cache needs to be flushed.

Press CTRL + Shift + N in Google Chrome to start an incognito session.

To clear your cache, go to Chrome Settings > More Tools > Clear Browsing Data or hit CTRL + Shift + Del. Select a time range and tick Cached Images and Files. Click Clear Data to continue.

Clear SSL State:

Clearing the SSL certificate on your computer can help get things back to normal. The process is comparable to clearing your browser’s cache.

To clear the SSL slate in Windows (and hence Chrome too), open Internet Options (click on Start and type internet options). Under the Content tab, click the Clear SSL State button. Restart Chrome afterward.

Turn off Antivirus:

Some antivirus software can affect your network settings. Try turning them off temporarily to see if that’s what’s causing the connection is not private error.

The same can be said for virtual private network (VPN) users.

Update your DNS:

If you’ve made changes to your DNS in the past, it may be time to have it obtain an address automatically. Some Google Public DNS users have experienced issues after switching to 8.8.8.8 or 8.8.4.4.

Windows users can update their DNS by opening the Control Panel. Go to Network and Sharing Center > Change Adapter Settings.

Right-click your network and click Properties.

A new window will pop up. Go to the Networking tab. Tick Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6). Once done, click Properties.

Another window will pop up. Under the General tab, tick Obtain DNS Server Address Automatically.

Fix Connection in Not Secure on Firerfox

In Mozilla Firefox the error message varies slightly, and instead of “your connection is not private” you’ll see “your connection is not secure” (as seen below).

The owner of domain.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.

Just like in Chrome, it’s accompanied by an error code message which helps to try and pinpoint the problem. Below are just a couple of the most common error codes you might see 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

Follow the instruction above for connection is not private on chrome procedure.

Leave a Comment