Author Topic: TLS handshake errors  (Read 2447 times)

0 Members and 1 Guest are viewing this topic.

Offline sludge7051-x

  • sludge7051-x
  • Jr. Member
  • **
  • Posts: 84
TLS handshake errors
« on: June 29, 2018, 10:54:01 PM »
Getting a lot of TLS handshake errors! • mozillaZine Forums . . . http://forums.mozillazine.org/viewtopic.php?f=37&t=3032011

This fixes it:

Avast - Menu / Settings / Components / Web Shield - Customize / Main settings - [un-check] Enable HTTPS scanning

Why does it make Firefox and other browsers hang?

Is there a way Avast could let me know it's doing this?

Offline Gopher John

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2098
Re: TLS handshake errors
« Reply #1 on: June 29, 2018, 11:49:55 PM »
The last post to the cited thread was on 28 Nov 2017. I'm having no problems with HTTPS sites at all.

There was a recent issue when Firefox 60+ enabled TLS 1.3.  Avast fixed this with VPS 180628-8 yesterday.
AMD A6-5350M APU with Radeon HD Graphics, 8.0GB RAM, Win7 Pro SP1 64bit, IE11
i7-3610QM 2.3GHZ, 8.0GB Ram,  Nvidia GeForce GT 630M 2GB, Win7 Pro SP1 64bit, IE 11
Common to both: Avast Premium Security 19.7.2388, WinPatrol Plus, SpywareBlaster 5.5, Opera 12.18, Firefox 68.0.2, MBam Free, CCleaner

Offline sludge7051-x

  • sludge7051-x
  • Jr. Member
  • **
  • Posts: 84
Re: TLS handshake errors
« Reply #2 on: June 30, 2018, 12:47:09 AM »
Well, it was getting stuck on TLS handshake for me on many web pages (I saw it in the bottom left corner of Firefox), that's all I can say.

I just checked, and have updated my Firefox from 60.0.2 to 61.0, and re-enabled HTTP scanning.  It looks like it works now.  This one page that got stuck before comes right up.

This was quite frustrating.

Can't they build it into the program that if it's holding something up, it lets you know?  That would be an improvement.

Offline sludge7051-x

  • sludge7051-x
  • Jr. Member
  • **
  • Posts: 84
Re: TLS handshake errors
« Reply #3 on: July 07, 2018, 07:11:33 PM »
Update:

06/30/18 Re-boot the modem - didn't help

07/01/18 Reset Win Firewall to the default values? - Yes, this fixed it