If Firefox shows “SSL_ERROR_BAD_MAC_ALERT,” it means the secure connection was interrupted because a message authentication code (MAC) check failed during the TLS handshake. The fix usually involves clearing your cache, disabling experimental TLS settings, or resetting Firefox’s security settings—start with the steps below, then work through the deeper causes if the error persists.
What Causes the Bad MAC Alert
The “bad MAC” error is a TLS alert (code 20) that the server sends when the integrity check on a handshake message fails. In plain terms, the data Firefox received did not match the cryptographic checksum the server computed, so Firefox aborts the connection to prevent tampering. Common triggers include:
- Corrupted cached SSL certificates or session data in Firefox.
- An outdated or misconfigured security software (antivirus, firewall, VPN) intercepting and modifying traffic.
- Firefox’s experimental TLS 1.3 settings or a custom “security.tls.version” preference that is set incorrectly.
- A network issue (proxy, router, or ISP) that corrupts packets mid-transmission.
- A server-side misconfiguration on the website, though this is less common.
Because the alert appears during the handshake, the page never loads, and you may see it on one site but not another, or intermittently on the same site.
Quick Fixes to Try First
- Clear the cache and cookies: Go to Menu ▾ > Settings > Privacy & Security, scroll to “Cookies and Site Data,” click “Clear Data…,” check both boxes, and click “Clear.” Then restart Firefox.
- Disable hardware acceleration: In Settings > General, uncheck “Use recommended performance settings” and “Use hardware acceleration when available.” Restart and test.
- Reset Firefox’s security settings: Type
about:configin the address bar, accept the warning, search forsecurity.tls.version, and reset any modified values to their defaults (right-click > Reset). Also search forsecurity.ssl.enable_ocsp_staplingand reset it. - Disable extensions temporarily: Open Menu ▾ > Add-ons and themes, disable all extensions, then re-enable one by one to isolate the culprit.
After each step, reload the page. If the error disappears, you’ve found the cause.
Advanced Troubleshooting: Network and Security Software
If the quick fixes fail, the problem likely lies outside Firefox. Antivirus suites with HTTPS scanning (e.g., Bitdefender, Kaspersky, Norton) and some corporate firewalls intercept SSL/TLS traffic to inspect it. This “man-in-the-middle” approach can break the MAC if the software’s certificate store is outdated or if it modifies packets incorrectly.
- Test in Safe Mode: Hold Shift and click the Firefox icon, or run
firefox -safe-mode. If the error disappears, a software conflict is likely. - Temporarily disable HTTPS scanning in your antivirus settings, then reload the page. If it works, update the antivirus or reinstall its root certificate.
- Check your VPN or proxy: Disconnect a VPN, or in Firefox go to Settings > Network Settings and select “No proxy.” If the error goes away, the VPN/proxy is altering traffic.
- Flush DNS and reset network: On Windows, run
ipconfig /flushdnsandnetsh winsock resetin an admin command prompt, then restart. On macOS, go to System Settings > Network, and renew the DHCP lease.
When the Problem Is on the Server Side
Sometimes the website itself is misconfigured—for example, a server that supports TLS 1.3 but has a broken cipher suite, or a load balancer that forwards corrupted handshake messages. You can confirm this by trying the same site in another browser (Chrome, Edge, Safari). If the error appears everywhere, it’s likely a server issue, and you should:
- Wait a few hours and retry; server admins often fix such issues quickly.
- Try a different network (e.g., mobile hotspot) to rule out your ISP.
- Contact the site owner with the exact error code and the time it occurred.
If the error only happens in Firefox, the problem is almost certainly local to your browser or system.
Resetting Firefox Completely
If nothing else works, a full refresh can eliminate corrupted profiles and settings without deleting bookmarks or passwords. Go to Menu ▾ > Help > More Troubleshooting Information, then click “Refresh Firefox” in the top-right corner. This resets preferences, disables extensions, and clears the cache, but keeps your personal data. After the refresh, re-test the problematic site.
If the error persists after a refresh, the issue is almost certainly external (network, security software, or the server). Consider creating a new Firefox profile (via about:profiles) to test further, but this is rarely necessary.
Frequently Asked Questions
Why does the error happen only on some websites?
If only one site fails, the server likely has a TLS configuration issue, or that site’s certificate chain is being modified by your security software. If the error is random across many sites, suspect network corruption or a VPN/proxy.
Can I disable TLS 1.3 to fix this?
Yes, but it’s not recommended because TLS 1.3 is more secure and faster. To test, go to about:config, set security.tls.version.max to 3 (which forces TLS 1.2), and reload. If the error disappears, the server or your security software has a TLS 1.3 bug. Re-enable TLS 1.3 later after updating software.
Does clearing the cache delete my passwords?
No. Clearing cache and cookies does not affect saved passwords, bookmarks, or history. Passwords are stored separately in the Login Manager, and you can back them up via Settings > Privacy & Security > Saved Logins.
Is this error a sign of a hacker attack?
Usually not. The MAC alert is a technical integrity failure, not an indication of malware. However, if you suspect interception, check your system for unusual network activity and keep your antivirus updated. The error itself is benign once the connection is aborted.
Will refreshing Firefox remove my extensions?
Yes, a refresh disables all extensions, but you can re-enable them later. Your passwords, bookmarks, and open tabs are preserved. After the refresh, Firefox creates a folder on your desktop with your old profile data for manual recovery.
What if the error appears in Chrome too?
If the same site fails in multiple browsers, the problem is not Firefox-specific. Check your system date and time (incorrect time breaks TLS certificates), disable HTTPS scanning in your antivirus, or try a different network. If it still fails, the server is likely at fault.
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
- How to View Wi-Fi Password on iPhone
- How to Stream on Twitch from PC
- GTM vs Facebook Pixel: What’s the Difference?
- Windows 10 Won’t Boot? Fix It in 30 Minutes
- Ubuntu 26.04 LTS Requirements & Hardware Checks
- ATK0100 Driver: Do You Need to Install It?