How to use an authenticated proxy in Google Chrome

Your proxy details

After you buy a plan, open My proxies. Choose the Proxy Type (Rotating or Sticky), the Protocol (HTTP or SOCKS5) and a Format, then copy a line. The generator offers three formats:

In the examples on this page, replace USERNAME, PASSWORD, HOST and PORT with the values from your line. SOCKS5_PORT is the port the generator shows when you pick SOCKS5.

Residential lines are either rotating (a new IP on new connections) or sticky (one IP for the time you choose). Datacenter and ISP plans give you a list of dedicated IPs, one per line as IP:PORT:USERNAME:PASSWORD, and each line is one fixed IP.

To test a line, open https://ipinfo.io/json through it: it shows the exit IP and country. For HTTP lines you can also use the free proxy checker.

Quickest: a separate Chrome window with its own proxy

Start Chrome with --proxy-server and a separate profile folder. Your normal Chrome stays on your normal connection.

& "C:\Program Files\Google\Chrome\Application\chrome.exe" --user-data-dir="$env:TEMP\chrome-proxy" --proxy-server="http://HOST:PORT"

open -na "Google Chrome" --args --user-data-dir="$HOME/chrome-proxy" --proxy-server="http://HOST:PORT"

google-chrome --user-data-dir="$HOME/chrome-proxy" --proxy-server="http://HOST:PORT"

Open https://ipinfo.io/json. Chrome shows a sign-in dialog for the proxy: enter USERNAME and PASSWORD.

The separate --user-data-dir matters. If Chrome is already running with your normal profile, a new window joins it and ignores the flag.

Use your computer’s proxy settings

In Chrome, Settings → System → Open your computer’s proxy settings takes you to the Windows or macOS settings. Chrome then uses the system proxy, and so do other apps that follow it. See the Windows and macOS guides.

Use a proxy extension

A proxy extension lets you switch proxies from the toolbar without restarting Chrome. The original Proxy SwitchyOmega no longer runs in current Chrome; maintained forks such as Proxy SwitchyOmega 3 (ZeroOmega) do.

In the extension, create a proxy profile with protocol HTTP, server HOST and port PORT, add your username and password if it has fields for them (or enter them when Chrome asks), then switch to that profile.

SOCKS5 in Chrome

Chrome can’t log in to SOCKS5 proxies with a username and password. Use HTTP lines in Chrome. SOCKS5 works only without a password, from an IP on the Access & API allow-list on a plan that supports login by IP.

Choose the country

On residential plans, add -country- and a two-letter country code to the end of the username, for example USERNAME-country-us or USERNAME-country-gb. To combine a country with a state, a city or a sticky session, build the line in the generator, which shows only the options your plan supports. Datacenter and ISP IPs have a fixed location that you choose when you buy them. In the sign-in dialog, enter the username with the country tag.

Tips

• Use a sticky line for browsing. A rotating line can give different tabs, and even parts of one page, different IPs.
• WebRTC can reveal your real IP to sites even when pages load through a proxy. If that matters, start Chrome with --force-webrtc-ip-handling-policy=disable_non_proxied_udp, or use an anti-detect browser.
• Match Chrome’s language and your timezone to the proxy country if a site checks them.

Troubleshooting

• net::ERR_PROXY_CONNECTION_FAILED

  The browser couldn’t reach the proxy at all. Check the host and port, and that you used the HTTP port for an http:// proxy.More on this error →

• net::ERR_TUNNEL_CONNECTION_FAILED

  The proxy refused the CONNECT request. Run the line through curl -v to see the real status (407, 502 or 503).More on this error →

• Chrome keeps asking for the password

  The username or password is wrong. Copy them again from the generator.More on this error →

• The flag seems to be ignored

  Chrome was already running with that profile. Use a separate --user-data-dir or quit Chrome first.

Seeing another error? Read proxy errors and how to fix them, or contact support.

Questions