Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Buscar en Ayuda

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

"Performing a TLS handshake" -> Sites don't load

  • Sin respuestas
  • 1 tiene este problema
  • 17 visitas
more options

Running v 60 ESR, downgraded from v 68, with zero problems for 3 weeks.

I've had this problem all of a sudden since last week. Steps I've taken so far:

  • Changed "security.tls.version.min" to 3 from 1 (didn't work)
  • Deleted cert8.db (didn't work)
  • Changed to Google DNS (not sure)
  • Changed to "auto-detect proxy" from "system proxy" (not sure, maybe)
  • Disabled IPV6 (not sure, maybe)
  • Turned off/on wifi hotspot, rebooted laptop (not sure, maybe)

The last 3 steps I took at the same time and they worked. On reboot the problem went away, albeit for 2 days!

It just came back, now it's performing a TLS handshake on about half the sites, with loading after 30-60 seconds or not at all. From searching, I see that solutions are all over the place on this and it's specific to FF. A post clearly identifies a Symantec certificates issue.

This is probably the toughest issue I've come across on FF.

Running v 60 ESR, downgraded from v 68, with zero problems for 3 weeks. I've had this problem all of a sudden since last week. Steps I've taken so far: * Changed "security.tls.version.min" to 3 from 1 (didn't work) * Deleted cert8.db (didn't work) * Changed to Google DNS (not sure) * Changed to "auto-detect proxy" from "system proxy" (not sure, maybe) * Disabled IPV6 (not sure, maybe) * Turned off/on wifi hotspot, rebooted laptop (not sure, maybe) The last 3 steps I took at the same time and they worked. On reboot the problem went away, albeit for 2 days! It just came back, now it's performing a TLS handshake on about half the sites, with loading after 30-60 seconds or not at all. From searching, I see that solutions are all over the place on this and it's specific to FF. A post clearly identifies a Symantec certificates issue. This is probably the toughest issue I've come across on FF.