How to Configure a SOCKS5 Proxy

Use SOCKS5 when you want app-level proxying that can handle web traffic, torrents, SSH tools, games, and other TCP traffic without forcing your whole device onto a VPN. SOCKS5 is the fifth version of the SOCKS protocol, defined by RFC 1928, and it supports authentication plus both TCP and UDP forwarding [source: RFC Editor]. That makes it flexible, but also a little annoying to set up because each operating system and app hides the proxy field in a different place.

TLDR: To configure a SOCKS5 proxy, get the proxy host, port, and optional username and password, then add them to your system, browser, or app proxy settings. For example, if your proxy is 185.22.10.44 on port 1080, you would enter those values under “SOCKS host” and “port” in Firefox. In a small remote team of 20 people, routing only browser traffic through SOCKS5 can cut VPN congestion noticeably, especially when video calls stay outside the proxy. Test it with an IP-check site afterward, because one wrong checkbox can send traffic the normal way.

What You Need Before You Start

A SOCKS5 proxy is not something you “turn on” out of thin air. You need connection details first. Your provider, server admin, or self-hosted proxy setup should give you:

• Server address: An IP address or hostname, such as proxy.example.com.
• Port: Often 1080, but it may be different.
• Username: Required if the proxy uses login authentication.
• Password: Also required for authenticated proxies.
• Protocol: Confirm that it is SOCKS5, not HTTP or HTTPS proxy.

Honestly, it feels like half of proxy problems come from mixing up proxy types. An HTTP proxy field will not behave like a SOCKS5 field. If your app asks for “HTTP proxy,” “HTTPS proxy,” and “SOCKS proxy,” choose the SOCKS option.

Configure SOCKS5 on Windows

Windows has built-in proxy settings, but the interface is more friendly to HTTP proxies than SOCKS5. Some apps respect the system proxy. Others ignore it completely. Expect to waste time on that if you are configuring older tools.

1. Open Settings.
2. Go to Network & Internet.
3. Select Proxy.
4. Under Manual proxy setup, enable Use a proxy server.
5. Enter the proxy address and port.
6. Save your changes.

For true SOCKS5 behavior on Windows, many users configure the proxy inside the app instead. Browsers, download tools, database clients, and SSH utilities often have better SOCKS5 support than the operating system panel.

Configure SOCKS5 on macOS

macOS makes SOCKS5 setup fairly clean. The setting lives in the network adapter options.

1. Open System Settings.
2. Go to Network.
3. Select your active connection, such as Wi Fi or Ethernet.
4. Click Details.
5. Choose Proxies.
6. Enable SOCKS Proxy.
7. Enter the server address and port.
8. If needed, enter your username and password.
9. Click OK, then Apply.

After that, apps that respect macOS proxy settings should route through SOCKS5. Some apps still use their own network stack. Yes, that is irritating. Test each critical app before assuming it works.

Configure SOCKS5 in Firefox

Firefox is one of the easiest ways to use SOCKS5 without changing your whole device. This is useful when you only want browser traffic to go through the proxy.

1. Open Firefox.
2. Go to Settings.
3. Scroll to Network Settings.
4. Click Settings.
5. Select Manual proxy configuration.
6. Enter the proxy host in SOCKS Host.
7. Enter the proxy port.
8. Select SOCKS v5.
9. Enable Proxy DNS when using SOCKS v5 if you want DNS requests to go through the proxy too.
10. Click OK.

The DNS checkbox matters. If it is off, your browser may use the proxy for page traffic while still asking your normal DNS resolver for domain lookups. That can leak which sites you visit.

Configure SOCKS5 in Chrome and Edge

Chrome and Edge usually use the operating system proxy settings. That means there is no neat built-in SOCKS5 panel like Firefox has. If you want per-browser SOCKS5 control, use a trusted proxy extension or start the browser with command-line options.

On Windows, a command may look like this:

chrome.exe --proxy-server="socks5://185.22.10.44:1080"

On macOS, it may look like this:

open -a "Google Chrome" --args --proxy-server="socks5://185.22.10.44:1080"

Replace the sample IP and port with your real proxy details. If your proxy needs a username and password, the browser may prompt you. Some setups do not handle SOCKS authentication well, which is when Firefox starts to look better.

Configure SOCKS5 on Linux

Linux gives you several routes. Desktop users can set a proxy in their network or system settings. Command-line users often set it per app.

For curl, use:

curl --socks5 185.22.10.44:1080 https://example.com

If DNS should also pass through the proxy, use:

curl --socks5-hostname 185.22.10.44:1080 https://example.com

For authenticated proxies:

curl --socks5 username:password@185.22.10.44:1080 https://example.com

Many apps also read environment variables, though SOCKS support is not consistent. Check the app documentation before relying on http_proxy or all_proxy.

Create a SOCKS5 Proxy with SSH

If you have SSH access to a server, you can create a temporary SOCKS5 proxy in seconds. This is one of the cleanest tricks in the toolbox.

ssh -D 1080 user@yourserver.com

This opens a local SOCKS5 proxy on port 1080. Then configure your browser or app to use:

• Host: 127.0.0.1
• Port: 1080
• Type: SOCKS5

The -D option enables local application-level forwarding in OpenSSH [source: OpenBSD Manual]. Keep the terminal window open. When you close the SSH session, the proxy stops.

Test That the Proxy Works

Do not skip testing. It takes under a minute and saves headaches later.

1. Open a site that shows your public IP address.
2. Check the displayed location and IP.
3. Turn the proxy off.
4. Refresh the page and compare the result.

If the IP does not change, the app is not using the proxy. If websites fail to load, the host, port, login, or firewall may be wrong. If only some sites fail, the proxy provider may block certain traffic types.

Security Tips That Actually Matter

• Do not treat SOCKS5 as encryption. SOCKS5 routes traffic, but it does not encrypt everything by itself.
• Use HTTPS websites. This protects page content from being read in transit.
• Prefer trusted providers. A shady free proxy can log traffic or inject junk.
• Proxy DNS when possible. This reduces DNS leaks.
• Use separate profiles. Keep proxy browsing apart from normal browsing.

A SOCKS5 proxy is best when you need precise control. Use it for one browser, one app, or one workflow. Use a VPN when you want most device traffic covered with less fiddling. The right choice depends on how much control you want, and how much setup pain you are willing to tolerate.