for a couple of weeks now i have been unable to view certain websites i know to be sage. IE - https://www.governmentjobs.com/careers/northcarolina/
this is where north carolina and many other state and local govts post there jobs.
The ensuing Avast page says -
“This site can’t provide a secure connectionwww.governmentjobs.com sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR”
i ran diagnostics but found no problem. The above website is just one example. i am getting blocked by alot of sites that i need to see and which were never blocked before 2 weeks ago.
there are some reports of problems with the new http3 protocol since version 106 of firefox.
Are you experiencing the same problem with another browser?
If not, try changing “network.http.http3.enabled” to “false” in about:config
Neither do I,
but there are a number of reported concerns about the problem with the new http3 protocol / firefox / avast https scanning that it’s hard to talk about isolated cases.
By the way, I would be curious to know if joefoot3 was disabling (temporarily) the https scan or simply the Quic/http3 scan of the avast web shield … if he got the access to this site?
Or if it’s ok with other browsers like chrome or ASB?
Problems here, Google Chrome (Version 107.0.5304.88 (Official Build) (64-bit)). Been a problem since the last Avast update 2 days ago.
Adding exceptions to Avast fixes the issue (although the UI is poor with the software).
No issues with FireFox and Microsoft Edge (also, both up to date). Somehow, Avast has screwed up Google Chrome.
I am yet to go through uninstallation of Avast etc, but I suspect that it has screwed Google Chrome settings and a simply uninstall and reinstall of Avast isn’t going to fix my problem.
I think I have managed to fix it. I did a repair on Avast One, rebooted my computer, but the problem was still prevalent.
I then did a reset settings on Chrome and restarted Chrome and things seem to have returned to normal functioning.
This problem was pretty much affecting every https page and was a real nuisance.
I suspect that Avast overwrote Chrome’s root certificates, which somehow meant Chrome used the Avast SSL cert for every https website. Not good. I base this comment on checking the https cert for a known website and it read back assigned by Avast. Obviously not right.
This problem occurred after an Avast update 3 or 4 days ago. Chrome had been updated a few days before that, as had Windows itself.