How to Fix "The Proxy Server Is Refusing Connections" in Firefox
Two fixes for Firefox and system settings, then a cURL, Python and Node.js test that prints the proxy's reply.
Updated
TL;DR
"The proxy server is refusing connections" means Firefox could not get through its proxy: no program accepted the connection on the proxy's port, or the proxy declined the request. If you never meant to use a proxy, select No proxy in Connection Settings and reload.
What Firefox shows
One page covers a closed proxy port, a cancelled proxy sign-in, and a 403, 429, 501 or unlisted reply to an https tunnel. The tab title reads Problem loading page.
| Where | What you see |
|---|---|
| Firefox desktop, current release and ESR 153 | The proxy server is refusing connections. Firefox can't connect to the server at example.com. What can you do about it? Contact your network administrator to make sure the proxy server is working. |
| Firefox ESR 140 (older page design) | The proxy server is refusing connections. Firefox is configured to use a proxy server that is refusing connections. Check the proxy settings to make sure that they are correct. Contact your network administrator to make sure the proxy server is working. |
| Firefox with its built-in VPN turned on | Couldn't connect to VPN. Try again in a few minutes. |
| Firefox for Android (refused connection) | Proxy Server Refused Connection. The browser is configured to use a proxy server, but the proxy refused a connection. |
| Firefox, related page (proxy replied 502 or 503, or a SOCKS handshake failed) | Unable to connect. Firefox can't connect to the server at example.com. |
| Firefox, related page (HTTP proxy host name did not resolve) | Unable to find the proxy server. Firefox can't connect to the server at example.com. |
Why this happens
Firefox loads every site through its proxy, so when the proxy says no, nothing loads.
A common reason is a stale entry: the app or service it points to has stopped, so nothing listens on that port. New profiles follow the system proxy, so a leftover Windows or macOS proxy counts too.
Diagnose your proxy refusal first
Find where Firefox gets its proxy, then ask the proxy itself what it answers.
Type proxy into Find in Settings and open Configure proxy; if an add-on is named above the options, that add-on controls Firefox's proxy.
Read the host under Manual proxy configuration; 127.0.0.1 or localhost means the proxy is a program on this computer.
If Settings shows a managed-browser notice, click it; a Proxy entry in about:policies means IT set the proxy and may have locked it.
Run the third card's test; 200 means the proxy works, another code is its refusal, and no reply means a wrong or closed port.
Look up other codes in your provider's error list; on Geonode, 465 means no proxy in the chosen location, 466 a reached bandwidth limit.
Solutions ranked by effectiveness
Start with Firefox's own entry, then look outside it; the code card tests a proxy you keep.
- Most common fix
Correct or clear Firefox's proxy entry
Applies when Manual proxy configuration is selected under Configure proxy. In ESR 140, click Settings under General > Network Settings.
If you never chose a proxy, pick No proxy and click OK.
To keep the proxy, paste its host and port from your provider's dashboard again.
Use the HTTP port in HTTP Proxy and tick Also use this proxy for HTTPS.
When Firefox asks for the proxy login, enter it and click Sign in, not Cancel.
- Check next
Remove the add-on or system proxy behind it
Applies when Firefox follows the system proxy or an add-on sets it; switch off whichever supplies the dead address.
In Connection Settings, click Disable Extension next to the add-on's name.
Switch off add-ons that route requests themselves, such as FoxyProxy, in about:addons.
On Windows, switch the proxy off in Settings > Network & internet > Proxy.
On a Mac, in System Settings > Network, turn off proxies in your network's Details.
- For developers
Ask the proxy directly, outside Firefox
Applies when you keep the proxy; current Firefox leaves its answer off the page. Use the HTTP host and port; curl prints 000 when no reply came.
curl -sS -o /dev/null -w "Proxy replied: %{http_connect}\n" \ -x http://USERNAME:PASSWORD@proxy.geonode.io:9000 \ https://example.com
Stop the proxy refusal from coming back
Habits that keep a stopped or forgotten proxy from breaking every site.
Create a second profile in about:profiles for proxy work; each profile keeps its own proxy settings.
In a PAC script, name a second proxy after the first; Firefox moves on when the first refuses the connection.
Firefox then skips the failed proxy for 30 minutes, so click Reload in Connection Settings once it is fixed.
Related errors
Learn more
FAQ
A country for each port
Port Configuration saves a country and session type on each HTTP port you add.


