Ky sajt do të funksionojë me kufizime, teksa bëjmë mirëmbajtjen e tij për të përmirësuar punën tuaj. Nëse një artikull nuk e zgjidh problemin tuaj dhe dëshironi të bëni një pyetje, kemi bashkësinë tonë të asistencës, e gatshme për t’ju ndihmuar, te @FirefoxSupport në Twitter dhe/r/firefox në Reddit.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Unable to log in to Fidelity.com - Firefox says "Performing TLS handshake . . ."

more options

When I try to log in to Fidelity.com using Firefox, there is a very long delay (until timeout), while the status bar at the bottom of the screen says "Performing TLS handshake . . ." This does not happen on other websites. Does anyone else have this problem, or any suggested solution?

When I try to log in to Fidelity.com using Firefox, there is a very long delay (until timeout), while the status bar at the bottom of the screen says "Performing TLS handshake . . ." This does not happen on other websites. Does anyone else have this problem, or any suggested solution?

Krejt Përgjigjet (5)

more options

Try again with Firefox in Safe Mode and see if you have the same issue.

more options

That didn't help (yes, I still have the same issue). To save time, none of the following helped either:

Creating a new profile Reinstalling Firefox Restarting my modem and router

I've been using Firefox for several years and never had this issue before. I think it must be a bug in the new release - the problem began about the same time as the latest release.

more options

You can try to disable IPv6 to see if that has effect.

more options

What security software are you running? Are you Win 11 Pro? If so, try Windows Sandbox. https://www.howtogeek.com/399290/how-to-use-windows-10s-new-sandbox-to-safely-test-apps/

more options

Sorry for delayed response. The problem seems to have solved itself before I got a chance to try either of the preceding recommendations. Will report back if it reappears. All good for now, except I don't understand what caused the problem, or what resolved it.