Set up GeekProxy in Google Chrome
Chrome doesn't have its own proxy settings. It uses whatever the operating system has configured. This guide walks through both Windows and macOS setup, plus how to verify things work.
You'll need: an active GeekProxy package and your proxy credentials from the dashboard. Setup takes about 2 minutes.
Get proxies1 Before you start
A few things to know up front:
- Chrome uses your computer's system proxy settings. Changing them affects all traffic, not just Chrome
- If you only want to route Chrome through the proxy, use a separate browser profile or a different user account on your machine
- HTTP and SOCKS5 proxies are supported natively through system settings. For SOCKS5 with username/password auth in Chrome specifically, there's a workaround we cover below
What you'll need
- Active GeekProxy package (residential or datacenter)
- Proxy credentials from your dashboard: Host, Port, Username, Password
- Admin rights on your computer (system settings usually require them)
- Field Example
- Protocol HTTP / SOCKS5
- Host 185.123.45.67
- Port 12345
- Username user-12345
- Password mypassword
2 Setup on Windows 10/11
Windows has one place for proxy settings that Chrome reads automatically.
Step-by-step
- Open Chrome, click the three dots in the top-right, pick Settings
- In the left menu go to System
- Click Open your computer's proxy settings. This opens the Windows settings app
- Under Manual proxy setup, flip on the toggle Use a proxy server
- Enter the Host (IP) and Port from your GeekProxy dashboard
- Click Save
Manual proxy setup with IP and Port fields filled in
Windows proxy settings don't have fields for username and password. For HTTP proxy, Chrome shows a pop-up to enter them the first time you open a site. For SOCKS5, Chrome doesn't support auth at all (see SOCKS5 in Chrome). Either way, IP whitelist is the most reliable auth method — details in Authentication.
3 Setup on macOS
macOS stores proxy settings per network connection. You configure them in System Settings, and Chrome picks them up automatically.
Step-by-step
- Open System Settings (or System Preferences on older macOS)
- Go to Network, pick your active connection (Wi-Fi or Ethernet), click Details
- Open the Proxies tab
- Check Web Proxy (HTTP) and Secure Web Proxy (HTTPS), or SOCKS Proxy depending on what you use
- Enter the Host and Port from your dashboard
- Check Proxy server requires password and enter your username/password
- Click OK, then Apply
Proxies tab with Web Proxy enabled and credentials filled in
Unlike Windows, macOS can store the proxy password in Keychain. You won't get a pop-up on every session.
4 Authentication
GeekProxy supports two ways to authorize your connection:
Login and password
The default. You enter credentials in the system proxy settings (on macOS) or in the Chrome pop-up that appears when you open the first site (on Windows). Chrome remembers them for the session.
Chrome's pop-up sometimes shows up repeatedly on Windows. If that happens, it's easier to switch to the IP whitelist method (below).
IP whitelist
Instead of username/password, you tell GeekProxy which of your home/office IP addresses can connect. No pop-up, no password needed.
- Go to your dashboard
- Open the package settings
- Switch authorization to Restricted by IP
- Add your current IP address (the dashboard can detect it automatically)
- Save
IP whitelist works well for fixed offices or home setups with a static IP. If your internet provider changes your IP often, stick with login/password.
5 Verify it's working
Quick sanity check:
- In Chrome, open any site that shows your IP address
- Compare the IP with the Host value from your GeekProxy dashboard
- They should match. If they do, the proxy is active
You can also check the country the site detects. If you bought a US proxy, it should show a US city. If it shows your actual location, Chrome is still going through your regular connection.
Some sites block proxy traffic aggressively and will show an error instead of your IP. Try a few different sites before assuming the proxy is broken.
6 SOCKS5 in Chrome
Chrome handles SOCKS5 through system settings, but there's a significant limitation: Chromium doesn't support SOCKS5 authentication at all, on any platform. This is a known long-standing issue in Chrome (Chromium issue 40323993).
If you need SOCKS5, the solution is to remove the need for authentication entirely — use IP whitelisting instead.
Recommended: switch to IP whitelist
- Go to your dashboard
- Open package settings
- Switch authorization to Restricted by IP
- Add your current IP (dashboard can fill it in)
- Save
After this, set up SOCKS5 in system settings as usual (see Windows or macOS section). No username, no password, Chrome will just work.
Alternative: Chrome command-line flag
You can also launch Chrome with a flag that routes traffic through SOCKS5. Useful if you don't want to change system settings. On Windows, create a shortcut with this target:
chrome.exe --proxy-server="socks5://HOST:PORT"
On macOS, run from Terminal:
open -a "Google Chrome" --args --proxy-server="socks5://HOST:PORT"
Replace HOST and PORT with your values. Authorization still has to go through the IP whitelist — the flag doesn't accept credentials.
When using command-line flags, all Chrome traffic in that session goes through the proxy. Close other Chrome windows first, or use a separate profile with --user-data-dir=/path/to/folder.
If IP whitelisting doesn't work for you (dynamic IP, multiple devices), use HTTP proxy instead of SOCKS5. Chrome does support HTTP proxy auth via the browser's password prompt.
7 Common issues
Sites load without the proxy
Chrome probably hasn't picked up the new settings. Fully quit Chrome (make sure no Chrome processes are running in the background) and reopen. On macOS, click Apply in the Network settings after changes.
Authentication pop-up keeps appearing
Happens with HTTP proxies when Chrome's credential cache gets cleared. Chrome should remember credentials within a session but may ask again after a restart. If it's persistent, switch to IP whitelist authorization.
ERR_PROXY_CONNECTION_FAILED
Three things to check:
- Is the proxy package active and not expired? Check the dashboard
- Are Host and Port entered correctly? Typos are common
- Is your firewall blocking the proxy port?
Some sites block you / CAPTCHAs everywhere
Datacenter IPs get flagged more often than residential on services like Google, Facebook, and streaming platforms. If you're seeing lots of CAPTCHAs, try a residential package instead.
Proxy works in Chrome but not in another app
Expected behavior if you only changed the system settings for a specific connection profile on macOS. Other apps might use a different profile. On Windows, system settings apply globally.