How to Set Up HTTP Proxies in Any Browser

Step-by-step setup for Chrome, Firefox, Safari and Edge, plus the operating-system proxy settings on Windows, macOS and Linux, with a test to confirm which apps use the proxy.


Once you have proxy credentials, the actual setup is short. The challenge is usually knowing where each browser hides the setting and which authentication method to pick. This guide covers Chrome, Firefox, Safari, and Edge, then the operating-system proxy settings on Windows, macOS, and Linux. A browser or OS proxy setting only covers the apps that read it, not every connection your machine makes, so at the end there is a quick test to confirm which apps are actually using the proxy.

What you need before you start

From your control panel you should have:

  • The proxy IP address (or hostname) and port: for example, 203.0.113.10:3128.
  • Either your username and password (for password auth) or your machine’s public IP whitelisted in the control panel (for IP-whitelist auth).

If you do not know your machine’s public IP, visit ifconfig.me from the device that will use the proxy. Whatever address shows up there is what you whitelist.

Browser setup

Chrome and Edge (Chromium-based)

Chromium browsers do not have their own proxy settings on Windows or macOS: they use the operating system’s settings. See the system-wide instructions below. On Linux, both browsers respect command-line flags:

google-chrome --proxy-server="http://203.0.113.10:3128"

If you want a proxy in one browser only, or want to switch proxies without changing OS settings, a proxy-management extension can do it. Before installing one, check that it is still maintained, who publishes it, and what permissions it asks for. The original Proxy SwitchyOmega project, for example, is no longer maintained, so we do not recommend it. An extension only affects the browser (and usually the profile) it is installed in.

Firefox

Firefox has its own network settings. It can follow the system proxy, or you can set a proxy for Firefox alone:

  1. Open Settings → General, scroll to Network Settings, click Settings...
  2. Select Manual proxy configuration.
  3. Enter the proxy IP and port in HTTP Proxy.
  4. Check Also use this proxy for HTTPS.
  5. Click OK. The next page load will prompt for credentials if you are using password auth.

Safari

Safari uses macOS system proxy settings: see the macOS instructions below. There is no in-browser proxy panel.

Operating-system proxy settings

The OS proxy setting is read by apps that choose to use it, mainly browsers and apps built on the system networking libraries. It is not a tunnel for all traffic: apps with their own proxy settings, many command-line tools, games, and apps that open their own connections can ignore it. Test each app you need to route.

Windows 10 / 11

  1. Open Settings → Network & Internet → Proxy.
  2. Under Manual proxy setup, toggle Use a proxy server on.
  3. Enter the proxy IP and port.
  4. Click Save.

Chrome and Edge use this setting. Firefox uses it only when its own Network Settings are set to use the system proxy. Command-line tools such as curl generally read environment variables or their own flags instead, so set those separately.

macOS

  1. Open System Settings → Network.
  2. Select your active connection (Wi-Fi or Ethernet) → Details → Proxies.
  3. Enable Web Proxy (HTTP) and Secure Web Proxy (HTTPS), entering the proxy IP and port for each.
  4. If using password auth, check Proxy server requires password and enter the credentials.
  5. Click OK, then Apply.

Linux

For command-line tools, the usual path is environment variables. Many tools read them, but not all do, and some only read the upper-case or lower-case form, so check each tool:

export http_proxy="http://username:password@203.0.113.10:3128"
export https_proxy="http://username:password@203.0.113.10:3128"

For GNOME-based desktops, also set the proxy in Settings → Network → Network Proxy for GUI applications that read the desktop setting. KDE has the equivalent panel under System Settings.

Authentication: IP whitelist vs username/password

USA private, Spain and Italy plans support both methods; USA shared plans use IP whitelist only (ask support if you need username and password). Where you have the choice, it depends on your environment:

  • IP whitelist is simpler for fixed-IP machines: your office desktop, a static-IP server. Add your public IP in the control panel, then connect with no credentials. The downside is that you have to update the whitelist every time your IP changes, which can be never (static IP) or constantly (mobile, dynamic ISP).
  • Username/password works from any IP, which makes it the right pick for laptops on changing networks, cloud machines with rotating IPs, or scraper fleets running across multiple servers. The downside is that you have to handle credential storage and rotation yourself.

Whitelisted IPs and your proxy username and password are both managed from the EZProxies control panel.

Testing the connection

The fastest test: visit ifconfig.me through the configured browser. If the IP shown is the proxy’s IP (not your real one), it is working. If it shows your real IP, the proxy is not actually in the request path: check the browser’s settings or restart it after changing OS settings.

A passing browser test only proves that browser uses the proxy. Run the same check from every other app or tool you meant to route, because each one may read a different setting. When you turn the proxy off again, repeat the check and confirm your own IP shows.

Command-line test for cURL users:

curl -x http://username:password@203.0.113.10:3128 https://ifconfig.me

Should print the proxy’s IP. If you get a 407 Proxy Authentication Required, check the credentials. If you get a connection timeout, check that the proxy IP and port are reachable from your network (some corporate firewalls block outbound connections to non-standard ports).

Troubleshooting common errors

  • HTTP 407: authentication failed. Double-check username/password, or check that the source IP is actually whitelisted in your control panel.
  • HTTP 403: the proxy refused the request. Often means the destination is on a block list or your account is suspended.
  • Connection timeout: your network cannot reach the proxy. Check firewall rules and that the port is not blocked.
  • Browser still shows real IP: the proxy is configured but not actually being used. Restart the browser; on Windows make sure the proxy is enabled in Settings, not just configured.

If something is broken and the above does not solve it, contact support with the exact error and we will work it through with you.

Ready to try it? Datacenter plans go live when payment clears.