[Support] binhex - rTorrentVPN


Recommended Posts

Hello, i'm trying to setup binhex-rtorrentvpn to make use of binhex-privoxyvpn. I want to do this so that i don't use too many connections on my vpn provider. Privoxy is up and running, connected through wireguard on default port 8118.

 

edit: i figured it out. an extra install of privoxy is not necessary when using rutorrent. it has a privoxy instance built in which can be used by other applications. pretty cool.

 

 

Edited by likesboc
Link to comment

i cannot figure out however how to change the listening port. editing \rtorrent\config\rtorrent.rc to use

# Port range to use for listening.
#
network.port_range.set = 5 digit portnumber

for example leads to rutorrent not starting anymore.

the log somehow circles around

2021-02-06 21:33:31,344 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2021-02-06 21:33:32,351 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2021-02-06 21:33:32,355 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2021-02-06 21:34:02,403 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.67.41.254 different, marking for reconfigure

2021-02-06 21:34:02,408 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2021-02-06 21:34:02,413 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2021-02-06 21:34:02,415 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2021-02-06 21:34:02,416 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2021-02-06 21:34:02,445 DEBG 'watchdog-script' stdout output:
Script done.

2021-02-06 21:34:13,524 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries

2021-02-06 21:34:13,525 DEBG 'watchdog-script' stdout output:
[warn] Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...

 

i thought maybe adding my forwarded vpn port to "Container Variable: ADDITIONAL_PORTS" would help but that doesnt change anything either.

 

any help would be appreciated :)

 

Edited by likesboc
Link to comment
10 minutes ago, likesboc said:

network.port_range.set = 5 digit portnumber

did you not see the existing entry in there?, it should of given you a clue as to the format, assuming incoming port (port forward) is 1234, the entry in rtorrent.rc would be:-

network.port_range.set = 1234-1234

 

Link to comment
9 minutes ago, binhex said:

did you not see the existing entry in there?

 

i did. i tried a port and also a range, but both variants failed. must have been something else though because following your advice now it works. thank you.

Edited by likesboc
typo
Link to comment
On 11/20/2020 at 3:44 AM, xtorrent said:

First off, thanks binhex for an incredible tool.  I'm a newbie to this image, and in the process of moving a lot of my stuff over.  If I find some stumbling blocks along the way hopefully my questions will help others.

 

First up, in "https://github.com/binhex/arch-rtorrentvpn/blob/master/README.md", section about "AirVPN provider" in the bit: about modifying rtorrent.rc to change the ports:






network.port_range.set = 20479-20479
port_random = no

 in the latest config file included with the image I noticed the following already exists:






# Start opening ports at a random position within the port range.
#
network.port_random.set = no

 

Are the "network.port_random.set" and "port_random" the same thing?  If so maybe the bit about port_random can be removed from the readme to make things even simpler using the latest image.

 

Second, I'm trying Pyroscope for the first time.  I searched for some guidance in this thread but most people commenting on Pyroscope seem to be old hands.  After a bit of digging around in the image I figured out pyroscope is already installed, but if you want the extra fields (loaded,completed,leechtime,seedtime) to work you need to add the config below to rtorrent.rc, as documented  at:

 

https://pyrocore.readthedocs.io/en/latest/setup.html

 






#
# PyroScope SETTINGS
#

# `system.has` polyfill (the "false=" silences the `catch` command, in rTorrent-PS)
catch = {"false=", "method.redirect=system.has,false"}

# Set "pyro.extended" to 1 to activate rTorrent-PS features!
# (the automatic way used here only works with rTorrent-PS builds after 2018-05-30)
method.insert = pyro.extended, const|value, (system.has, rtorrent-ps)

# Set "pyro.bin_dir" to the "bin" directory where you installed the pyrocore tools!
# Make sure you end it with a "/"; if this is left empty, then the shell's path is searched.
method.insert = pyro.bin_dir, string|const,

