rTorrent SOCKS5 proxy: network.proxy.global.set and the password catch

rTorrent got real SOCKS5 proxy support in July 2026, and it is one line in .rtorrent.rc: network.proxy.global.set. Two things make this guide longer than one line. The source at the current release drops the SOCKS5 username and password on the floor, so the documented credentials format is not something to trust yet. And a seedbox that seeds 24/7 through a per-GB proxy is a very efficient way to empty a balance.

Checked against the rTorrent Proxy-Configuration wiki, the v0.16.16 release notes and the libtorrent v0.16.25 source in October 2026. We read the source; we did not run it.

What changed in v0.16.16

The release notes from 3 July 2026 announce “new proxy support, using network.proxy.global.set and network.proxy.http.set, with http://, socks5:// and socks5h:// support”, plus “a new ProxyManager and support for socks5 for peer connections”. The old network.http.proxy_address is deprecated. If your seedbox runs something older, those commands will not exist; check the version before you edit anything. The current release is v0.16.25, and ruTorrent, the web front-end most seedboxes put on top, is at v5.3.16.

What the proxy switches off

The wiki is blunt: with the global proxy set, “UDP (trackers/dht) and listening ports are disabled.” Not relayed, not leaked: off. That lines up with our side too, since our SOCKS5 should be treated as TCP only (UDP relay is unverified on our gateways), and an HTTP proxy never carries UDP. In practice:

• Only torrents with http:// or https:// trackers will find peers.
• No listening port means no incoming peers. The seedbox connects out, and only to peers that accept incoming connections.
• Anything else on the box that skips the proxy, a second client or a script, still shows the seedbox’s real IP.
• On residential, and past a shared IP’s allowance, the meter counts per GB, so a torrent you seed pays both ways. The meter section below prices a seedbox.
• A proxy relays; it does not encrypt. For copyright-type risk the qBittorrent’s wiki points people to a VPN; see proxy vs VPN.
• Lawful content only: Linux distributions, datasets, open releases. Sharing files you have no right to share through our proxies is not allowed, under the acceptable use policy.

The one-line setup

In ~/.rtorrent.rc, using the IP and port from your dashboard:

network.proxy.global.set = "socks5h://IP:PORT"

socks5h hands hostnames to the proxy to resolve, so tracker lookups do not come from the seedbox’s resolver. There is also network.proxy.http.set, which “Sets HTTP proxy (overrides global)” and “Supports all native libcurl schemas”, for when HTTP traffic should go somewhere different from the peers. Most setups need only the global line. Both commands are marked safe to call over XML-RPC in command_network.cc, so a running instance can be changed without a restart; we could not confirm a proxy option in ruTorrent’s own interface.

The password catch

The wiki documents credentials in the URL, with the example network.proxy.global.set = "socks5h://user:[email protected]:1080". At tag v0.16.25, though, the source in proxy_manager.cc parses the user and password from a socks5:// URL and then constructs the SOCKS5 connection without passing them; the constructor defaults both to empty. So until someone tests it and it works, assume authenticated SOCKS5 for rTorrent’s peer connections does not.

The fix that does not depend on rTorrent: add the seedbox’s own public IP to the order’s IP allowlist. The proxy then accepts connections from that address with no password, and the URL above, with no credentials in it, is all you need. Test it with one small legal torrent and watch the meter: if peers are going through, the usage view in your dashboard climbs with the transfer.

Read the meter: a seedbox never sleeps

A seedbox exists to upload. Take a 20 GB public research dataset and seed it to a ratio of 2.0 through a per-GB line: at least 60 GB through the proxy, both ways, before overhead. The smallest residential order that covers it is 60 GB for $180.00, and a box seeding a dozen datasets multiplies that. The metering explainer has the counting rules.

A dedicated datacenter IP is $1.90 for 30 days with no traffic meter. For anything that seeds around the clock, that is the only line that makes sense, and the bandwidth calculator shows the volume at which it overtakes residential. Check how many threads the order includes before raising rTorrent’s peer limits; more are a paid add-on. P2P is fine on our residential IPs and on dedicated IPs with no traffic meter, as long as what you share is lawful.

Then audit it. rTorrent tracks what each torrent uploaded and downloaded; total those for a day, export the same day from your dashboard as CSV, and diff. The bill audit guide has a script, and the honesty page says what we do if our number comes out higher than yours by more than overhead.

Throttle before you seed

Set rTorrent’s global upload throttle and a ratio rule in .rtorrent.rc before you add a single dataset. Changing them after the first top-up has gone is the expensive way to learn. Seeding legal data is a public service. Doing it on a meter is a budget line; treat it like one.

Verdict: does a seedbox even need a proxy?

Usually not. A seedbox already leaves from somebody else’s IP: the hosting company’s. Putting a proxy in front of it means paying twice for a different address and losing incoming peers in the process. Proxy it when the seedbox’s own IP is the problem, for example when the hosting company’s range is refused by a tracker or mirror you are entitled to use. Then: v0.16.16 or later, socks5h://, allowlisted rather than password-in-URL, a dedicated datacenter IP, and a throttle you set on day one. Want a headless client whose proxy credentials are documented and read by the code? The qBittorrent guide covers qbittorrent-nox.

Quick answers