Author Topic: recently started getting ERR_SSL_PROTOCOL_ERROR  (Read 2148 times)

0 Members and 1 Guest are viewing this topic.

Offline joefoot3

  • Newbie
  • *
  • Posts: 3
recently started getting ERR_SSL_PROTOCOL_ERROR
« on: November 03, 2022, 09:06:55 PM »
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.

whats up.

Offline Rundvleeskroket

  • Poster
  • *
  • Posts: 508
Re: recently started getting ERR_SSL_PROTOCOL_ERROR
« Reply #1 on: November 04, 2022, 01:08:22 AM »
I'm running the latest version of Avast Free and can access the site just fine with Firefox.

Are you using a VPN?

Offline chris..

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2933
Re: recently started getting ERR_SSL_PROTOCOL_ERROR
« Reply #2 on: November 04, 2022, 01:29:34 AM »
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

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89057
  • No support PMs thanks
Re: recently started getting ERR_SSL_PROTOCOL_ERROR
« Reply #3 on: November 04, 2022, 02:32:56 AM »
No problem connecting here, and I have Firefox as my default browser.  I have just done a manual browser update check to 106.0.4 (64-bit).
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline chris..

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 2933
Re: recently started getting ERR_SSL_PROTOCOL_ERROR
« Reply #4 on: November 04, 2022, 12:06:12 PM »
No problem connecting here, and I have Firefox as my default browser.  I have just done a manual browser update check to 106.0.4 (64-bit).
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?
« Last Edit: November 04, 2022, 12:07:55 PM by chris.. »

Offline david_pastern

  • Newbie
  • *
  • Posts: 2
Re: recently started getting ERR_SSL_PROTOCOL_ERROR
« Reply #5 on: November 08, 2022, 04:29:47 AM »
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. 

Not a happy camper.

Offline r@vast

  • Avast team
  • Massive Poster
  • *
  • Posts: 2761
Re: recently started getting ERR_SSL_PROTOCOL_ERROR
« Reply #6 on: November 09, 2022, 12:25:10 PM »
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. 

Not a happy camper.

Hi,

Can you try to disable HTTPS scanning and see if that makes a difference?
https://support.avast.com/article/use-antivirus-https-scan/

Offline david_pastern

  • Newbie
  • *
  • Posts: 2
Re: recently started getting ERR_SSL_PROTOCOL_ERROR
« Reply #7 on: November 10, 2022, 12:03:25 AM »
Hi Team,

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.