# Remove the ".default" if you want to change something (else your changes
# get over-written on update, when you put them into ``*.default`` files).
import = ~/.pyroscope/rtorrent-pyro.rc.default

# TORQUE: Daemon watchdog schedule
# Must be activated by touching the "~/.pyroscope/run/pyrotorque" file!
# Set the second argument to "-v" or "-q" to change log verbosity.
schedule = pyro_watchdog,30,300,"pyro.watchdog=~/.pyroscope,"

Hopefully the next time someone searches for Pyroscope in this thread this will save them some time.

 

Thanks again binhex.

 

 

 

Just installed this Docker and loving it. Having issues getting pyrocore tools to work. When I add these commands into rtorrent.rc, rtorrent never loads and the watchdog-script keeps repeating "Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...". If I open a shell into the container and attach to the tmux session, I see the console message that Pyroscope loaded but rtorrent restarts shortly thereafter.

 

Anyone else have this issue or can point me in the right direction?

 

Edit: I figured out what was happening and worked around it for now. rTorrent-PS takes quite a lot longer to start with the PS extensions loaded - at least in my environment with a large number of torrents in the session. While it would eventually come up (4+ minutes), the rtorrent.sh script kept trying to restart rTorrent and would delete the rtorrent.lock file in the session directory - which would in turn prevent things like rtcontrol from running. I modified /home/nobody/rtorrent.sh to increase retry_wait=1 to retry_wait=30. This allows everything to come up. I'm running everything from NVMe SSDs on a 10th Gen i7 with plenty of RAM and no obvious chokepoints.

 

Not sure of a permanent fix for this? I do have a ton of hash checks running (importing from Transmission) - so maybe I'll wait that out and see if it's the issue - I'll update here on what happens.

 

Update- after all hash checks finished, the issue continues. For now I am just updating the retry_wait value via script on container startup. Seems I'm the only one with the issue so probably not valuable to try and accommodate. I'll leave this all here in case anyone else has the issue in the future.

Edited by rinseaid
The secret ingredient is patience
Link to comment

I've been trying to figure out the port forwarding situation for a while but not having any luck.  I use TorGuard which has facilities for port forwarding (you go on their customer portal and request a port to be forwarded for a given VPN server, then configure your ovpn file to hit that server so that with your credentials, they know to set up the forwarding on connect).  I've worked with their support team to validate that traffic is flowing through the forwarded port, but still, open port checker websites report the port is closed (although weirdly, if I hit a random port, I get an answer right away, but with my targeted port it takes a longer time to determine --as if it is timing out).  In any case, @binhex I'm not sure what's the best way to debug.  Privoxy works, torrent files work, but magnet links relying on DHT do not.  rtorrent also gives me MUCH higher speeds for the torrents that DO work vs deluge (saturating my internet bandwidth), so I really want to get this to work.  I'm running this on a QNAP NAS.  Is it possible that the iptables settings or the ip route are doing funny things?

Link to comment

IMPORTANT - Move from rtorrent-ps to rTorrent

 

Due to the following reasons the next docker image release will be rTorrent NOT rtorrent-ps:-

  • Stagnant development - Development has pretty much stopped for rtorrent-ps (stuck on 0.9.6), whilst it still progresses on with rTorrent (0.9.8), this leads to a multitude of bugfixes identified in rTorrent not being applied to rtorrent-ps.
  • Issues building pyrocore - There are issues when compiling pyrocore during docker build which leads to more development work by me, i would rather ditch this in favour of a simpler build with only rTorrent to compile and support.

I realise this may upset certain users who rely on pyrocore and/or rtorrent-ps, but if you want to use pyrocore and rtorrent-ps then you will have to use an existing tagged release, latest will be moving on (i'm afraid i simply don't have enough time to support both).

 

This has now been reversed back to rtorrent-ps due to issues around public trackers that have been introduced into rtorrent 0.9.8, i will keep an ee on the issue but for now we are back to rtorrent-ps with pyrocore.

Link to comment

Just updated this container about 20 mins ago and now i cant get the client to load.  Just loops in the log.

 

