Unblock a Website in Firefox: Settings That Actually Apply
The short answer
In Firefox, open Settings, search for Network Settings, and set a manual HTTP proxy, or use an extension that does the same per site. Check that DNS-over-HTTPS is not overriding your resolver. If the block is on your network rather than the browser, no Firefox setting changes it.
Firefox is the browser where a proxy actually takes effect without touching the operating system, which makes it the fastest place to test whether an address change fixes a block. It is also the browser with a second, less obvious setting, DNS-over-HTTPS, that can quietly keep a filtered lookup in place even after you change the proxy.
The two Firefox settings that matter
Network Settings is where a manual proxy lives: HTTP proxy, port, and the option to use it for all protocols. Firefox applies it to the browser only, so the rest of the machine is unaffected. That isolation is useful for testing and for keeping a work profile on the normal connection.
DNS-over-HTTPS is switched on by default in recent versions. It sends lookups to a chosen provider inside the browser, which can be helpful or can be the reason a blocked name still resolves to a filtered answer. If you have changed the proxy and the site still fails to load at all, turn this setting to off and retest.
A proxy per site rather than for everything
Firefox does not offer per-site proxying natively. The practical options are an extension that routes chosen domains through a proxy, or a separate Firefox profile with its own proxy settings, launched for the sites that need it. A second profile keeps work traffic on the normal connection and avoids routing everything through one address.
If you use a SOCKS5 proxy, choose Manual proxy configuration, enter the SOCKS host and port, and pick SOCKS v5. Firefox will then pass the hostname to the proxy rather than resolving it locally, which matters when the lookup itself is filtered.
- Settings, then General, then search for Network Settings at the bottom of the page.
- Fill SOCKS Host and Port, choose SOCKS v5, and leave the HTTP proxy fields empty unless you have one.
- Remove the localhost and 127.0.0.1 entries from "No proxy for" if you need local testing through the proxy.
- Close all Firefox windows after changing the setting; the preference applies to new connections.
When the browser is not the problem
If the site returns a block notice rather than failing to load, the request reached the site and the site refused it. That decision is about the address the request came from, so the proxy must be the thing that changes it. A proxy that is configured but not actually used, common when the "No proxy for" list still contains the domain, produces exactly the same block notice.
Confirm the proxy is live by checking your apparent address in the browser after configuring it. If the address has not changed, the setting is not being applied, and everything you do afterwards is guesswork.
Worked example: a market research portal that refused one office
An analyst needed a competitor pricing portal that returned "not available in your region" from the office in Lagos and worked from a phone on mobile data. Firefox was already installed, so the first test was a manual SOCKS5 entry pointing at a private proxy address. The block notice vanished on the next request, which proved the portal was judging the source address and that a browser-level change was enough.
The first attempt had failed, though: the proxy was configured but the domain had been left in the "No proxy for" list from an earlier local-development setup. The request never went through the proxy, so the address had not changed. Removing that entry was the entire fix, and checking the apparent address in the browser before and after would have found it in a minute.
The team kept a second Firefox profile with the proxy set for that one portal. Everything else stayed on the office connection, and no operating-system setting had to be touched for a single site.
Firefox symptom, cause, and the setting that addresses it
| What you see | Likely cause | Firefox setting | Effect |
|---|---|---|---|
| Block notice from the site | Network address refused | Manual proxy or a proxy extension | Changes the source address |
| Site will not load at all | Lookup filtered in browser | DNS-over-HTTPS off | Uses your system resolver |
| Works in Chrome, not Firefox | Different proxy or DoH setting | Compare both browsers | Find the difference |
| Proxy set, address unchanged | Exclusion list or extension off | "No proxy for" and extension state | Makes the proxy apply |
| Login page loops | Cookies from the blocked session | Clear site data for that domain | Fresh session |
Firefox settings affect Firefox only; a phone or another browser on the same machine keeps the old behaviour until it is configured too.
In order, so you do not chase the wrong cause
- 1Reproduce the block in a private window with extensions disabled.
- 2Open Network Settings and confirm no manual proxy is set before you add one.
- 3Set the proxy, then check the apparent address has actually changed.
- 4Turn DNS-over-HTTPS off if the name itself fails to resolve, then retest.
- 5Clear site data for the domain so the old session is not carried over.
Where this connects on this site
- If you also need the other browser configured, see the Chrome equivalent of this setup
- For an address that is not shared with strangers, compare private proxy plans
- To see the situations people hit most often, browse which sites this is commonly needed for
What this will not do
- A Firefox setting cannot change a block applied to your whole network by a router or firewall before the browser sees it.
- A proxy does not reset an account restriction; signing in with a restricted account can still be refused.
- Free public proxies are visible to the site and often already blocked, so a failure does not prove the approach is wrong.
- No configuration here guarantees access; the destination decides what it serves and can change that at any time.
Questions this page gets asked
- Does Firefox have a built-in VPN I can use instead?
- Firefox offers a paid VPN in some regions, which routes your whole connection rather than just the browser. It is a different mechanism from a proxy and produces a different exit address. A manual proxy is the more precise tool when you need one site to leave from one address.
- Why does the proxy work in Firefox but not in Chrome on the same PC?
- Chrome on Windows and macOS uses the system proxy settings, so a proxy entered only in Firefox is invisible to it. That is expected. Configure the proxy in the operating system for Chrome, or keep the work in Firefox.
- Do I need to restart Firefox after changing the proxy?
- You should. Existing connections can persist, particularly with HTTP keep-alive and HTTP/2, so a site may keep using the old route until the connection is closed. Closing all windows and reopening is the reliable way to be sure the new setting is in effect.
Last reviewed 2026-10-27. Written for readers in the United States and elsewhere; rules about access, email and consent differ by country, and nothing on this page is legal advice.