Fix Firefox Blocking Access to Local IP Addresses

Firefox sometimes refuses to load pages on your own network, like 192.168.1.1 or a NAS address, even when the device itself is running fine.

The usual causes are HTTPS-Only Mode and a proxy bypass list that skips your LAN range. Work through the settings below in order, starting with the quick toggles and leaving about:config for last.

In this guide, I have covered:

Why Firefox Refuses to Load Local IP Pages

Your router page at http://192.168.1.1 opens fine in another browser, but Firefox throws an error. Nothing is broken on the device. Firefox is applying a security rule that was never designed for a home network.

Two settings cause most of these failures: HTTPS-Only Mode and the proxy bypass list. Mozilla’s HTTPS-Only Mode write-up explains the feature was built to push every site onto TLS, which is exactly why a NAS or printer without a certificate fails to load.

A bypass list that leaves out your LAN range sends local traffic to the proxy, or drops it. Either way, the request never reaches the device you are trying to manage.

Work through the fixes below in order. The first two are quick toggles in Settings. The about:config edits come last, and only if the toggles do not help.

Check the URL Bar and Address Spelling First

Before you change any setting, rule out the obvious. Some routers serve only HTTP, others only HTTPS, and a stray :8443 or trailing slash sends the page nowhere.

1. Type the IP directly into the address bar, without https:// in front.
2. If Firefox shows a “Secure Connection Failed” page, click the padlock in the address bar to see what the browser objected to.
3. Try the same URL with http:// explicitly added, then with https:// explicitly added, to see which one your device actually serves.
4. If your device’s admin page lives at a custom port like http://192.168.1.1:8080, include the port.

If the page loads with one prefix but not the other, the device speaks only that protocol. HTTPS-Only Mode is then the wrong setting to keep on. Move to the next fix.

Fully Disable HTTPS-Only Mode as a Test

This is the first setting worth testing. When HTTPS-Only Mode is on for all windows, Firefox silently rewrites every http://192.168.x.x request to https://. Most home routers, printers, and NAS boxes do not run TLS, so the rewrite fails.

Turn it off temporarily. If the local page loads, you have found the cause, and you can narrow the protection to private windows only.

1. Click the hamburger menu at the top right and choose Settings.
2. Select Privacy & Security from the left sidebar.
3. Scroll to HTTPS-Only Mode.
4. Select "Don't enable HTTPS-Only Mode."
5. Reload the page that was blocked.

You’ll know it worked when the LAN page renders without a certificate warning. Once it does, open Settings → Privacy & Security → HTTPS-Only Mode again and pick Enable HTTPS-Only Mode in private windows only if you still want the upgrade protection for everyday browsing.

Loopback addresses such as localhost, 127.0.0.1, and [::1] are never sent through any configured proxy. If those fail, the cause is HTTPS-Only Mode, an extension, or DNS, not the proxy list.

Stop Firefox From Auto-Upgrading HTTP to HTTPS

HTTPS-Only Mode is off, yet the address bar still flips to https://. Firefox has a second upgrade path, controlled by browser.fixup.fallback-to-https in about:config.

1. In the address bar, type about:config and press Enter.
2. Click Accept the Risk and Continue.
3. In the search field at the top, type browser.fixup.fallback-to-https.
4. Click the toggle on the right to set it to false.
5. Reload the local page in Firefox.

Setting it back to true later restores the upgrade. The change lives in the profile you are editing, so other profiles on the same machine keep their own value.

TIP:
The same preference also forces HTTPS for address-bar typos such as http//example.com. Disabling it makes Firefox fall back to a search instead of trying HTTPS first, which is sometimes what LAN hosts need.

Add Local Addresses to the Proxy Bypass List

If your network runs a proxy (work, school, VPN, or one you added by hand), Firefox sends LAN traffic through it unless those hosts sit in the bypass list. The default list covers localhost, 127.0.0.1. Private ranges like 192.168.x.x and 10.x.x.x need to be added.

1. Open the menu and choose Settings.
2. Click General in the left sidebar.
3. Scroll to the bottom and click Settings… next to Network Settings.
4. Confirm the dialog title reads Connection Settings. If Configure Proxy Access to the Internet is set to Use system proxy settings, Firefox is following your OS proxy, and editing this list will not help.
5. In the No proxy for field, type the addresses to bypass, separated by commas. A safe starter list is localhost, 127.0.0.1, 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12, .local.
6. Click OK and reload the LAN page.

Wildcards inside IPv4 octets are not supported. You cannot write 192.168.*.*. The parser expects literal hosts or CIDR ranges such as 192.168.0.0/16.

If you are using a work or school proxy, contact IT before changing proxy settings. A corporate proxy may also block private ranges on purpose as a security boundary.

Disable an Extension That May Be Blocking LAN Traffic

Extensions tamper with requests on private addresses more often than you would expect. Privacy tools that strip tracking parameters, network filters, and Multi-Account Containers all touch LAN traffic. Containers treat a container tab as a different origin, even on localhost.

1. Click the puzzle piece menu in the toolbar.
2. Choose Manage Extensions.
3. Toggle off anything that touches requests, containers, or URLs (privacy blockers, HTTPS Everywhere forks, corporate policy extensions, ad blockers with custom filter rules).
4. Reload the LAN page in the same tab.

If the page loads, turn the extensions back on one at a time to find the offender. A private window (Ctrl+Shift+P or Cmd+Shift+P) is the faster check: extensions are off there by default, so a page that loads in private mode points straight at an add-on.

Stale data can also keep an old error on screen. Clearing Firefox cookies and cache for that host forces a fresh request.

Refresh Firefox If Nothing Else Works

Nothing above worked, so you are down to the last resort. Refresh keeps your bookmarks, history, and saved logins, but resets every preference, disabled extension, and stored permission back to defaults.

1. Open the menu and choose Help.
2. Pick More Troubleshooting Information.
3. Click Refresh Firefox….
4. Confirm with Refresh Firefox again.
5. Re-test the local page.

If a refreshed Firefox still refuses http://192.168.x.x, open the same address in another browser on that machine. When every browser fails, the device, your firewall, or a VPN is the blocker, not Firefox.

If the trouble started right after a Firefox update, downgrading to an older Firefox version is the other way to confirm it.

RELATED: Reset Mozilla Firefox Browser Settings on the Computer