When I load Chrome, the start page is google.com. The https:// gets crossed out in red, and a page is displayed stating the below message. When I disable avast shields, it works fine. Would someone let me know if this is being corrected?
"Your connection is not private
Attackers might be trying to steal your information from www.google.com (for example, passwords, messages, or credit cards).
ReloadHide advanced www.google.com normally uses encryption to protect your information. When Chrome tried to connect to www.google.com this time, the website sent back unusual and incorrect credentials. Either an attacker is trying to pretend to be www.google.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit www.google.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
OK, well I appreciate you telling me that, but I don’t know what I’m searching for and can’t find what you’ve seen. Would you mind posting the thread url? Thanks
Not using anything like Trusteer. I have had issues with MalwareBytes Anti-Malware conflicting with installations of Avast in the past, but that doesn’t seem to have happened with this upgrade. Before it would say Avast isn’t running when that problem occured, and that’s not the error I’m getting.
The good news is I did as you suggested and unchecked https scanning in the settings, that seems to have resolved the issue! I am hoping this is just a bug with Avast and not Avast telling me something important I’m not able to see.
Thanks for your help.
EDIT: I also found this thread which is right on target with my problem.
Hi,
this seems like we weren’t sucessfull in adding the root certificate into the trusted certificate store.
My advice here is to do the easy things first:
check your time and date? is it correct?
reinstall avast – uninstall, reboot, reinstall again – what I hope this will do here is removing the certificate (if any) and re-generating the root one again. It will also clean the certificate store from all the certificates we have (webshield) ever created. And during reinstall you’ll get a second try.
you can also do most of the checks from 2) manually:
i) go to the certificate store and check for Mail/Web Shield root certificate in it
- Start / Run (or Win+R on Windows 8 ) / certmgr.msc
- Navigate to Trusted Root Certificate Authorities \ Certificates
- Look for the Avast root certificate there - it should be “avast! Web/Mail Shield Root”
ii) if not there, you can manually import it into the store
- Start / Run ( or Win+R on Windows 8 )
- Type:
C:\ProgramData\AVAST Software\Avast\wscert.der
A certificate window should open. Similar to the one attached.
Click Install Certificate
Choose: Store location: Local machine
Choose: Place all certificates into the following store
Click browse and navigate to “Trusted Root Certification Authorities”
Hi, Lukor! Thank you for responding so fast. I will go through your suggestions in detail, but I have to see where Lord_Ami is going with this. I am in fact using Zemana Antilogger Free.
Disable Zemana’s SSL protection as it does not trust avast! certificates. I’ve reported it to Zemana and they are adding “compatibility” warning in next version as far as I understood.
It would be better if Avast staff contacts them about this issue.
Time/Date is correct… I don’t understand the rest of what you are asking. Sorry. I do not see an option to open the certifcate when it fails and I don’t know what the root is.
It appears you’re right. I turned off SSL in Zemana, and re-enabled HTTPS checking in Avast, and I no longer seem to have any issues. Lord_Ami, do you feel like they both do the same thing? Which do you prefer to use Zemana’s or Avasts?
Not just Eddy: everyone, have a really good read of Eddy’s link. Ask yourselves what Google (Chrome) means by the term “SSL”. Does Google mean Secure Sockets Layer only? Or do they mean Secure Sockets Layer and Transport Layer Security? The question is not trivial. If Google means both technologies, what does (should) that tell us about the browser Avast chooses to support? What does that tell us about Avast’s own knowledge of internet security?
I really hope this leaves at least some people with an uncomfortable feeling in their gut, forcing them to get a better appreciation of the jungle we call “cyber-space”.
