So recently out of nowhere avast has decided to stop most internet connections on my computer. If I don not disable avast I can not get on any website that is not google or avast.com. For example I went to https://www.kickstarter.com and google chrome said that the web page is blocked by my firewall. I went into the firewall setting of avast and I can’t seem to figure it out. Also when going on the store or community section of steam it doesn’t work either. I am running avast premier and malwarebytes pro. Any help would be awesome. It seems to only have started since last update.
Disable https scanning in the webshield and let us know if the problem is solved.
Also mention the OS/SP you are using as well as the exact avast version.
What is your Operating System ?
Many such topics relating to this, most relating to XP and Vista.
Sorry forgot to mention that. I am running on Windows 10 Pro 64bit
After further investigation it seems like avast corrupted itself on last update. A re-install fixed the issue. Thank you for your quick responses!
Hi Eddy, i need your help. Have the same problem: since I´ve automatically updated from the Avast user interface to this version it is almost impossible to navigate in internet. I can only do it if I deactivate the web shield. I switched to “low” Sensitivity and did not improve. If I add as Exclusions the websites that I usually visit, would it be solved? What risks do I expose myself? If I download an attachment from one of those sites, Avast will neither check it? There is another way to fix this problem? Thank you very much for your answer. Itati (OS Windows Vista - browser Mozilla Firefox. Is the same in my computer with Free Avast, than in my mother one with paid Avast, same OS & browser).
Does disabling the https scanning solves it ?
Thank you Eddy, do you refer to this item?
Yes that is what he is talking about
Nice! i´ll try and i tell you later. Thank you very much!
It worked!!! thank you both very much. Kind regards from Argentina!!
Itati, disabling the HTTPS scanning should be only a temporary solution until this is fixed, we hope, in a later version.