Lots of messages like:

2021-02-11 11:24:53,221 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries
[warn] Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...

2021-02-11 11:24:53,221 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries
[warn] Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...

2021-02-11 11:25:23,499 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP [REDACTED] different, marking for reconfigure

2021-02-11 11:25:23,503 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2021-02-11 11:25:23,507 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2021-02-11 11:25:23,510 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2021-02-11 11:25:23,511 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2021-02-11 11:25:23,534 DEBG 'watchdog-script' stdout output:
Script done.

2021-02-11 11:25:34,592 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries
[warn] Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...

 

The client UI will load but it's all empty.  Just looks like a fresh install of Rtorrentvpn with no torrents in it.

 

Before I start getting H&R warnings all over the place is there a means to revert just this container to whatever I previously had working?

Edited by DontWorryScro
Link to comment

Hello, Nothing is working after updating. Please let me know what to do?
 

2021-02-12 01:27:54,365 DEBG 'rutorrent-script' stderr output:
[NOTICE] [pool www] 'group' directive is ignored when FPM is not running as root

2021-02-12 01:27:54,369 DEBG 'rutorrent-script' stdout output:
[info] starting nginx...

2021-02-12 01:28:01,133 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2021-02-12 01:28:01,151 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening on port 5000
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2021-02-12 01:28:01,164 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

2021-02-12 01:28:01,177 DEBG 'watchdog-script' stdout output:
[info] nginx running
[info] Initialising ruTorrent plugins...

2021-02-12 01:28:17,985 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

 

Meanwhile, I have moved back to the previous working version with tag: 

 

binhex/arch-rtorrentvpn:rtorrent-ps-1.1.r54.ga787dd9-1-28

 

  Hey, You can change the latest tag to above mentioned tag like this:

 

Screenshot: https://i.imgur.com/WoTUrGy.png

37 minutes ago, DontWorryScro said:

Just updated this container about 20 mins ago and now i cant get the client to load.  Just loops in the log.

 

The client UI will load but it's all empty.  Just looks like a fresh install of Rtorrentvpn with no torrents in it.

 

Before I start getting H&R warnings all over the place is there a means to revert just this container to whatever I previously had working?

 

Edited by learningunraid
Link to comment
On 2/11/2021 at 8:00 PM, learningunraid said:

Hello, Nothing is working after updating. Please let me know what to do?

This will be a configuration option in your /config/rtorrent/config/rtorrent.rc file that is no longer compatible with the newer version of rtorrent (now v0.9.8).

 

The permanent fix for this is to simply rename or delete the existing config file /config/rtorrent/config/rtorrent.rc and then restart the container, then re-edit the config file if required to re-apply any settings you want, sadly this is not something i can automate for you.

 

This should no longer be necessary, as we have rolled back to rtorrent-ps (v0.9.6) thus all existing configs should work fine.

  • Like 1
Link to comment
1 minute ago, binhex said:

This will be a configuration option in your /config/rtorrent/config/rtorrent.rc file that is no longer compatible with the newer version of rtorrent (now v0.9.8).

 

The permanent fix for this is to simply rename or delete the existing config file /config/rtorrent/config/rtorrent.rc and then restart the container, then re-edit the config file if required to re-apply any settings you want, sadly this is not something i can automate for you.

Thanks for the prompt reply. If you don't mind,

 

