Last active
April 20, 2026 17:16
-
-
Save jasdeepkhalsa/497226a5c72f572d8206 to your computer and use it in GitHub Desktop.
Configuring a SOCKS proxy server in Chrome
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| From: http://www.chromium.org/developers/design-documents/network-stack/socks-proxy | |
| To configure chrome to proxy traffic through the SOCKS v5 proxy server myproxy:8080, launch chrome with these two command-line flags: | |
| --proxy-server="socks5://myproxy:8080" | |
| --host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE myproxy" | |
| The first thing to check when debugging is look at the Proxy tab on about:net-internals, and verify what the effective proxy settings are: | |
| chrome://net-internals/#proxy | |
| Next, take a look at the DNS tab of about:net-internals to make sure Chrome isn't issuing local DNS resolves: | |
| chrome://net-internals/#dns | |
| Next, to trace the proxy logic for individual requests in Chrome take a look at the Events tab of about:net-internals: | |
| chrome://net-internals/#events | |
| Example Usage: | |
| $ ssh -C2qTnN -D 8080 user@domain.com | |
| $ google-chrome --proxy-server="socks5://127.0.0.1:8080" --host-resolver-rules="MAP * ~NOTFOUND , EXCLUDE 127.0.0.1" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you happen to be using these kinds of things to bypass blocks for the first time, see those settings and get scared, I want to say that modern proxy services are much nicer and more comfortable to use. I'm using SimplyNode right now, and the setup process exists, but it's simple because first, there's a guide, and second, you take the ready-made data from your personal account and paste it where you need it. Everything else is generated automatically.