parallel-socks

SOCKS5 parallel racing aggregator

Installation

Using Nix

nix profile add github:bdim404/parallel-socks

From Source

cd src && go build -o parallel-socks

Usage

Config file mode

Create a config file (default: config.json):

{
  "log_level": "info",
  "listeners": [
    {
      "listen": "[::1]:1080",
      "socks": [
        {
          "name": "US-West-1",
          "address": "upstream1:1081"
        },
        {
          "name": "US-East-1",
          "address": "upstream2:1082"
        }
      ]
    }
  ]
}

Run with default config file:

parallel-socks

Run with custom config file:

parallel-socks --config /path/to/config.json
parallel-socks -c /path/to/config.json

Command line mode

parallel-socks --listen-address ::1 --listen-port 1080 --socks upstream1:1081 --socks upstream2:1082
parallel-socks -a ::1 -p 1080 -s upstream1:1081 -s upstream2:1082
parallel-socks -a ::1 -p 1080 -s upstream1:1081 -l debug

Command Line Options

Option	Short	Default	Description
--config	-c	config.json	Path to config file
--listen-address	-a	::1	Listen address for SOCKS5 server
--listen-port	-p		Listen port (required for command line mode)
--socks	-s		Upstream SOCKS5 proxy (can be specified multiple times)
--log-level	-l	info	Log level: debug or info
--help	-h		Show help message

Notes

• Config file mode: If --listen-port is not specified, the program will load configuration from the config file
• Command line mode: If --listen-port is specified, at least one --socks upstream must be provided
• The --socks option can be used multiple times to specify multiple upstream proxies

Testing

Test the SOCKS5 proxy with curl:

curl --socks5 [::1]:1080 http://ipinfo.io

Check your IP address:

curl --socks5 [::1]:1080 https://api.ipify.org

Test connection speed:

curl --socks5 [::1]:1080 -w "\nTime: %{time_total}s\n" -o /dev/null -s http://www.google.com

Example Output

Info level (default):

2026/01/04 00:58:10 listening on [::1]:1080 with 3 upstreams
2026/01/04 00:58:18 accepted connection from [::1]:xxxxx
2026/01/04 00:58:19 ✓ www.example.com:443 -> upstream3 (x.x.x.x:xxxx) (678ms)

Debug level (with -l debug):

2026/01/04 00:58:10 listening on [::1]:1080 with 3 upstreams
2026/01/04 00:58:18 accepted connection from [::1]:xxxxx
2026/01/04 00:58:18 socks5: sending connect request (20 bytes) to www.example.com:443
2026/01/04 00:58:18 socks5: sending connect request (20 bytes) to www.example.com:443
2026/01/04 00:58:18 socks5: sending connect request (20 bytes) to www.example.com:443
2026/01/04 00:58:19 socks5: received reply: ver=5, rep=0, rsv=0, atyp=1
2026/01/04 00:58:19 socks5: read bind addr: 0.0.0.0:0
2026/01/04 00:58:19 socks5: connect handshake completed successfully
2026/01/04 00:58:19 ✓ www.example.com:443 -> upstream3 (x.x.x.x:xxxx) (678ms)
2026/01/04 00:58:19 socks5: received reply: ver=5, rep=0, rsv=0, atyp=1
2026/01/04 00:58:19 socks5: read bind addr: 0.0.0.0:0
2026/01/04 00:58:19 socks5: connect handshake completed successfully
2026/01/04 00:58:19 socks5: received reply: ver=5, rep=0, rsv=0, atyp=1
2026/01/04 00:58:19 socks5: read bind addr: 0.0.0.0:0
2026/01/04 00:58:19 socks5: connect handshake completed successfully