[Support] binhex - rTorrentVPN


Recommended Posts

On 12/28/2022 at 8:42 AM, fonzie said:

This docker has been working perfectly for a long time, but just recently have the speeds been super slow to completely stopped.  Some torrents will show there are no seeders (when I know there should be) and even those with seeders will not download.

 

I'm using Private Internet Access as a VPN provider.  I was using the Berlin VPN for years and it's been fine up until recently.  Tried changing it to the Mexico one, due to lower latency, but it is the same issue, if not worse.

 

Does anyone have a recommendation for a city to use with Private Internet Access and this docker?  Or know of anything that could be causing my downloading issues?

 

 

+1

Been noticing that the little port checker icon on the bottom has been giving me lots of yellow triangles or straight up red exclaimation circles telling me ports are unverified or closed with a 127.0.0.1:[port] showing often.  I have to assume something has changed with PIA OpenVPN servers recently.  I was using Berlin flawlessly for years.  Now I cant even find port forwarded location list on the PIA site.  They seem to make it hard to find.  But I only ask here to see if this is not in fact a PIA thing and that something may have changed in the client.  Anyone solve this yet?

  • Like 1
Link to comment

I'm curious about switching to this image but haven't been able to figure something out. I want to use PIA with a static VPN on this image. I assumed there might be some mechanism for doing so with the VPN_OPTIONS env var, but I haven't been able to trace that var through the repo for this image so I'm unsure where to go from here.

 

Edit: I'm told by PIA support that I must use their client to use their Dedicated IP

Edited by ghixmir
got more info from PIA support
Link to comment
On 1/19/2023 at 2:25 PM, DontWorryScro said:

 

 

+1

Been noticing that the little port checker icon on the bottom has been giving me lots of yellow triangles or straight up red exclaimation circles telling me ports are unverified or closed with a 127.0.0.1:[port] showing often.  I have to assume something has changed with PIA OpenVPN servers recently.  I was using Berlin flawlessly for years.  Now I cant even find port forwarded location list on the PIA site.  They seem to make it hard to find.  But I only ask here to see if this is not in fact a PIA thing and that something may have changed in the client.  Anyone solve this yet?

 

Haven't fixed it for myself yet.  I'm using PIA and installed the qbittorrentVPN docker and the speeds are much faster using the same PIA VPN server so I have to assume that it's an issue with either rtorrent or the docker itself.

 

I just wish I could fix this issue because I much prefer the feature rich rTorrentVPN docker over the qbittorrentVPN docker.  I'll be checking in this thread regularly to see if any updates come by that let me come back to this docker.

 

Link to comment
 
Haven't fixed it for myself yet.  I'm using PIA and installed the qbittorrentVPN docker and the speeds are much faster using the same PIA VPN server so I have to assume that it's an issue with either rtorrent or the docker itself.
 
I just wish I could fix this issue because I much prefer the feature rich rTorrentVPN docker over the qbittorrentVPN docker.  I'll be checking in this thread regularly to see if any updates come by that let me come back to this docker.
 

I switched to using PIA WireGuard instead of OpenVPN and rutorrentvpn and my speeds doubled almost tripled


Sent from my iPhone using Tapatalk
Link to comment
On 1/22/2023 at 9:52 AM, DontWorryScro said:


I switched to using PIA WireGuard instead of OpenVPN and rutorrentvpn and my speeds doubled almost tripled

 

I'll give that a try.  I see the option in the docker settings for rutorrentVPN to change from openvpn to wireguard, but where in the private internet access website can i find the config files for wireguard?  And where in the docker will I place them once I have them?

Link to comment
3 hours ago, fonzie said:

but where in the private internet access website can i find the config files for wireguard?  And where in the docker will I place them once I have them?

dont worry about that, its all done automagically for you :-).

Link to comment
Interesting.  So how do I select which VPN server rtorrentVPN connects to if it's done automatically?  Or do I just let it choose the best option?
 
It is hard coded on first run to connect to the Netherlands if you then wish to change the endpoint then you can edit the wireguard config file and change it to your desired endpoint connection - see /config/supervisord.log for a list of available endpoints.

Sent from my 22021211RG using Tapatalk

Link to comment
11 hours ago, binhex said:

It is hard coded on first run to connect to the Netherlands if you then wish to change the endpoint then you can edit the wireguard config file and change it to your desired endpoint connection - see /config/supervisord.log for a list of available endpoints.

Sent from my 22021211RG using Tapatalk
 

 

