Troubleshooting 4 min read

Proxy Works in curl but Not in the Browser? Here's Why

curl does exactly what you tell it. Browsers layer system settings, extensions, cached credentials and protocol limits on top. Here's where they differ.

When a proxy works in curl but not in the browser, the proxy itself is fine. curl proves the host, port, credentials and plan all work. The difference is in how the browser is configured and what it supports, because browsers don't take a proxy URL the way curl does. They read system settings, apply bypass rules, cache credentials, defer to extensions, and simply don't support some proxy features. This guide lists the differences that matter, in the order they usually bite.

Start with a Known-Good curl Command

curl -x http://USERNAME:[email protected]:8080 https://api.ipify.org

Write down exactly what works: protocol (http), host, port (8080) and the full username including any options like -country-us. Everything below compares the browser against that.

Difference 1: Browsers Don't Take Credentials in the Proxy Address

curl accepts USERNAME:PASSWORD@host in the proxy URL. Browser and operating system proxy fields take only a host and a port. If you paste the full URL into the host field, the browser tries to connect to a host literally named "USERNAME:[email protected]", which fails with ERR_PROXY_CONNECTION_FAILED. Enter global.nodeproxies.xyz and 8080, and the browser will prompt for credentials on the first request. See how to set up a proxy in Chrome or Firefox proxy setup.

Difference 2: SOCKS5 Authentication Isn't Supported

curl --proxy socks5h://USERNAME:[email protected]:1080 works fine. Chrome doesn't support SOCKS5 with username and password at all, and Firefox's settings have no fields for SOCKS credentials. If your curl test used SOCKS5, switch the browser to the HTTP endpoint on 8080. Details in SOCKS5 authentication failed.

Difference 3: Cached or Saved Wrong Credentials

If you mistyped the password once and saved it, the browser keeps sending it and you see ERR_TUNNEL_CONNECTION_FAILED or a repeated prompt. Fully quit and reopen the browser to clear session credentials, and remove the saved entry from the browser's password manager if it was stored there. Then re-enter the username exactly as in your working curl command, options included.

Difference 4: Something Else Overrides the Proxy

In Chrome, open chrome://net-internals/#proxy to see the effective configuration. You may find:

  • A proxy or VPN extension controlling the settings. Only one extension can control proxy settings at a time, and it overrides system settings.
  • A PAC script that sends some or all hosts direct.
  • A bypass list that includes the site you're testing. Many setups bypass localhost, local network names and sometimes specific domains.
  • Enterprise policies that force a different proxy.

In Firefox, check Settings, then Network Settings: Firefox can use its own proxy settings independently of the system.

Difference 5: The Browser Leaks Your Real IP to the Test Page

Sometimes the proxy works in the browser, but an IP test page shows your real IP anyway. Pages that use WebRTC can discover local and public addresses outside the HTTP proxy path. Check the HTTP-visible IP with what is my IP or https://api.ipify.org, which only report the address the request came from. For more, see DNS leaks and proxies.

Difference 6: The Site Treats Browsers and curl Differently

Occasionally a site loads in curl but fails in the browser through the same proxy because the browser carries cookies, a stored region, or service worker caches from earlier direct visits. The site sees an existing session suddenly arriving from a different IP. Test in a private window or a fresh browser profile.

Difference 7: Different Protocol Behavior

  • Browsers prefer HTTP/2 and sometimes HTTP/3 to the site; curl may use HTTP/1.1 by default. Through an HTTP proxy, HTTPS still goes over a CONNECT tunnel, so this rarely matters for the proxy, but it can change how the site responds.
  • Browsers enforce HSTS and certificate rules strictly. If your network intercepts TLS, curl -k might have hidden it; the browser won't, so check for interception first.

A Five-Minute Checklist

  1. Use the HTTP endpoint in the browser: host global.nodeproxies.xyz, port 8080.
  2. Put only host and port in proxy fields; enter USERNAME and PASSWORD in the prompt.
  3. Check chrome://net-internals/#proxy or Firefox's network settings for overrides.
  4. Disable proxy and VPN extensions you aren't using.
  5. Restart the browser to clear cached credentials, then test in a private window.

Browser Proxies with NodeProxies

Every plan works over HTTP on 8080, which all major browsers support with a credential prompt. For multiple browser identities, a dedicated profile per identity with its own sticky session id works better than switching system settings; see proxies for antidetect browsers. Register to get credentials.

FAQ

Why does my proxy work in curl but Chrome says ERR_PROXY_CONNECTION_FAILED?

Most often the credentials were pasted into the host field, or the wrong port or a SOCKS endpoint was used. Enter only host and port, and use the HTTP endpoint.

Can I put username and password in Chrome's proxy settings?

No. Chrome prompts for HTTP proxy credentials when needed, or an extension can supply them.

Why does the browser show my real IP with a proxy?

Either the proxy isn't applied (check overrides and bypass lists) or the test page uses WebRTC. Test with an HTTP-only IP checker.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account