Fix connection errors

A website you're trying to view might use SSL (secure socket layer) to keep any information you enter on their pages private and secure. In that case, you might see one of these errors:

Learn how to fix these types of errors below.
 


"Connect to network"

Sometimes, you might need to visit a login page before you can get online. This type of page is called a Wi-Fi portal. The Wi-Fi portal is blocking your secure connections (https://) until you log in, so you could get the error: "Connect to network."

To fix, click Connect on the page you're trying to open.

"Your connection is not private"

If you see the error "Your connection is not private" in Chrome, try the following tips:

Computer

Tip 1: Log in to the portal

If you recently connected to a new Wi-Fi network, try logging in.

  1. Go to any site that loads the web address with http:// at the beginning.
  2. The Wi-Fi portal log-in page should be reloaded.
  3. Log-in to the portal to access the internet.

Tip 2: Try opening the page in incognito mode

Open the page in an incognito window. If it works there, it means one of your extensions is causing the security problem and you should remove it. Learn how to turn off an extension.

Tip 3: Update Windows

If you're using a Windows computer, make sure your operating system is up to date and has the most recent service packs installed.

Tip 4: Temporarily turn off your antivirus

If you have any antivirus software on your computer that provides "HTTPS protection" or "HTTPS scanning," it might be interfering with the browser's ability to provide security. Turn it off for now to see if it fixes the problem. If that works, you'll need to turn off this feature to use secure sites.

Remember to turn your antivirus program back on when you're done.

Still not working? If the tips above don't help, your connection might be compromised. You can get more help on the Chrome Help Forum.
Mobile device

Tip 1: Login to the portal

If you recently connected to a new Wi-Fi network, try loggin in.

  1. Go to any site that loads the web address with http:// at the beginning.
  2. The Wi-Fi portal log-in page should be reloaded.
  3. Log-in to the portal to access the internet.

Tip 2: Temporarily turn off your mobile antivirus

If you have any anti-virus software on your mobile device that provides "HTTPS protection" or "HTTPS scanning," it might be interfering with the browser's ability to provide security. Turn it off for now to see if it fixes the problem. If that works, you'll need to turn off this feature to use non-secure sites.

Remember to turn your antivirus program back on when you're done.

Still not working? If the tips above don't help, your connection might be compromised and someone might be trying to attack you. You can get more help on the Chrome Help Forum.

"Your clock is behind," "Your clock is ahead," or Net::ERR_CERT_DATE_INVALID

If you see these errors, your computer or mobile device's inaccurate date and time are causing an SSL error. To get rid of this message, update your device's clock and double-check the exact date.

"Server has a weak ephemeral Diffie-Hellman public key" or ERR_SSL_WEAK_EPHEMERAL_DH_KEY

If you see this error, it means that a secure connection can't be established because of outdated security code on the website. Chrome protects your privacy by preventing you from connecting to these sites. You won't be able to visit this page using Chrome.

If you're a website administrator, we recommend you update your server to support ECDHE and disable DHE. If ECDHE is unavailable, you can instead disable all DHE cipher suites and rely on plain RSA.

"This webpage is not available" or ERR_SSL_VERSION_OR_CIPHER_MISMATCH

If you see this error, it means that a secure connection can't be established because of outdated security code on the website. Chrome protects your privacy by preventing you from connecting to these sites. 


For website administrators, this error is often caused by the server requiring RC4, which is no longer considered secure. For best practices, we recommend using TLS 1.2 and TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. If this is unavailable, make sure that other non-RC4 ciphers are turned on.

Laura is a Google Chrome expert and author of this help page. Leave her feedback about the page.

Was this article helpful?