Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox hangs, hard drive light hard on - this happens frequently when performing a TLS handshake- does not end when Firefox terminated

  • 10 பதிலளிப்புகள்
  • 2 இந்த பிரச்னைகள் உள்ளது
  • 48 views
  • Last reply by dennyem

I have seen other similar posts, mostly concerning Avast or AVG. I am not running either of these but still get hang ups with "Performing TLS Handshake with..." message. I'm running Windows 7 64 bit. Firefox 65.0 64 bit.

I have seen other similar posts, mostly concerning Avast or AVG. I am not running either of these but still get hang ups with "Performing TLS Handshake with..." message. I'm running Windows 7 64 bit. Firefox 65.0 64 bit.

தீர்வு தேர்ந்தெடுக்கப்பட்டது

That makes sense Pj. I still have not seen the issue since the last update, I am confident it is now resolved, thank you.

Read this answer in context 👍 0

All Replies (10)

So what site are you at when this happens? And what security software are you using and what other addons are installed?

I'm visiting an Australian Banking site "nab.com.au". It happens when attempting to login. You don't need an ID and Password to get the error just select Login.

I have OpenH264 and Widevine plugins, no extensions. The only security software currently in use is Windows Defender and Spybot Search and Destroy.

Chrome never has a problem with this site.

dennyem மூலமாக திருத்தப்பட்டது

dennyem said

I'm visiting an Australian Banking site https://www.nab.com.au/. It happens when attempting to login. You don't need an ID and Password to get the error just select Login.

I have OpenH264 and Widevine plugins, no extensions. The only security software currently in use is Windows Defender and Spybot Search and Destroy.

Chrome never has a problem with this site.


I have Avast, and got to the Login page ok. So, if you temporarily disable Windows Defender and/or Spybot Search and Destroy, does that work?


~Pj

Many users seems to have this problem again and again. It is since Firefox 61. In former versions we do NOT have this problem.

And: We do not have the same problem with other browsers such as google crome or MS-explorer.

ONLY Firefox >61 have this.

Best way to solve the problem ist using a better browser.

And: You have to kill the FF-process in the task manager. Just closing the browsers windows does not stop the TLS-Handshake.

dennyem said

I ... get hang ups with "Performing TLS Handshake with..." message. I'm running Windows 7 64 bit. Firefox 65.0 64 bit.

I have some strange, performance / speed / navigation issues at times. The following procedure corrected my ISP speed, Windows, and FF Browser performance:

The following is for a separate Modem and Router:

  • Unplug both the Modem and Router.
  • Wait at least 30 Seconds.
  • Plug-in Modem in first.
  • Wait at least 60 Seconds.
  • Plug-in Router.
  • Wait at least 2 minutes.

Finally, it's possible one or more of your devices (your computer) needs to be ReBooted to recover access or expected performance.

Full details in this article from www.LifeWire.com:

https://www.lifewire.com/how-to-properly-restart-a-router-modem-2624570


~Pj

Try to disable IPv6 (check for other possible causes as well).

Why did this work over the years until Mozilla came out with the 60-versions?

So - its up to Mozilla to solve this!

In out company we are using other browsers because of this annoying problem.

I have not (yet) experienced the problem since the last update (65.0.1). I'm feeling positive that the issue is solved although not being able to put a handle on why still gripes.

dennyem said

I have not (yet) experienced the problem since the last update (65.0.1)...

Perhaps related to this 65.0.1 fix?:

Fixed looping CONNECT requests when using WebSockets over HTTP/2 from behind a proxy server (bug 1523427).


~Pj

தீர்வு தேர்ந்தெடுக்கப்பட்டது

That makes sense Pj. I still have not seen the issue since the last update, I am confident it is now resolved, thank you.