This guide walks you through fixing the “Performing a TLS Handshake” error in Mozilla Firefox on Windows. The error typically appears as a stalled connection or a “Secure Connection Failed” page, and it prevents you from loading HTTPS websites. You’ll learn the most common causes—outdated browser settings, corrupted certificates, interference from security software, or system time issues—and the exact steps to resolve each one.
What You’ll Need
- Administrator access to your Windows PC (for some steps)
- Your current Firefox login (to sync bookmarks after resetting, if you choose that step)
- Internet connection (to download updates or verify fixes)
Step-by-Step
- Check your system date and time. Incorrect date/time is the #1 cause of TLS handshake failures. Right-click the clock in the taskbar, select “Adjust date/time,” and ensure “Set time automatically” and “Set time zone automatically” are both ON. If they’re already on, toggle them off, wait 10 seconds, then toggle back on. Restart Firefox and test the site.
- Disable experimental TLS settings. Type
about:configin the address bar, press Enter, and accept the risk warning. Search forsecurity.tls.version. Setsecurity.tls.version.minto1andsecurity.tls.version.maxto4(these are the defaults). If you or an extension changed these, resetting them often fixes handshake errors. Restart Firefox. - Clear SSL state and cookies. Click the menu (three horizontal lines) > Settings > Privacy & Security. Under “Cookies and Site Data,” click “Clear Data…”, check both boxes, and click Clear. Then scroll to “Security” and click “Manage Certificates” > “Authorities” tab. Look for any certificate named “MITM” or “Proxy” (common with antivirus). If present, select it and click Delete. Restart Firefox.
- Disable HTTPS scanning in antivirus/firewall. Many security suites (Norton, McAfee, Avast, Kaspersky) intercept HTTPS traffic to scan it, which can break the handshake. Open your antivirus settings, look for “SSL/TLS scanning,” “HTTPS filtering,” or “Web protection,” and disable it temporarily. If the error disappears, re-enable it but add Firefox to the exclusion list. If you can’t find the setting, uninstall the antivirus temporarily (Windows Defender will take over) and test.
- Reset Firefox to default settings. This is a nuclear option but fixes most configuration corruption. Go to Settings > Help (or type
about:supportin the address bar). Click “Refresh Firefox” in the top-right corner. Confirm, and Firefox will close, back up your profile, and reopen with default settings. Your bookmarks, passwords, and history are preserved, but extensions and custom settings will be removed. Re-test the site. - Update Firefox and Windows. Outdated software can have TLS bugs. Click the menu > Help > About Firefox. Firefox will check for updates and install them automatically. Then go to Windows Settings > Update & Security > Windows Update and install any pending updates. Restart your PC after both.
- Flush DNS and reset network stack. Open Command Prompt as Administrator (type “cmd” in Start, right-click, “Run as administrator”). Run these commands one by one, pressing Enter after each:
ipconfig /flushdnsnetsh winsock resetnetsh int ip reset
Restart your PC and test. - Create a fresh Firefox profile. If nothing else works, your profile may be corrupted. Close Firefox, press
Win + R, typefirefox -P, and press Enter. In the Profile Manager, click “Create Profile”, name it “Test”, and launch Firefox with it. If the error is gone, your old profile is the problem. You can migrate bookmarks/passwords manually, or just use the new profile.
Common Mistakes
- Skipping the date/time check. This is the simplest fix but often overlooked because the error message doesn’t mention it.
- Changing
security.tls.versionto extreme values. Some guides suggest setting min to 3 or 4, but that can block older sites. Stick to defaults (min=1, max=4). - Disabling antivirus permanently. This leaves you vulnerable. Use it only as a test, then re-enable with exclusions.
- Not restarting Firefox after changes. Many settings only take effect after a full restart (not just closing the tab).
Tips
- Test the same website in another browser (Edge or Chrome). If it works there, the issue is Firefox-specific; if it fails everywhere, it’s your system or network.
- Use Firefox’s built-in “Troubleshoot Mode” (Help > Troubleshoot Mode) to see if an extension is causing the problem. If the site loads in Troubleshoot Mode, disable extensions one by one.
- Check if the problem is only on one website. If so, that site’s TLS certificate may be expired or misconfigured—you can’t fix that, but you can report it to the site owner.
- Keep Firefox updated automatically. The browser regularly patches TLS vulnerabilities and compatibility issues.
Troubleshooting
If the error persists after all steps, try these additional checks:
- Test with a different network. Connect to a mobile hotspot or a different Wi-Fi. If the site loads, your router or ISP is interfering. Restart your router or contact your ISP.
- Check for proxy settings. In Firefox Settings > Network Settings, ensure “Use system proxy settings” is selected. If you have a manual proxy configured, try “No proxy” temporarily.
- Look at the error code. The “Secure Connection Failed” page often shows an error code like
SSL_ERROR_BAD_CERT_DOMAINorERROR_SSL_PROTOCOL_ERROR. Search that exact code for more specific fixes. - Reinstall Firefox. Uninstall Firefox via Windows Settings > Apps, then download the latest installer from mozilla.org and reinstall. Your profile is kept, but this replaces the program files which may be corrupted.
Frequently Asked Questions
Why does the TLS handshake error happen only on some websites?
If only one or a few sites fail, the problem is likely on the server side—the site’s certificate is expired, the server doesn’t support modern TLS, or the site is blocking your region. You can’t fix that from your end, but you can try accessing via a different browser or a VPN to confirm.
Will clearing cookies delete my passwords?
No. Clearing cookies removes site data like login sessions and preferences, but saved passwords (stored in the Password Manager) are kept. You’ll need to log in again to sites after clearing.
Can a VPN cause TLS handshake errors?
Yes. VPNs and some proxy extensions can interrupt the handshake. Disable your VPN or proxy and test. If it works, configure the VPN to allow Firefox traffic or switch to a different VPN server.
Is it safe to disable HTTPS scanning in my antivirus?
Temporarily, yes. The risk is that malicious sites may go undetected, but Windows Defender provides baseline protection. If you need to keep it disabled for performance reasons, consider using a different antivirus that doesn’t break TLS.
How long does the “Refresh Firefox” process take?
Usually under a minute. Firefox backs up your profile folder to your desktop, then creates a fresh one. Your extensions are removed, but you can reinstall them from the Add-ons page.
What if the error appears on every HTTPS site, even after resetting?
This suggests a system-wide issue. Try the “Flush DNS and reset network stack” step again, then check if Windows itself is up to date. If it still fails, run sfc /scannow in Command Prompt (Admin) to repair Windows system files.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Set a Google Play Budget & Stop Accidental Purchases
- Destiny 2 Error Code Anteater: Fixes & Causes
- View Android Photos on Chromebook: Step-by-Step
- Fix Windows Could Not Prepare the Computer to Boot
- Windows 11 Security Settings: Best Config Guide
- Install Custom Recovery on Samsung Galaxy Trend