Firefox Won’t Load Pages | Quick Fix Guide

Seeing blank tabs, endless spinners, or “Hmm. We’re having trouble finding that site”? This step-by-step path gets sites open again fast. Start here.

Fast Triage: What You’re Seeing And What It Points To

Match your symptom to a likely cause, then jump to the fix. Keep this open while you try things.

Symptom	Likely Cause	Fast Fix
Only some sites fail	Cookies/cache, site data, HTTPS rule, bad DNS	Clear data, test HTTPS-Only, switch DNS
All sites fail in Firefox only	Add-on, profile glitch, proxy setting, antivirus HTTPS scan	Use Troubleshoot Mode, check proxy, disable scan
No browser loads anything	Network or router issue, ISP outage	Reboot router, test hotspot, call provider
Works on Wi-Fi but not on VPN	Blocked region or slow tunnel	Turn VPN off or change region
Secure sites fail, others work	Clock wrong, HTTPS-Only block, SSL inspection	Fix system time, review HTTPS setting, stop SSL scan
“Proxy server is refusing connections”	Wrong proxy config or policy	Set No Proxy or System Proxy

Check The Connection First

Open another browser and visit a site you never cached before. If nothing loads anywhere, power-cycle the router and modem, then try a phone hotspot. If the hotspot works, the issue sits with the original network.

Fix For Firefox Not Opening Websites On Any Network

This section handles cases where other browsers work or the issue follows Firefox across networks. Work through each step; you can stop when pages start loading.

1) Try Troubleshoot Mode

Menu → Help → Troubleshoot Mode → Restart. This starts Firefox with add-ons off, default theme, hardware acceleration off, and clean toolbar state. If sites load here, an extension or driver setting is likely at fault. Keep reading for how to narrow it down.

2) Clear Site Data And Cache

Go to Settings → Privacy & Security → Cookies and Site Data → Clear Data. Check both items and confirm. Then reload the problem page with Ctrl/Cmd+F5 to bypass stale assets. If only one site fails, click the padlock icon → Clear cookies and site data for this site, then sign in again.

3) Review HTTPS-Only Mode

HTTPS-Only upgrades every request to HTTPS. That’s great for safety, but older sites may not support it and will fail to load. Go to Settings → Privacy & Security → HTTPS-Only Mode and choose Off or Only private windows. Test the page. If it works now, leave HTTPS-Only off for daily browsing and keep it on for sensitive sessions.

4) Switch DNS (Or Toggle DoH)

Some networks hand out flaky DNS servers. In Firefox you can use encrypted DNS (DoH) or your system’s resolver. Go to Settings → General → Network Settings → Settings…. Under Enable DNS over HTTPS, toggle the box on, pick a provider, and test. If it was already on, turn it off and retry. You can also switch your system DNS to a public resolver and test again.

5) Check Proxy Or VPN

Still no luck? Open Settings → General → Network Settings → Settings…. Pick No Proxy or Use system proxy settings, then restart the browser. If you run a VPN, disconnect and retry. Many “proxy refusing connections” errors stem from a stale PAC file, a dead corporate proxy, or a locked policy on shared PCs.

6) Disable HTTPS Scanning In Antivirus

Security suites sometimes intercept TLS traffic to scan it, which can break handshakes or pin old ciphers. In the suite’s settings, turn off HTTPS or SSL scanning and retry. If that fixes it, update the suite or add Firefox to its trusted list.

7) Refresh The Profile (Non-Destructive)

Type about:support in the address bar and click Refresh Firefox. This keeps bookmarks, passwords, and open tabs, while rebuilding the core profile. Many edge-case glitches vanish after a refresh.

If Only One Site Won’t Open

When most pages load but one domain fails, the cause is usually stale cookies, a redirect loop, or a mismatch between cached HTTP and live HTTPS.

Targeted Fixes That Work

• Hard reload: Ctrl/Cmd+Shift+R forces a fresh fetch.
• Clear only this site’s data: Click the padlock → Clear cookies and site data.
• Drop HSTS for the site: about:preferences#privacy → View Certificates → Servers → find the host → Delete.
• Turn off Enhanced Tracking Protection for that site: Click the shield → toggle off → reload.

When No Browser Loads Anything

If every browser times out, look beyond the app. Reboot the PC, then the router. Check the ISP status page on a phone with mobile data. Pull the modem’s power for 30 seconds. If a phone hotspot works while the home router does not, flush the router’s DNS cache.

Deep Dives: What Each Step Proves

Curious why these tests work? Here’s the logic, written in plain terms.

Troubleshoot Mode Proves Add-On Or Driver Faults

Disabling add-ons and hardware acceleration strips away layers that can block scripts, rewrite traffic, or trip GPU bugs. If pages load here, re-enable add-ons in batches until the break reappears, then remove the last batch one by one. Update the graphics driver if video or canvas elements glitch.

Cache And Cookies Flush Bad State

Sites flip between domains, CDNs, and login states. Old cookies and cached redirects can trap the browser in loops or point it at dead hosts. Clearing restores a clean handshake with the server and fetches fresh assets.

HTTPS-Only And SSL Inspection Explain Secure-Only Failures

If secure pages fail while plain ones load, two knobs stand out: an upgrade rule in the browser and man-in-the-middle scanning by security tools. Turn one off at a time to see which one blocks the handshake.

DNS And DoH Test The Name Lookup Path

Names turn into IP addresses through resolvers. When the resolver is down or filtered, sites appear gone. Toggling DoH or swapping resolvers sends your query down a different path and often restores reachability.

Proxy And VPN Settings Control The Route

If traffic must pass through a proxy or VPN, one stale rule can block every request. Resetting to No Proxy or pausing the VPN sends traffic direct, which proves whether the middle hop is the culprit.

Mac, Windows, And Linux Paths You’ll Use

Menu paths differ a bit across platforms. Here’s a quick map for common moves.

Task	Windows/macOS	Linux
Open Troubleshoot Mode	Menu → Help → Troubleshoot Mode	Same path; or run firefox -safe-mode
Clear site data	Settings → Privacy & Security → Cookies and Site Data	Same
Network settings	Settings → General → Network Settings → Settings…	Same
Refresh profile	about:support → Refresh Firefox	Same

Quick Edge Cases That Trip People Up

System Clock Is Off

HTTPS needs a correct clock. Sync time with the OS time service, then retry the site.

Captive Portals On Public Wi-Fi

Hotel or airport Wi-Fi often needs a login. Visit a plain http page like http://neverssl.com to trigger the portal, sign in, then switch back to your page.

Profile Corruption After A Crash

If Firefox closed mid-write, databases inside the profile can go bad. A refresh rebuilds them while keeping key data. If the refresh helps only briefly, create a new profile with about:profiles and migrate bookmarks and logins.

Enterprise Policy Locks

On work PCs, proxy and DoH can be locked by policy. Type about:policies to view active rules. If the proxy type value is locked, talk to IT or use another network.

When To Reinstall

A clean install is rare, since Refresh usually fixes profile issues. If you still see strange behavior after Refresh and new profile tests, remove Firefox, delete the program folder, and install the latest release. Keep your profile folder or sync account so you don’t lose data.

Keep It Stable Next Time

• Limit extensions to what you trust and keep them updated.
• Use one content blocker, not three.
• Update graphics drivers and Windows/macOS/Linux regularly.
• Pick one DNS path and stick with it once stable.
• Avoid mixing VPN, custom proxy, and security suite filters unless needed.

Helpful References

For deeper setup details, see Mozilla’s connection-troubleshooting steps and Firefox DNS over HTTPS. Both pages track current menu paths and settings names.