If this issue is affecting sites using self-signed certificates, then you may be encountering a problem with the way Firefox parses SSL certificates. If you are a developer, or using interval/private websites, check this next solution: Self-Signed Certificates With Identical Subject/Issuer Information There is also a small chance the cause is related to self-signed certificates. Instead, you may want to transfer your important data to the new profile you created. You can try to troubleshoot your original profile (remember to switch back to it using the Profile Manager), however isolating the issue will be difficult (check if you have a proxy connection configured, and try disabling your add-ons) and it may be due to corrupted data in the profile, which cannot be easily repaired.
If they load normally now, you know the issue is your Firefox profile (instead of with the website itself or your connection to the internet). Try visiting a few sites which have stalled on the “performing a TLS handshake” status. Click “ Set as default profile ” and then close and relaunch Firefox. This will open the Profile Manager.Ĭlick “ Create a New Profile ” and follow the wizard. Starting here is easy and will help isolate if the issue is related to Firefox’s settings, or originating elsewhere.įirst, open a new tab and paste about:profiles into the address bar and hit enter. Your profile data could include misconfigured options or errant data that cause uncommon and hard-to-track-down bugs.
When you use Firefox, all your personalized settings are connected to a specific profile. The first thing to try is creating a new Firefox profile. Here are a few ways to troubleshoot the issue: Create a New Profile If you are frequently noticing that this step takes upwards of 5 seconds, there is likely something wrong. First and foremost, everyone needs to… shake hands?! There’s a lot going on underneath the hood when you connect to a website via HTTPS.
0 kommentar(er)
