Why do I keep getting SSL error/HSTS failure when I try to go to twitter?3 Recommended Answers
Your issue not there? Please provide the following information & provide a description of your issue:
Chrome Version (type about:version into your omnibox): 32.0.1700.102 (Official Build 246481) m
Operating System (Windows 7/8/Vista/XP, Mac, Linux, Android, iOS): Windows 8
Extensions (type Chrome:extensions into your omnibox): add blocker, add to pocket
I haven't been able to visit twitter these past two days and receive this error when I try:
Cannot connect to the real twitter.com
Something is currently interfering with your secure connection to twitter.com.
Try to reload this page in a few minutes or after switching to a new network. If you have recently connected to a new Wi-Fi network, finish logging in before reloading.
If you were to visit twitter.com right now, you might share private information with an attacker. To protect your privacy, Chrome will not load the page until it can establish a secure connection to the real twitter.com.
twitter.com normally uses encryption (SSL) to protect your information. When Chrome tried to connect to twitter.com this time, twitter.com returned unusual and incorrect credentials. Either an attacker is trying to pretend to be twitter.com, or a Wi-Fi login screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
Network errors and attacks are usually temporary, so this page will probably work later. You can also try switching to another network.
twitter.com has asked Chrome to block any certificates with errors, but the certificate that Chrome received during this connection attempt has an error.
Error type: HSTS failure
Issuer: DigiCert High Assurance CA-3
Public key hashes: sha1/ae59qg2zFxaY3CjC5fxD4dN/YIg= sha256/V4k/5XLareqhqZ8s3CwhflYHUQ59IBcw1JagAzk+6So= sha1/lfnXQ0sc5x3vQhHua+PA4CVvrZU= sha256/emrYgpjLplsXa6OnqyXuj5BgQDPaapisB5WfVm+jrFQ= sha1/gzF+YoVCU9bXeDGQ7JGQVumRueM= sha256/WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18=
configurations of Kaspersky and ESET security software.
We recommend that users disable SSL scanning in these products. Even
when they work, SSL scanning bypasses Chrome's own certificate
We believe that we have a partial workaround for the ESET bug which we
are planning to include in a future Chrome 33 update.
We do not currently have a workaround for the Kaspersky bug that
doesn't involve reducing the security of all Chrome users. As other
browsers deploy the same changes as in Chrome 33, they will also
trigger the same bug.
To fix ESET do:
Setup -> Advanced setup... -> Web and Email -> Web access protection
-> HTTP, HTTPS -> check "do not use HTTP protocol checking" and click
To fix Kaspersky:
Settings -> Additional -> Network -> unclick "Scan encrypted connections"
Some community members might have badges that indicate their identity or level of participation in a community.
Member levels indicate a user's level of participation in a forum. The greater the participation, the higher the level. Everyone starts at level 1 and can rise to level 10. These activities can increase your level in a forum:
- Post an answer.
- Having your answer selected as the best answer.
- Having your post rated as helpful.
- Vote up a post.
- Correctly mark a topic or post as abuse.
Having a post marked and removed as abuse will slow a user's advance in levels.
View profile in forum?
To view this member's profile, you need to leave the current Help page.
Report abuse in forum?
This comment originated in the Google Product Forum. To report abuse, you need to leave the current Help page.
Reply in forum?
This comment originated in the Google Product Forum. To reply, you need to leave the current Help page.