Author Topic: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG  (Read 9940 times)

0 Members and 1 Guest are viewing this topic.

Offline Spiritual2016

  • Sr. Member
  • ****
  • Posts: 348
Specs:

Avast Free Version 18.5.2342
Firefox 61.0 (64 bit)
No Proxy
Windows 7 Home Premium

When accessing Google from Firefox, the above error code is displayed each time. Firefox was closed and re-opened and even reset but the issue remains and only with the Firefox browser.

Firefox Tech stated that Avast is meddling with encrypted connections. The latest version of Firefox (Version 61) introduced a better security protocol TLS 1.3 but Avast cannot cope with it yet.

When will Avast release an update to fix this bug?
« Last Edit: June 28, 2018, 07:33:36 PM by Spiritual2016 »

Offline vianello_85

  • from Italy
  • Full Member
  • ***
  • Posts: 115

Offline lukor

  • Administrator
  • Super Poster
  • ***
  • Posts: 1884
    • AVAST Software
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #2 on: June 28, 2018, 09:55:09 AM »
Hi, we are working on a fix, will be released later today.

As a workaround, you can temporarily disable TLS1.3 in firefox settings.

1. In the address bar enter about:config
2. Search or scroll to security.tls.version.max
3. Change the value to 3

Done.

This will limit the TLS version to 1.2, the default for Firefox previous version and other browsers at this moment. I'll update here when an Avast fix is ready. Undoing this configuration change is easy as well, just follow the same steps and change the value back to 4.

REDACTED

  • Guest
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #3 on: June 28, 2018, 11:25:09 AM »
Hi, we are working on a fix, will be released later today.

As a workaround, you can temporarily disable TLS1.3 in firefox settings.

1. In the address bar enter about:config
2. Search or scroll to security.tls.version.max
3. Change the value to 3

Done.

Thank you, I also have this problem on Internet security,
When the antivirus is updated, will it auto enable HTTPS scanning again? Because i have disabled it in avast for now and i will forget later to reactivate HTTPS scanning :)


Offline suk

  • Avast team
  • Jr. Member
  • *
  • Posts: 32
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #5 on: June 28, 2018, 01:54:35 PM »
Fixed partially via Virus Definitions Update 180627-2
It should be delivered automatically, but you can force the update in Menu->Settings->Update->Virus Definitions->Update

UPDATE: Virus definition update 180628-06 seems to still causing issues.

If you experience it, could you try to refresh the page by button "Try again" or Ctrl+R (might require several attempts)?
 

   
« Last Edit: June 28, 2018, 02:41:51 PM by suk »

Offline The Sniggler

  • Full Member
  • ***
  • Posts: 120
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #6 on: June 28, 2018, 02:49:13 PM »
Fixed partially via Virus Definitions Update 180627-2
It should be delivered automatically, but you can force the update in Menu->Settings->Update->Virus Definitions->Update
UPDATE: Virus definition update 180628-06 seems to still causing issues.
If you experience it, could you try to refresh the page by button "Try again" or Ctrl+R (might require several attempts)?

Tried to update definitions, but 180627-2 appears to be current. Will keep trying.

Offline suk

  • Avast team
  • Jr. Member
  • *
  • Posts: 32
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #7 on: June 28, 2018, 04:35:57 PM »
Fixed via Virus Definitions Update 180628-8
It should be delivered automatically, but you can force the update in Menu->Settings->Update->Virus Definitions->Update

If you still experience the issue, please let us know (+ include the site that's causing issue as well, so we can test it on real data)

REDACTED

  • Guest
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #8 on: June 28, 2018, 06:36:14 PM »
I just updated and seems to work now for me, at least for now, fingers crossed. Thx for fixing this :)

Offline Spiritual2016

  • Sr. Member
  • ****
  • Posts: 348
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #9 on: June 28, 2018, 07:38:27 PM »
I decided to wait it out and not 'tamper' with a workaround.

Google can now be accessed from Firefox without any error messages and my Avast Virus Definitions shows 180628-8.

Issue resolved.








« Last Edit: June 30, 2018, 08:52:43 PM by Spiritual2016 »

Offline The Sniggler

  • Full Member
  • ***
  • Posts: 120
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #10 on: June 28, 2018, 07:56:47 PM »
Fixed via Virus Definitions Update 180628-8

Fixed... thanks!

Offline kanon86

  • Newbie
  • *
  • Posts: 11
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #11 on: June 29, 2018, 05:53:17 PM »
Https scanning doesn't work anymore for me since that update. Http scanning still works fine.

Am I the only one with this problem?

REDACTED

  • Guest
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #12 on: June 29, 2018, 10:22:55 PM »
Https scanning doesn't work anymore for me since that update. Http scanning still works fine.

Am I the only one with this problem?

Are you saying it does not scan https anymore after you got the update ?

Offline kanon86

  • Newbie
  • *
  • Posts: 11
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #13 on: June 30, 2018, 09:28:35 PM »
Https scanning doesn't work anymore for me since that update. Http scanning still works fine.

Am I the only one with this problem?

Are you saying it does not scan https anymore after you got the update ?

Yes, using Firefox 61.
« Last Edit: June 30, 2018, 09:30:52 PM by kanon86 »

REDACTED

  • Guest
Re: Secure Connection Failed: Error code: SSL_ERROR_RX_RECORD_TOO_LONG
« Reply #14 on: July 01, 2018, 07:56:53 PM »
Https scanning doesn't work anymore for me since that update. Http scanning still works fine.

Am I the only one with this problem?

Are you saying it does not scan https anymore after you got the update ?

Yes, using Firefox 61.

How can I check if mine is scanning https ? It is enabled in settings but if it scans I don't know.