SOCKS5 Proxy Setup Guide for Telegram, Discord, and P2P Applications
A step-by-step guide to configuring SOCKS5 proxies for Telegram, Discord, torrent clients, and other popular applications across Windows, macOS, and Linux.
Why SOCKS5?
SOCKS5 is the most versatile proxy protocol. Unlike HTTP proxies that only handle web traffic, SOCKS5 works with any TCP or UDP application — messaging apps, torrent clients, games, and custom tools.
Before You Start
You'll need:
- A SOCKS5 proxy address and port (find one in our Proxy List)
- Proxy credentials (username/password), if authentication is required
- 5 minutes per application
Telegram
Desktop (Windows, macOS, Linux)
- Open Telegram → Settings → Advanced → Connection Type
- Select Use custom proxy
- Choose SOCKS5
- Enter the proxy host and port
- If required: enable Username/password and enter credentials
- Click Save and test the connection
Host: proxy.example.com
Port: 1080
Username: (optional)
Password: (optional)
The connection status indicator should turn green, and you'll see a proxy badge next to your connection status.
Mobile (Android, iOS)
- Open Telegram → Settings → Data and Storage → Proxy
- Tap Add Proxy → SOCKS5
- Enter host, port, and credentials
- Tap Done and enable the proxy
Discord
Discord doesn't have built-in proxy settings. You need to configure your system proxy or use a proxy-aware launcher.
Using Discord with a System Proxy (macOS/Linux)
macOS:
networksetup -setsocksfirewallproxy wi-fi proxy.example.com 1080
networksetup -setsocksfirewallproxystate wi-fi on
# Launch Discord
# After Discord is running, disable:
networksetup -setsocksfirewallproxystate wi-fi off
Linux:
# Launch Discord with SOCKS5 proxy
SOCKS5_PROXY="socks5://proxy.example.com:1080"
discord --proxy-server="$SOCKS5_PROXY" &
# Or use tsocks
sudo apt install tsocks
echo "server = 127.0.0.1" >> /etc/tsocks.conf
echo "server_port = 1080" >> /etc/tsocks.conf
tsocks discord
Using Discord with a Wrapper (Windows)
Use SocksCap64 or Proxifier to route Discord through a SOCKS5 proxy:
- Install SocksCap64
- Add Discord.exe to the application list
- Configure SOCKS5 proxy settings
- Launch Discord through SocksCap64
Torrent Clients
qBittorrent
- Open qBittorrent → Settings → Advanced → Network Interface
- Under Proxy, select SOCKS5
- Configure:
Type: SOCKS5 Host: proxy.example.com Port: 1080 Username: (optional) Password: (optional) - Check Use proxy for peer connections and Use proxy for tracker connections
- Click Apply
Transmission (Linux/macOS)
# Edit Transmission config
nano ~/.config/transmission/settings.json
# Set these values:
"proxy": "proxy.example.com",
"proxy-auth-enabled": true,
"proxy-auth-password": "your_password",
"proxy-auth-username": "your_username",
"proxy-port": 1080,
"proxy-type": 0, # 0 = SOCKS5
"proxy-enabled": true,
Linux Command Line
curl
curl --socks5 proxy.example.com:1080 https://example.com
curl --socks5-hostname proxy.example.com:1080 https://example.com # DNS over proxy
wget
# In ~/.wgetrc or via ENV
export http_proxy="socks5://proxy.example.com:1080"
export https_proxy="socks5://proxy.example.com:1080"
wget https://example.com
SSH over SOCKS5
# Route SSH through SOCKS5
ssh -o ProxyCommand='nc -x proxy.example.com:1080 %h %p' user@target-server
Browser Configuration
Firefox (Native SOCKS5)
Firefox has the best SOCKS5 support among browsers:
- Settings → Network Settings → Manual proxy configuration
- SOCKS Host: proxy.example.com Port: 1080
- Select SOCKS v5
- Check Proxy DNS when using SOCKS v5 (critical for leaks)
- Save
Chrome/Chromium
Chrome uses system proxy settings or command-line flags:
google-chrome --proxy-server="socks5://proxy.example.com:1080"
Testing Your SOCKS5 Connection
# Test SOCKS5 connectivity
curl --socks5 proxy.example.com:1080 https://api.ipify.org?format=json
# Expected output: {"ip":"proxy_ip_here"}
# Test DNS over SOCKS5
curl --socks5-hostname proxy.example.com:1080 https://api.ipify.org?format=json
# Test UDP (if supported)
# Use netcat or specialized tools
Troubleshooting
| Problem | Solution |
|---|---|
| Connection refused | Proxy might be offline — try another |
| Authentication failed | Check username/password, ensure SOCKS5 auth |
| DNS leaks | Use --socks5-hostname or check "Proxy DNS" |
| Slow connection | Try a proxy closer to your location |
| App doesn't support SOCKS | Use SocksCap64/Proxifier (Windows) or tsocks |
Find SOCKS5 Proxies
Browse our Proxy List and filter by SOCKS5 protocol. Every listed proxy is verified for SOCKS5 compatibility.