Does wireguard only work with PIA? I use TorGuard and was thinking of maybe trying to switch to WG to see if it works better/is faster than using OVPN. 

Link to comment
 
Does wireguard only work with PIA? I use TorGuard and was thinking of maybe trying to switch to WG to see if it works better/is faster than using OVPN. 
This docker image is designed you work with any VPN provider that supports openvpn and/or wireguard

Sent from my 22021211RG using Tapatalk

Link to comment

Just deleted my rtorrentvpn container and removed the image and deleted the appdata folder just to start fresh.

 

When trying to start the container I'm getting this error:

 

2023-01-28 02:04:19,647 DEBG 'watchdog-script' stdout output:
Script done.

2023-01-28 02:04:30,759 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...

2023-01-28 02:05:15,818 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.24.138.156 different, marking for reconfigure

2023-01-28 02:05:15,825 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2023-01-28 02:05:15,826 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2023-01-28 02:05:15,828 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2023-01-28 02:05:15,830 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2023-01-28 02:05:15,860 DEBG 'watchdog-script' stdout output:
Script done.

2023-01-28 02:05:26,971 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...

 

It just keeps going round and round giving that error.

Any ideas? I'm pretty sure everything to do with this container is fresh and "untainted" by human error.. My docker run is identical to how I had it previously.

Link to comment

My docker run:

Docker run
  -d
  --name='binhex-rtorrentvpn'
  --net='proxynet'
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="binhex-rtorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='...'
  -e 'VPN_PASS'='...'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_AUTODL_IRSSI'='no'
  -e 'ENABLE_RPC2'='yes'
  -e 'ENABLE_RPC2_AUTH'='yes'
  -e 'ENABLE_WEBUI_AUTH'='yes'
  -e 'RPC2_USER'='...'
  -e 'RPC2_PASS'='...'
  -e 'WEBUI_USER'='...'
  -e 'WEBUI_PASS'='...'
  -e 'LAN_NETWORK'='192.168.69.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'PHP_TZ'='UTC'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:9080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/rtorrent-icon.png'
  -p '5000:5000/tcp'
  -p '9080:9080/tcp'
  -p '9443:9443/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/data/torrents/':'/data/torrents':'rw'
  -v '/mnt/user/appdata/binhex-rtorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-rtorrentvpn'

7363c663c14046b494d6a97245c04bde3edf4b12240f042fd2a23d86cbfe468d

The command finished successfully!

 

Link to comment

Is there some trick building this from source? I build it with just docker build . but that's not getting me very far right now :( It behaves very strange. When I build two images show up, one binhex/arch-int-vpn and another untagged one. A container also shows up that isn't tagged. I see from the docker build file that binhex/arch-int-vpn is pulled in as the base, so that makes sense.

Edited by doubleopinter
Link to comment
On 1/28/2023 at 2:10 AM, Partial said:

Just deleted my rtorrentvpn container and removed the image and deleted the appdata folder just to start fresh.

 

When trying to start the container I'm getting this error:

 

2023-01-28 02:04:19,647 DEBG 'watchdog-script' stdout output:
Script done.

2023-01-28 02:04:30,759 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...

2023-01-28 02:05:15,818 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.24.138.156 different, marking for reconfigure

2023-01-28 02:05:15,825 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2023-01-28 02:05:15,826 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2023-01-28 02:05:15,828 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2023-01-28 02:05:15,830 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2023-01-28 02:05:15,860 DEBG 'watchdog-script' stdout output:
Script done.

2023-01-28 02:05:26,971 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...

 

It just keeps going round and round giving that error.

Any ideas? I'm pretty sure everything to do with this container is fresh and "untainted" by human error.. My docker run is identical to how I had it previously.

 

I figured out my issue so I'll put my resolution here for any future dummies like me:

I changed the default container path.. When it generates the rtorrent.rc file it doesn't know this and uses the original default.

I went into rtorrent.rc and changed:

 

execute = {/bin/bash,-c,mkdir -p /data/torrents}
directory.default.set = /data/torrents/

 

which coincide with my new paths. Everything works now and it was definitely user error from a change I made a while ago.

 

FYI I changed the paths based on "Trash Guides" guide to get hard links working for faster/instant Sonarr imports.

 

Link to comment

Ok I managed to build the latest release. I'm getting errors when I try to start,

 

