Firefox refusing to load pages — the spinner runs forever, the page goes white, or you get a connection error — almost always has one of three causes: a broken network stack, a corrupted Firefox profile, or an extension interfering with requests. The good news is you can tell which one in about 60 seconds. This fits into the wider topic we cover in our Google Chrome Errors.
Open a Private Window (Ctrl+Shift+P) and try loading the same page. Private windows disable extensions and use a fresh session. If the page loads in Private mode but not in regular Firefox, an extension is responsible — go straight to Fix 3. If it fails in Private mode too, you’re looking at a Firefox or network-level issue — continue below.
Try another browser. If Chrome or Edge also can’t load the page, the problem is your network or DNS, not Firefox.
Fix 1: Reset the network stack
This is the single most effective fix when Firefox stops loading pages suddenly with no obvious trigger — especially if it happened after a VPN install, a Windows update, or a security software change. The Windows network stack gets corrupted in ways that block Firefox specifically while other apps seem fine.
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsAdministrator Command Prompt. Run all three, restart. Don’t skip the restart — the winsock reset doesn’t fully apply until the machine reboots. Most “Firefox stopped loading pages overnight” situations resolve with this.
Fix 2: Clear Firefox cache and connection state
If Firefox is failing on specific sites but loading others fine, the issue is more likely cached bad data for those sites. Settings → Privacy and Security → scroll to Cookies and Site Data → Clear Data. Also: in the same section → Cached Web Content → clear it separately.
One common variant of this is when pages load but their media does not — if videos won’t play in Firefox while the rest of the page renders fine, the cause sits with the media stack rather than page loading.
For a site-specific nuclear option without clearing everything: right-click the padlock icon on the failing site → Clear cookies and site data. This removes only that site’s data without touching everything else.
Fix 3: Extensions
Ad blockers, privacy tools, VPN extensions, and script blockers are the most common extension culprits. The Private Window test already tells you if extensions are involved. To identify which one:
about:addons → Extensions → disable all → reload the page. Re-enable them one by one. The extension that breaks loading when enabled is the issue — update it, configure it to allow the site, or remove it.
uBlock Origin with strict settings, Privacy Badger, and some VPN extensions are the most frequent offenders. They’re not broken, they’re just configured to block something the site needs.
Fix 4: DNS settings in Firefox
Firefox has its own DNS-over-HTTPS setting that operates independently from Windows DNS. When the DNS-over-HTTPS provider is down or returns incorrect results, pages fail to load even though the operating system’s DNS works fine.
about:preferences#general → scroll to Network Settings → Settings → DNS over HTTPS → either disable it or change the provider to a different one (Cloudflare, NextDNS, etc.). If disabling DoH fixes the loading issue, the previous DoH provider was the problem — not Firefox or the sites.
Fix 5: Proxy settings
Firefox has its own proxy configuration that doesn’t always follow Windows’ system proxy. If a proxy is configured and unreachable — corporate proxy when working from home, a VPN proxy that was set up and forgotten — every page request fails.
about:preferences#general → Network Settings → Settings → connection settings. Check what’s selected. “Use system proxy settings” follows Windows. “Manual proxy configuration” with specific addresses is worth checking — if those addresses are stale, clear them and switch to “No proxy” or “Use system proxy settings.”
Fix 6: Firefox Refresh
When nothing else resolves widespread loading failures: Firefox menu → Help → More Troubleshooting Information → Refresh Firefox. This rebuilds the Firefox profile from scratch while keeping bookmarks, passwords, and history. Extensions are removed and need to be reinstalled — which is actually useful for diagnosing extension problems, since you can add them back selectively.
The Refresh process takes 2–3 minutes. It’s the right tool when Firefox has accumulated configuration or profile corruption over months or years of use.
Fix 7: Specific error codes
The error message Firefox shows matters. Each code points at a specific layer:
- PR_CONNECT_RESET_ERROR / ERR_CONNECTION_RESET — TCP connection reset, often security software or VPN
- PR_END_OF_FILE_ERROR — SSL/TLS handshake failed, check antivirus HTTPS inspection
- NS_ERROR_NET_TIMEOUT — Connection timed out, DNS or proxy problem
- MOZILLA_PKIX_ERROR_MITM_DETECTED — Antivirus intercepting HTTPS, needs certificate imported to Firefox
- SSL_ERROR_NO_CYPHER_OVERLAP — TLS protocol mismatch, usually a server using old TLS 1.0/1.1
Reading the error code saves trying fixes that don’t apply to the actual failure mode.
Antivirus HTTPS inspection
Worth calling out specifically because it causes a disproportionate share of “Firefox won’t load pages” issues: security suites that scan HTTPS traffic present their own certificate to Firefox instead of the website’s. Firefox, with its own certificate store (unlike Chrome which uses Windows’), doesn’t trust the antivirus certificate by default and refuses the connection.
If errors mention certificates or MITM: check whether the antivirus has an option to add its root certificate to Firefox automatically, or import it manually — Firefox Settings → Privacy and Security → Certificates → View Certificates → Authorities → Import → select the antivirus root certificate file.
Related Firefox issues around specific sites refusing to load often trace back to certificate problems covered in our Firefox secure connection guide. For the network-level problems that affect all browsers (not just Firefox), the DNS troubleshooting guide covers the Windows DNS stack fixes. Mozilla’s connection error documentation covers the full list of error codes with their specific causes and Mozilla’s recommended resolution for each.
about:config tweaks that cause loading failures
If someone (or you, following a performance guide) modified Firefox settings through about:config, those changes can cause loading failures that look like network problems. Specifically: security.tls.version.min set too high, network.http.max-connections-per-server set to 1, or cookie acceptance policies set to reject all — any of these can break page loading in non-obvious ways.
Check: about:config → search for any settings shown in bold (bold means modified from default). Reset each bold setting by right-clicking → Reset to Default. After resetting all modified settings, test the failing pages. If they load, one of the modified settings was causing the issue — re-apply the changes one at a time to identify which specific setting was responsible.
Hardware acceleration and page rendering failures
Firefox uses GPU hardware acceleration for rendering. When the GPU driver has compatibility issues with Firefox’s rendering pipeline — common after Firefox updates and GPU driver updates — pages may partially load, show white sections, or fail to render entirely while appearing to load (spinner stops but content doesn’t appear).
about:preferences#general → Performance section → uncheck “Use recommended performance settings” → uncheck “Use hardware acceleration when available” → restart Firefox. If pages now render correctly, GPU hardware acceleration was the cause. Update the GPU driver from the manufacturer’s website, then re-enable hardware acceleration — the updated driver usually resolves the rendering incompatibility.
Firefox stuck in “offline mode”
Firefox has a manual offline mode that can be accidentally activated. When enabled, Firefox refuses all network connections and shows errors for every page as if the network is down. File menu → if “Work Offline” has a checkmark next to it, that’s the issue. Click it to uncheck. Alternatively: the File menu might not be visible — press Alt to show the menu bar temporarily.
This sounds too obvious, but offline mode gets activated accidentally when Alt+F is pressed followed by W (File → Work Offline) and it persists across restarts. People spend 20 minutes troubleshooting what turned out to be a two-click fix.
Content blocking — Enhanced Tracking Protection
Firefox’s Enhanced Tracking Protection (ETP) in Strict mode blocks some tracking scripts and resources that some sites depend on for loading. The site’s content doesn’t load because Firefox blocked a resource the site considers essential.
Test: click the shield icon in the address bar → toggle “Enhanced Tracking Protection for this site” → reload the page. If it loads, ETP was blocking something the site needed. You can add the site to ETP exclusions (shield icon → Turn off protections for this site) without disabling ETP everywhere. Strict mode is the usual culprit — Standard mode is more conservative and rarely breaks sites.
IPv6 causing connection failures
Firefox prefers IPv6 connections. On networks where IPv6 is partially configured but not fully functional — common with some ISPs and older routers — Firefox times out trying to connect via IPv6 before falling back to IPv4. Pages appear to “load slowly” or time out entirely when the real problem is IPv6 timeouts.
Test: about:config → search for “network.dns.disableIPv6” → if it’s false, double-click to set it to true → restart Firefox and test. If pages load immediately, IPv6 was causing timeout delays. This is a browser-level workaround; the proper fix is correcting IPv6 configuration on the router, but the about:config change provides immediate relief.
Profile location and disk issues
Firefox stores its profile (cache, cookies, history, settings) on the system drive. If the drive is nearly full (under 2–3 GB free) or if the drive has read errors in the profile directory, Firefox may fail to load pages because it can’t write necessary session data during page loads.
Check: Settings → System → Storage → see how much free space remains on C:. Also run CrystalDiskInfo to check drive health. If S.M.A.R.T. shows warnings, the drive is degrading and Firefox’s profile data may be on affected sectors. Moving the Firefox profile to a different drive (Firefox Profile Manager, accessible via firefox.exe -P) is a temporary fix while the drive is replaced.
Multiple Firefox instances
Running multiple Firefox instances (not multiple windows, but multiple instances launched separately) can cause profile locking that prevents the second instance from accessing the profile data it needs. Pages fail to load because Firefox can’t read or write to the profile.
Check Task Manager for multiple firefox.exe processes. Close all of them → reopen a single Firefox instance. If Firefox shows a “Firefox is already running” error when launching: the profile is locked by a previous crashed instance. Navigate to the Firefox profile folder (about:support → Profile Directory → Open Directory) → delete the “lock” file → relaunch Firefox.
Firewall blocking Firefox specifically
Windows Defender Firewall or third-party firewalls can block specific applications. If Firefox was accidentally blocked — a security software update changed access rules, or a firewall prompt was dismissed incorrectly — Firefox’s network requests are blocked at the OS level before they even reach the DNS or network stack.
Windows Security → Firewall and network protection → Allow an app through firewall → check whether Firefox appears → confirm both Private and Public network access are checked for firefox.exe. If Firefox doesn’t appear in the list: Add another app → browse to firefox.exe (usually in C:Program FilesMozilla Firefox) → add it → allow both Private and Public.
Telemetry and connection testing built into Firefox
Firefox has a built-in connection test page: about:networking → this page shows DNS lookup times, open connections, and network status. The “HTTP tab” shows recent connections and their status codes. Loading this page while the site is failing can show whether Firefox is even attempting the connection (and failing) or not attempting it at all (indicating a proxy or offline mode issue).
Also useful: about:networking → DNS → manually look up the failing site’s domain. If DNS resolution succeeds here but the page still won’t load, the issue is past DNS — it’s at the TCP connection or TLS level. If DNS lookup fails, the DNS configuration is the problem, and the DoH settings or network stack reset is the fix.
For truly persistent loading failures that survive profile refresh, all configuration resets, and network stack fixes: test Firefox Nightly (Mozilla’s development build) or Firefox ESR (Extended Support Release) on the same machine. If one of these loads the page while the stable channel doesn’t, a bug in the current stable release is responsible, and waiting for the next Firefox update or reverting to the previous version through Mozilla’s FTP archive (ftp.mozilla.org/pub/firefox/releases/) resolves it. Firefox release bugs that affect page loading are uncommon but happen, and they get patched quickly given how many users would be affected.
A note on the order of fixes: the Private Window test and the winsock reset cover probably 60% of “Firefox won’t load pages” situations between them. Extensions (in Private mode) and the network stack (winsock reset) are the two most commonly corrupted layers, and checking both first before moving to profile refresh or reinstall saves significant time. The more exotic fixes — about:config settings, IPv6 disabling, hardware acceleration — are for the remaining cases where the common fixes were tried and didn’t resolve it. You might also run into Chrome Loading Pages Slowly.
