How to Set Up HTTP Proxies in Any Browser

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 system-wide configuration on Windows, macOS, and Linux. At the end there is a quick test you can use to confirm the proxy is actually being used.

What you need before you start

From your control panel you should have:

• The proxy IP address (or hostname) and port — for example, 185.123.45.67: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://185.123.45.67:3128"

For per-tab or per-profile proxy control, use a browser extension such as Proxy SwitchyOmega (Chrome) or FoxyProxy (works in both). Extensions handle authentication prompts cleanly and let you toggle proxies without restarting the browser.

Firefox

Firefox has its own network settings independent of the OS:

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.

System-wide setup

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.

Windows applies this to most network traffic system-wide, including Chrome and Edge. Some apps (notably Firefox) ignore the system setting and need their own configuration.

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

The cleanest path is environment variables, which most command-line tools and many GUI apps respect:

export http_proxy="http://username:[email protected]:3128"
export https_proxy="http://username:[email protected]:3128"

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

Authentication: IP whitelist vs username/password

Both auth methods work. The right choice 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.

You can switch between auth methods any time 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.

Command-line test for cURL users:

curl -x http://username:[email protected]: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.