2023-01-30 23:29:58,623 INFO spawnerr: command at '/home/nobody/logrotate.sh' is not executable
2023-01-30 23:29:58,623 INFO spawnerr: command at '/home/nobody/pyrocore.sh' is not executable
2023-01-30 23:29:58,624 INFO spawnerr: command at '/home/nobody/rutorrent.sh' is not executable
2023-01-30 23:29:58,624 INFO spawnerr: command at '/home/nobody/watchdog.sh' is not executable
2023-01-30 23:30:01,628 INFO spawnerr: command at '/home/nobody/logrotate.sh' is not executable

 

I hacked at it and +x those files but I think there's something fundamentally wrong. After +x to those files, tmux was missing for some reason. After installing that it still doesn't start just indicating that rtorrent wasn't able to start.

Edited by doubleopinter
Link to comment

Tried building the latest code on Ubuntu and managed to get a different error now. Except that I can even ping that github ip from the host building this.

#0 83.73 Successfully installed wheel-0.37.1
#0 84.09 Getting pyrobase...
#0 84.09 Cloning into 'pyrobase'...
#0 213.4 fatal: unable to connect to github.com:
#0 213.4 github.com[0: 140.82.113.3]: errno=Connection timed out
#0 213.4
------
Dockerfile:27
--------------------
  26 |     # make executable and run bash scripts to install app
  27 | >>> RUN chmod +x /root/*.sh /home/nobody/*.sh && \
  28 | >>> 	/bin/bash /root/install.sh "${release_tag_name}"
  29 |
--------------------
ERROR: failed to solve: process "/bin/sh -c chmod +x /root/*.sh /home/nobody/*.sh && \t/bin/bash /root/install.sh \"${release_tag_name}\"" did not complete successfully: exit code: 128

 

Edited by doubleopinter
Link to comment
  • 2 weeks later...

Hello,

 

I have encountered a very perceuliar issue which has been difficult to diagnose and has repeated itself twice (I reinstalled Unraid after a server rebuild).

 

In short, I use a NordVPN account and this docker but encounter what seems to be an invisible 1MB/s (almost exactly 8-9 mbps), I have 100% double checked I have no limit set within rtorrent, and if I remove the openvpn config it goes back to normal using all my net connection.

 

However if I connect to exactly the same VPN Openvpn profile manually on my MacBook, I can obtain full speeds as expected (40-50mbps.

 

Can anyone point me in the direction of how I can rectify this please?

 

Let me know if there is anything further I can provide to help investigate it.

Please be gentle as I am an Unraid novice :)

 

Screenshot 2023-02-10 at 20.25.57.png

Screenshot 2023-02-10 at 20.42.10.png

Link to comment

 I am trying to use this docker with the br0 setting and changing the webui port to 80.  But for some reason it stays at 9080, no matter what I do.  I have disabled almost everything else for now, but this still happens.

 

Here is the docker run command:
 

docker run
  -d
  --name='binhex-rtorrentvpn'
  --net='br0'
  --ip='192.168.1.243'
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Portrush"
  -e HOST_CONTAINERNAME="binhex-rtorrentvpn"
  -e 'TCP_PORT_5000'='5000'
  -e 'TCP_PORT_9080'='80'
  -e 'TCP_PORT_9443'='9443'
  -e 'TCP_PORT_8118'='8118'
  -e 'VPN_ENABLED'='no'
  -e 'VPN_USER'='vpn username'
  -e 'VPN_PASS'='vpn password'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_AUTODL_IRSSI'='no'
  -e 'ENABLE_RPC2'='no'
  -e 'ENABLE_RPC2_AUTH'='no'
  -e 'ENABLE_WEBUI_AUTH'='no'
  -e 'RPC2_USER'='admin'
  -e 'RPC2_PASS'=''
  -e 'WEBUI_USER'='webui username'
  -e 'WEBUI_PASS'='webui password'
  -e 'LAN_NETWORK'='192.168.1.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'PHP_TZ'='UTC'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:9080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/rtorrent-icon.png'
  -v '/mnt/user/media/torrents':'/data':'rw'
  -v '/mnt/user/appdata/binhex-rtorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-rtorrentvpn'

94329f8da75053c1cbc4a041453ab0f0b81ca2d58f8af3ef3661715xxxxxx

 

 

But in the docker page of the webui it shows this for ports:

192.168.1.243:49160/TCP192.168.1.243:49160
192.168.1.243:49170/TCP192.168.1.243:49170
192.168.1.243:5000/TCP192.168.1.243:5000
192.168.1.243:8118/TCP192.168.1.243:8118
192.168.1.243:9080/TCP192.168.1.243:9080
192.168.1.243:9443/TCP192.168.1.243:9443

 

Link to comment
  • binhex locked this topic
Guest
This topic is now closed to further replies.