Which proxy works best with Google Chrome?
Residential proxies with a sticky session are the usual choice for browsing, because the IP address looks like a home connection and stays the same while you work. For heavy use such as video, a time-based Unlimited Datacenter plan avoids paying by the gigabyte.
Proxy settings for Google Chrome: host, port and login
A BooProxies plan gives you four things: a host, a port, a username and a password. These are the values for Residential; the username and password are on your plan page.
| Host | resi.proxies.boo |
|---|---|
| HTTP port | 8080 |
| SOCKS5 port | 1080 |
| Username | USERNAME |
| Password | from your plan page |
The country and the session are chosen in the username, not in a separate setting. The generator on your plan page writes the username for you, and Targeting and sessions explains each part.
Google Chrome proxy setup, step by step
- For the whole computer, set the proxy in Windows or macOS. Chrome's own settings page only opens that system page.
- For Chrome only, install a proxy extension such as FoxyProxy and enter the four values there.
- For one window, start Chrome with
--proxy-serverand enter the login when Chrome asks.
Menu names can differ a little between versions of Google Chrome. The four values to enter are always the same.
Google Chrome proxy example
Start Chrome with a proxy
chrome --proxy-server="http://resi.proxies.boo:8080"Replace USERNAME and PASSWORD with the login from your plan page. The example asks an IP-check address, so the output is the address your request left from.
Rotating or sticky sessions for Google Chrome?
A device or browser that sends everything through the proxy is acting as one visitor, so a sticky session is usually what you want: the IP address stays the same while you work. Remember that gigabyte plans count all traffic, so video and large downloads use a plan up quickly.
A sticky username looks like this:
USERNAME-country-us-time-600-session-a1b2c3d4Google Chrome proxy not working?
- Chrome ignores a username and password written into
--proxy-server. It asks for them in a pop-up instead. - Chrome cannot log in to a SOCKS5 proxy. Use the HTTP port, 8080.
- A
407error means the username or password was not accepted. Copy both again from your plan page, and check that nothing added a space or cut the username short. - If the IP address is in the wrong country, look at the username: the country code is part of it. More fixes.
Questions about Google Chrome and proxies
Does Google Chrome work with SOCKS5 proxies?
Not with a username and password: Google Chrome can use SOCKS5 only without a login. Use the HTTP port, 8080, which works for both http and https sites.
Which BooProxies proxy should I use with Google Chrome?
Residential proxies with a sticky session are the usual choice for browsing, because the IP address looks like a home connection and stays the same while you work. For heavy use such as video, a time-based Unlimited Datacenter plan avoids paying by the gigabyte.
Terms explained: proxy port, proxy format, HTTP proxy, SOCKS5 proxy, proxy checker.
Google Chrome is a product of its own makers. BooProxies is not affiliated with it; the name is used here only to say what this guide is about. Use it within the rules of the sites you work with and our acceptable use policy.