rtorrent running but can't connect to ruTorrent

[Chester007]

This is on a fresh installation. I can verify that rtorrent is running by checking htop but the ruTorrent webUI says that connection is not established. I checked the scgi port settings on both and they match. However, entering the command

rtorrent

or

/usr/bin/rtorrent

on the terminal seems to temporarily fix the connection issue but then now I have 2 rtorrent processes running and closing the terminal also terminates the process.

[MichaIng]

@Chester007
Many thanks for your report.

Jep I verified the bug: https://github.com/MichaIng/DietPi/issues/2629

I hope we can fix this for v6.22 which is about to be released soon.

[Chester007]

Thank you for noticing this issue. I was just about to report that I was able to replicate this on a newly installed system and on a different microsd card. I'm also hoping that this issue gets resolved soon. I personally prefer rtorrent over other torrent clients.

[arturo]

Hi,
I also would like rutorrent webif to be working again

[MichaIng]

The fix is already in Beta. If you want to test it: https://github.com/MichaIng/DietPi/issues/2632

[arturo]

Now rutorrent connects, but download speed is 0 (through Nordvpn vpn)
I understand I need to setup a socks5 proxy with authentication, can that be done with rtorrent ?

[MichaIng]

rTorrent has no internal SOCKS5 support: https://github.com/rakshasa/rtorrent/issues/105

So you would need to setup setup the proxy externally and make rTorrent use it. However a proxy should not be required, it is just recommended to stabilize and further anonymize the connection.

Did you verify that you use a P2P ready NordVPN server?

It works without VPN active, doesn't it?

[Chester007]

After some playing around with the new update, I've found that changing the hostname to something other than DietPi also causes the problem where rutorrent can't connect to rtorrent

[MichaIng]

Hmm will check. Actually ruTorrenr should simply scan/show the local loopback IP for rTorrent instances so the hostname should not matter. Perhaps rTorrent only listens/answers requests sent to or associated with the hostname at the time it is started. But I would call this a bug actually. Does restarting rTorrent solve it?

[Chester007]

I tried restarting it using

Code: Select all

dietpi-services restart rtorrent

but didn't work