1. How is the current update helps us? (Since, we are mostly layman who doesn't understand technical terms, I wish to know what benefit latest update brings in comparison to the previous stable version)?

 

2. VPN are going to work as good as the previous version?

 

3. This update is going to fix any bugs of rutorrent/rtorrent?

 

Thanks.

Link to comment
1 minute ago, learningunraid said:

1. How is the current update helps us? (Since, we are mostly layman who doesn't understand technical terms, I wish to know what benefit latest update brings in comparison to the previous stable version)?

multiple fixes and improvements - resources usage is improved for one example.

 

1 minute ago, learningunraid said:

2. VPN are going to work as good as the previous version?

yes

 

1 minute ago, learningunraid said:

3. This update is going to fix any bugs of rutorrent/rtorrent?

see 1.

  • Like 1
Link to comment
Just now, binhex said:

multiple fixes and improvements - resources usage is improved for one example.

 

yes

 

see 1.

Thanks for the reply again, I will try the solution as you have suggested and will report back here.

 

One more question: Are we ever going to have Discord Server for the Binhex Fan Club? And if there is any channel in other discord server where you provide support, please let me know.

 

Thanks.

Link to comment
7 minutes ago, learningunraid said:

Thanks for the reply again, I will try the solution as you have suggested and will report back here.

 

One more question: Are we ever going to have Discord Server for the Binhex Fan Club? And if there is any channel in other discord server where you provide support, please let me know.

 

Thanks.

lol didn't realise i had a Fan Club 🙂

Link to comment
15 hours ago, VVnnXXzzAA said:

I've been trying to figure out the port forwarding situation for a while but not having any luck.  I use TorGuard which has facilities for port forwarding (you go on their customer portal and request a port to be forwarded for a given VPN server, then configure your ovpn file to hit that server so that with your credentials, they know to set up the forwarding on connect).  I've worked with their support team to validate that traffic is flowing through the forwarded port, but still, open port checker websites report the port is closed (although weirdly, if I hit a random port, I get an answer right away, but with my targeted port it takes a longer time to determine --as if it is timing out).  In any case, @binhex I'm not sure what's the best way to debug.  Privoxy works, torrent files work, but magnet links relying on DHT do not.  rtorrent also gives me MUCH higher speeds for the torrents that DO work vs deluge (saturating my internet bandwidth), so I really want to get this to work.  I'm running this on a QNAP NAS.  Is it possible that the iptables settings or the ip route are doing funny things?

 

Bump on this question, but also in trying to debug, I noticed that the iptables settings for INPUT allow all incoming traffic from the VPN tun0 interface.  Isn't that a security hole?  Shouldn't we be more selective about what ports to open for incoming traffic from the VPN network?

Link to comment
18 minutes ago, binhex said:

This will be a configuration option in your /config/rtorrent/config/rtorrent.rc file that is no longer compatible with the newer version of rtorrent (now v0.9.8).

 

The permanent fix for this is to simply rename or delete the existing config file /config/rtorrent/config/rtorrent.rc and then restart the container, then re-edit the config file if required to re-apply any settings you want, sadly this is not something i can automate for you.

 

I renamed the old .rc file, updated the container again to the new one and let a new .rc file get generated but im still getting:

 

2021-02-11 12:31:38,726 DEBG 'watchdog-script' stdout output:
[warn] Failed to start rTorrent, skipping initialisation of ruTorrent Plugins...

2021-02-11 12:32:08,909 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.x.xxx.101 different, marking for reconfigure

2021-02-11 12:32:08,912 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2021-02-11 12:32:08,916 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2021-02-11 12:32:08,919 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2021-02-11 12:32:08,920 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2021-02-11 12:32:08,942 DEBG 'watchdog-script' stdout output:
Script done.

2021-02-11 12:32:19,994 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries

2021-02-11 12:32:19,994 DEBG 'watchdog-script' stdout output:

 

Link to comment
19 minutes ago, VVnnXXzzAA said:

I noticed that the iptables settings for INPUT allow all incoming traffic from the VPN tun0 interface.  Isn't that a security hole?

not for 99% of providers, no, nearly all (there is only 1 I'm aware of that doesnt block) block all incoming ports, allowing to define a single port for port forwarding, so by default everything inbound is blocked.

Link to comment
17 minutes ago, DontWorryScro said:

I renamed the old .rc file, updated the container again to the new one and let a new .rc file get generated but im still getting:

ok thats really odd!, im running the latest image here myself so it has been tested. ok can you attach (not paste) your rtorrent.rc file and i will take a look at it and see if i can spot a problem with it.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.