Chrome proxy setup

Chrome has no proxy fields of its own: it uses the computer's settings, a launch flag or an extension. Each works with our HTTP port and your login.

Protocols: HTTP with a login. SOCKS5 only without a login, so not with our gateway
UDP: No. WebRTC can send UDP around the proxy
Where the setting is: Settings → System → Open your computer's proxy settings, the --proxy-server flag, or an extension
Works with: Residential and mobile proxies

Before you start

Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product.
Pick a route: the computer's settings (every app), the launch flag (one separate Chrome instance) or an extension per Chrome profile that also fills in the login (ZeroOmega, FoxyProxy).

Connection details

Host: gate.aeonproxy.com
Port (HTTP / HTTPS): 7000
Login: your proxy login, with targeting keys if you need them: LOGIN-cc-us-sid-abc123
Password: your proxy password

Copy the login and password from the Residential or Mobile page of the dashboard; the generator there also writes ready lines. Key syntax: targeting and sessions.

Add the proxy in the computer's settings

Open Chrome's menu → Settings → System and click Open your computer's proxy settings.
Windows: under Manual proxy setup, click Set up next to Use a proxy server. Turn it on, enter gate.aeonproxy.com in Proxy IP address and 7000 in Port, and click Save.
macOS: in your connection's Details → Proxies, turn on Web proxy (HTTP) and Secure web proxy (HTTPS), enter gate.aeonproxy.com and 7000 in both, and click OK.
Open any site. A Sign in window says the proxy requires a username and password: enter your login (with keys, see below) and password and click Sign in.

Chrome ignores passwords saved in system proxy settings, so this window is how it gets your login. If it warns that the connection is not private, that refers to the login going to the proxy over plain HTTP; HTTPS sites stay encrypted.

Or start Chrome with a launch flag

The flag sets the proxy for one instance. Give it its own --user-data-dir: a Chrome already running with the same folder ignores the flag.

# Windows (Command Prompt)
"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="http://gate.aeonproxy.com:7000" --user-data-dir="%LOCALAPPDATA%\ChromeProxy"

# macOS (Terminal)
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --proxy-server="http://gate.aeonproxy.com:7000" --user-data-dir="$HOME/chrome-proxy"

# Linux
google-chrome --proxy-server="http://gate.aeonproxy.com:7000" --user-data-dir="$HOME/.chrome-proxy"

# Chrome then asks for LOGIN and PASSWORD in its Sign in window

Keep the login out of the flag: http://LOGIN:PASSWORD@… fails with ERR_NO_SUPPORTED_PROXIES. Command Line on chrome://version shows the flags in use. Automating Chrome? See Playwright or Selenium.

Check the proxy

Open the IP checker in the same window: it should show the country you asked for. Then compare WebRTC public IP with IP sites see. Chrome has no WebRTC setting, and by default WebRTC sends UDP outside the proxy, which can reveal your real address. FoxyProxy's Limit WebRTC → Disable Non-Proxied stops that, and so does the WebRtcIPHandling policy set to disable_non_proxied_udp on a managed computer. See WebRTC leaks.

Rotating or sticky

Use a sticky login. Chrome opens many connections per page; with a rotating login each gets a new IP, which can sign you out of sites. With -sid- they share one IP for the -ttl- minutes (60 at most), then the line gets a new IP from the same place.

LOGIN-cc-us-st-california-sid-chrome01-ttl-60

Chrome keeps the typed login until it quits. For a new line, quit Chrome completely and enter it when asked.

If it does not work

What you see	What to check
Your own IP, no Sign in window	The system proxy is off, or an extension or policy controls it: Settings → System then says so.
The Sign in window keeps coming back	The gateway rejected the login (407): a wrong password, or a key not in the lists, such as a misspelled city.
`ERR_SOCKS_CONNECTION_FAILED`	Chrome is set to SOCKS5 on port 7001 and cannot log in there. Switch to HTTP on port 7000.
`ERR_PROXY_CONNECTION_FAILED`	Chrome cannot reach the proxy: a mistyped host or port, or a flag that starts with `https://`.
`ERR_TUNNEL_CONNECTION_FAILED`	The gateway accepted the login but refused the site: no traffic left (402), a site blocked by default (403) or a failed exit (502, reload). See gateway errors.
Other apps lost the internet	They share the system proxy but cannot ask for a login. Turn it off when you finish, or use the flag or an extension.

Questions

No. Chrome has no SOCKS5 authentication, and extensions cannot add it. Use port 7000: it carries HTTPS sites through a CONNECT tunnel.

Not through the computer's settings, which every profile shares. Install ZeroOmega or FoxyProxy in each profile and give each one its own -sid- key.

Yes with the system settings or the flag. An extension needs Allow in Incognito turned on in its details on chrome://extensions.

Proxy questions? Ask support in the live chat.

Contact support See pricing