Socks5?

[YouveGotMeowxy]

Support guidelines

• [X] I've read the support guidelines

I've found a bug and checked that ...

• [X] ... the documentation does not mention anything about my problem
• [X] ... there are no open or closed issues that are related to my problem

Description

I'd like to use my vpn in socks5 settings. In qbtorrent there's an area in settings to fill the info in but I dont see how in rutorrent?

Expected behaviour

.

Actual behaviour

.

Steps to reproduce

.

Docker info

.

Version

• Docker compose version (type docker-compose --version):
• System info (type uname -a):

Docker compose

.

Container logs

.

Additional info

No response

[YouveGotMeowxy]

Just to update in case anyone else stumbles along this post, and since no one seems to ever really reply here, I found out you can do it in a "hacky workaround" way, but it would be SO MUCH more user friendly if whoever has the ability to do so, just add it into the UI settings:

To add SOCKS5 Proxy add it to the .rtorrent.rc file (note, there is also a rtorrent.rc W/OUT a dot in front; that won't work):

i.e. config/rtorrent/.rtorrent.rc

network.http.proxy_address.set = "socks5h://<uname>:<pw>@<yoursock5provider>:1080"

[ToshY]

@YouveGotMeowxy I was looking for this, so thanks. I think however that the issue should be raised in Novik/ruTorrent instead, as this repo is just a docker image for it.

---

Edit

I've realised changing the setting this setting in .rtorrent.rc, changes it in UI if you look at Settings > Advanced > http_proxy. But trying to change the proxy_address setting, both in the UI as well as .rtorrent.rc (network.proxy_address.set) returns error Could not set proxy address: Try again.

I'm not sure what the difference is between network.proxy_address.set and network.http.proxy_address.set.

[YouveGotMeowxy]

@ToshY Sorry, I'm not sure why yours isn't working. Mine works; I've even tested that the IP changes with an IP checker.

[ToshY]

Hey @YouveGotMeowxy 👋

I think you've slighly misunderstood what I meant. The setting you've denoted network.http.proxy_address.set does "work" (also tested it with a magnet link with ipleak.net), but this is apparently only for tracker connections, whereas network.proxy_address.set is for peer connections.^1

Because I was unsure what that actually meant, I've tested this, and saw that when I have ruTorrent setup with network.http.proxy_address.set with sock5 proxy, and connect it to a torrent, while at the same time connecting another torrent client to the same torrent, it still showed the original hostname/ip for the ruTorrent client and not the proxy hostname.

So that's why I also wanted to set network.proxy_address.set, which doesn't work 🙁

[YouveGotMeowxy]

@ToshY oh wow! You're right, I did misunderstand. That's scary to know actually!

I've been running it for awhile now using only the "tracker proxy" thinking I'm covered. Thankfully no DM-CA notices since switching that "on", but now I'm a lil freaked out. Please keep me updated if you get the "peers proxy" part working!

[ToshY]

Hey @YouveGotMeowxy 👋

I will keep you updated. In the meantime I've created an issue at https://github.com/rakshasa/rtorrent/issues/1238. Don't really have much hope for it, as rtorrent doesn't seem to be maintained anymore (and the latest release 0.9.8 was almost 4 years ago) 🙁

So we shall see.

[ToshY]

Hey @YouveGotMeowxy 👋

Apparently there has never been any support for setting a socks5 proxy for peer connections: https://github.com/rakshasa/rtorrent/issues/1238#issuecomment-1653796535 Not sure if it will be implemented some day, as rtorrent itself doesn't seem to be actively maintained anymore.