Google Chrome

Chrome has no proxy settings of its own on Windows and macOS: it follows the computer's proxy settings. You can change those, start a separate Chrome profile with its own proxy, or let an extension handle it. This page covers all three.

The examples use the Residential gateway, geo.gw.nyxon.sh with port 8080. Other products have their own host and port, listed in Endpoints and ports.

Use the computer's proxy settings#

1. Open Chrome Settings and select System.
2. Click Open your computer's proxy settings.
3. Set geo.gw.nyxon.sh with port 8080 as the HTTP proxy. The steps are in the Windows and macOS guides.
4. Open any website. Chrome shows a Sign in dialog for the proxy.
5. Enter your proxy username and password, then click Sign in.

These settings apply to the whole computer, so other apps that follow them use the proxy too. If Chrome says it is using proxy settings from an extension or from your administrator, that extension or policy decides the proxy, and changes to the system settings do not reach Chrome.

Start a separate profile with its own proxy#

The --proxy-server switch sets the proxy for one Chrome instance. With a profile folder of its own, it gives you a proxied Chrome next to your normal one:

& "C:\Program Files\Google\Chrome\Application\chrome.exe" --user-data-dir="$env:TEMP\chrome-proxy" --proxy-server="http://geo.gw.nyxon.sh:8080"

open -na "Google Chrome" --args --user-data-dir="$HOME/chrome-proxy" --proxy-server="http://geo.gw.nyxon.sh:8080"

google-chrome --user-data-dir="$HOME/chrome-proxy" --proxy-server="http://geo.gw.nyxon.sh:8080"

Chrome asks for the username and password when the first page loads.

• Keep the credentials out of the switch. With USERNAME:PASSWORD@ in --proxy-server, Chrome refuses the proxy and every page fails with ERR_NO_SUPPORTED_PROXIES.
• Use a separate profile folder. If Chrome is already running with the same profile, the command only opens a window in that instance, and the switch has no effect.

Use an extension#

FoxyProxy and ZeroOmega set the proxy for Chrome only, store your credentials and switch between proxies or a direct connection from the toolbar.

Countries and sessions#

Targeting and sessions go in the username you sign in with. To browse from Germany and keep one IP for 30 minutes:

USERNAME-country-de-session-a1b2c3d4-time-30

A page opens several connections, and on a rotating username they can leave from different IPs, which signs you out of some sites. Use a session ID for anything with a login. See Rotating and sticky sessions.

SOCKS5#

Chrome cannot send a username and password to a SOCKS5 proxy, so use the HTTP port. It still carries HTTPS sites end to end: Chrome opens an encrypted tunnel through the gateway and runs TLS inside it. See Clients without SOCKS5 passwords.

Check the IP#

Open https://ipinfo.io/json. It should show a NyxonProxies IP in the location you targeted, not your own. WebRTC can still reveal your real IP, see Check your proxy IP.

Errors#

More in Error codes.