Set up a proxy in your browser to route traffic through a proxy server for privacy, access control, or testing. This guide walks you through Chrome, Firefox, Edge, and Safari with clear steps for Windows, macOS, and Linux.
Learn more in our Proxy Basics Guide → https://www.proxiesthatwork.com/guides/proxy-basics
What you need before you start
- Proxy type: HTTP, HTTPS, or SOCKS5
- Server address and port (example: proxy.example.com:8080 or 203.0.113.10:1080)
- Optional credentials: username and password
- Optional PAC file URL (example: https://cdn.example.com/proxy.pac)
Quick visual: values you will enter
Server: proxy.example.com
Port: 8080
Type: HTTP (or HTTPS or SOCKS5)
Username: alice
Password: ••••••••
Bypass: localhost, 127.0.0.1, *.internal, *.local
Example inputs
HTTP/HTTPS: http://proxy.example.com:8080
SOCKS5: socks5://203.0.113.10:1080
PAC file: https://cdn.example.com/proxy.pac
Tip: Keep your proxy credentials handy. Some systems will prompt once and save them to the OS keychain/credential manager.
Google Chrome
Chrome normally uses your system proxy settings. You can also force a Chrome-only proxy with a command-line flag.
Option A — Use system proxy (recommended)
Windows 11/10
- Open Settings > Network & Internet > Proxy.
- For a manual proxy: turn on Use a proxy server.
- Enter Server and Port. Optional: add exceptions in Do not use proxy server for.
- Save, then restart Chrome.
macOS (Sonoma/Ventura/Monterey)
- Open System Settings > Network.
- Select your active network (Wi‑Fi or Ethernet), click Details (or Advanced) > Proxies.
- Check Web Proxy (HTTP) and/or Secure Web Proxy (HTTPS); enter server and port.
- Check Proxy server requires password if needed and enter credentials.
- Click OK > Apply, then restart Chrome.
Linux (GNOME)
- Open Settings > Network > Network Proxy.
- Choose Manual; fill HTTP/HTTPS/SOCKS fields and port.
- Add ignored hosts (bypass list) as needed; Apply, then restart Chrome.
Visual guide
Chrome
→ System Settings
→ Network / Internet
→ Proxy
→ Manual configuration
Option B — Chrome-only proxy (advanced)
Start Chrome with a specific proxy without changing the OS setting.
--proxy-server=http://proxy.example.com:8080
--proxy-server=socks5://203.0.113.10:1080
--proxy-pac-url=https://cdn.example.com/proxy.pac
Launch examples
open -a "Google Chrome" --args --proxy-server=http://proxy.example.com:8080
google-chrome --proxy-server=http://proxy.example.com:8080
chrome.exe --proxy-server=http://proxy.example.com:8080
Authentication
- Chrome will prompt for credentials when required.
- Storing credentials: Chrome delegates to your OS credential manager.
- URL-embedded credentials (user:pass@host) are often blocked for security; prefer the prompt.
Mozilla Firefox
Firefox has its own per-browser proxy settings that do not depend on the OS (unless you choose Auto-detect).
Steps
- Open Firefox.
- Menu (☰) > Settings > General.
- Scroll to Network Settings and click Settings.
- Choose one:
- Manual proxy configuration
- HTTP Proxy: enter host and port.
- Check Use this proxy server for all protocols (or set HTTPS/SOCKS separately).
- For SOCKS, select SOCKS v5 for DNS support.
- Automatic proxy configuration URL (PAC)
- No proxy for: add localhost, 127.0.0.1, *.local, *.internal.
- Click OK and restart tabs.
DNS with SOCKS
- To send DNS over the proxy, ensure SOCKS v5 is selected and Proxy DNS when using SOCKS v5 is checked.
Authentication
- Firefox prompts for credentials when a site first loads through the proxy. You can save them.
Visual path
Firefox
→ Settings
→ General
→ Network Settings
→ Settings…
→ Manual or PAC
Microsoft Edge
Edge uses Windows system proxy by default, similar to Chrome. You can also launch Edge with a specific proxy flag.
Option A — Use Windows proxy
- Open Settings > Network & Internet > Proxy.
- Turn on Use a proxy server.
- Enter Server and Port. Add exceptions.
- Save, then restart Edge.
Option B — Edge-only proxy (advanced)
msedge.exe --proxy-server=http://proxy.example.com:8080
msedge.exe --proxy-pac-url=https://cdn.example.com/proxy.pac
Apple Safari (macOS)
Safari uses the macOS system proxy configuration.
Steps
- Open System Settings > Network.
- Select your active network (Wi‑Fi or Ethernet), click Details (or Advanced) > Proxies.
- Enable Web Proxy (HTTP) and/or Secure Web Proxy (HTTPS); enter server and port.
- Check Proxy server requires password and enter credentials if needed.
- Click OK > Apply, then restart Safari.
Certificate prompts
- If your organization uses SSL inspection, you may need to trust a custom root certificate in Keychain Access to avoid HTTPS warnings.
See our full setup tutorials → https://www.proxiesthatwork.com/guides/setup
Testing your proxy
Confirm traffic is routed through the proxy.
Browser checks
Command-line checks
curl -x http://proxy.example.com:8080 https://ifconfig.me
curl --socks5 203.0.113.10:1080 https://ifconfig.me
- PAC test (fetch a URL that should be proxied)
curl --proxy "http://proxy.example.com:8080" https://example.com
Common problems and quick fixes
Connection fails immediately
- Check server address and port.
- Ensure your IP is allowed by the proxy provider (if whitelisting is required).
- Disable VPNs or other network filters temporarily.
- Windows: if using Manual proxy, turn off Automatically detect settings.
ERR_TUNNEL_CONNECTION_FAILED (Chrome/Edge)
- Wrong proxy host/port or blocked by firewall.
- Try removing quotes around the proxy flag if used.
- Test with curl to isolate browser vs. network issues.
The proxy server is refusing connections (Firefox)
- Verify HTTP vs. SOCKS type matches your proxy.
- Uncheck Use this proxy for all protocols if only HTTP is provided.
Endless auth prompts
- Re-enter credentials carefully; check for special characters.
- Clear stored credentials:
- Windows: Control Panel > Credential Manager > Windows Credentials.
- macOS: Keychain Access > search for proxy host > delete the saved item.
- Some proxies require username in a specific realm format (e.g., DOMAIN\user or user@realm).
HTTPS certificate warnings
- Corporate proxies that intercept TLS require a trusted root CA.
- Install the provided certificate:
- macOS: Keychain Access > System > Certificates > import and set Always Trust.
- Windows: mmc.exe > Certificates (Local Computer) > Trusted Root Certification Authorities.
Local resources unreachable (localhost)
- Add bypass entries:
- Windows: Do not use proxy for: localhost;127.0.0.1;.local;.internal
- Firefox: No proxy for: localhost, 127.0.0.1, *.local, *.internal
- macOS: Proxies panel > Bypass proxy settings for these Hosts & Domains
DNS still leaks with SOCKS
- Firefox: enable Proxy DNS when using SOCKS v5.
- Chrome/Edge: prefer a real HTTP(S) proxy or configure system to proxy DNS if required.
Performance issues
- Choose the nearest proxy location.
- Prefer HTTP/1.1 Keep-Alive or HTTP/2 capable proxies.
- Reduce extensions that intercept traffic.
Conflicts with security software
- Temporarily disable or allowlist your browser in antivirus/firewall.
- Corporate networks may block unknown proxies.
Useful diagnostics
- Chrome/Edge network log: visit chrome://net-export, click Start Logging, reproduce, then Stop.
- Firefox: about:networking (DNS/HTTP logs), about:config (search for proxy settings).
- Windows: netsh winhttp show proxy (system-level), check Advanced Proxy Settings.
- macOS logs: in Terminal, run
log stream --predicate 'subsystem == "com.apple.CFNetwork"'
Roll back or disable the proxy
- Windows: Settings > Network & Internet > Proxy > turn off Use a proxy server.
- macOS: System Settings > Network > Proxies > uncheck Web Proxy/Secure Web Proxy; Apply.
- Firefox: Settings > General > Network Settings > Settings > No proxy.
- Chrome/Edge flags: close all windows started with --proxy-server or relaunch normally.
Security and privacy tips
- Never share your proxy credentials publicly.
- Prefer HTTPS or SOCKS5 over plain HTTP when possible.
- Treat PAC files as code; only use trusted sources.
- Rotate credentials and IPs according to your provider’s best practices.
Explore our proxy troubleshooting guide → https://www.proxiesthatwork.com/guides/troubleshooting
