[Support] binhex - rTorrentVPN

[kryptonite93]

Hey guys looking for some direction,

Have been using expressvpn on 2 trackers without an issue, ever since the most recent update all my torrents from tracker #2 say 

Tracker: [Could not parse bencoded data]

 

If i disable the vpn everything works on both trackers, was something changed in the most recent update for vpn handling? I looked into rolling back but I can't figure out how (new to unraid and dockers in general)

 

Thanks

[Pirate]

isnt the variable pieces.memory.max.set =  valid anymore in rtorrent.rc?

When i try it with both xxxxM and xGB rtorrent refuse to start.

 

[binhex]

isnt the variable pieces.memory.max.set =  valid anymore in rtorrent.rc?

When i try it with both xxxxM and xGB rtorrent refuse to start.

 

Quick Google search and I see examples like this:-

 

pieces.memory.max.set = 1800M

 

Is that how you are setting it?

 

Good doc:- https://www.google.com/url?sa=t&source=web&rct=j&url=https://readthedocs.org/projects/rtorrent-docs/downloads/pdf/latest/&ved=2ahUKEwjqy-zmo_DhAhXjXxUIHTGnAKcQFjADegQIAxAB&usg=AOvVaw3asbWapMaZJ0Wv12JM09ZU&cshid=1556368368996

Sent from my EML-L29 using Tapatalk

 

 

 

[Pirate]

13 minutes ago, binhex said:

Quick Google search and I see examples like this:-

 

pieces.memory.max.set = 1800M

 

Is that how you are setting it?

 

Good doc:- https://www.google.com/url?sa=t&source=web&rct=j&url=https://readthedocs.org/projects/rtorrent-docs/downloads/pdf/latest/&ved=2ahUKEwjqy-zmo_DhAhXjXxUIHTGnAKcQFjADegQIAxAB&usg=AOvVaw3asbWapMaZJ0Wv12JM09ZU&cshid=1556368368996

Sent from my EML-L29 using Tapatalk

 

 

 

Tried with both variables:

pieces.memory.max.set = 8192M and

pieces.memory.max.set = 8GB

Rtorrent doesnt start with any.

Edited April 27, 2019 by Pirate

[binhex]

4 hours ago, Pirate said:

Tried with both variables:

pieces.memory.max.set = 8192M and

pieces.memory.max.set = 8GB

Rtorrent doesnt start with any.

works for me, just added my example line to the top of my rtorrent.rc, restarted the container and it started first time, no issues, you arent using windows notepad are ya? if so then dont, you need something that respects line endings such as notepad++

[Pirate]

17 hours ago, binhex said:

works for me, just added my example line to the top of my rtorrent.rc, restarted the container and it started first time, no issues, you arent using windows notepad are ya? if so then dont, you need something that respects line endings such as notepad++

Weird, when im adding pieces.memory.max.set = 8192M it doesnt work.

 

Im using notepad++ to edit the rtorrent.rc

 

and the log only says:

 

2019-04-28 12:41:53,125 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2019-04-28 12:41:53,133 DEBG 'watchdog-script' stdout output:
Script started, file is /home/nobody/typescript

2019-04-28 12:41:53,213 DEBG 'watchdog-script' stdout output:
Script done, file is /home/nobody/typescript

2019-04-28 12:42:22,308 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted
[info] Waiting for rTorrent process to start listening on port 5000...

2019-04-28 12:42:22,308 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted
[info] Waiting for rTorrent process to start listening on port 5000...

 

*Edit: tried with everything between 2GB to 8GB

Edited April 28, 2019 by Pirate

[wcd]

First of all: Thank you @binhex for all your hard work on the vpn-torrent containers. These are great!

 

Only this rtorrent docker gives me headache. When I'm starting the docker for the first time it always takes around ten minutes to start. The log is stopping in every case at the same point. Full log: https://textuploader.com/1dd0u

After:

"2019-04-28 19:23:59.988292 [info] ENABLE_RPC2_AUTH defined as 'no'"

and before:

"2019-04-28 19:33:08.525499 [info] Starting Supervisor..."

 

And nothing in between. Even with debug:yes there is not more information.

 

My environment:

OMV / Debian 9

Docker version 18.09.5, build e8ff056dbc

 

I have tried docker-compose (prefered) but even with a plain docker command as mentioned here https://github.com/binhex/arch-rtorrentvpn (airvpn example)

Further I have tried with all extra services off (even vpn). But everytime with the same result.

 

Can you please help me out with this one?

 

Edit: Ahhh, and by the way: ENABLE_RPC2_AUTH: "no" does nothing. I have to authenticate nevertheless.

Edited April 28, 2019 by wcd

[binhex]

2 hours ago, wcd said:

When I'm starting the docker for the first time it always takes around ten minutes to start.

this is due to chmod/chown of files/folders inside the container to match the puid and pgid chosen, as you rightly state it happens only on the first run of the container, obviously if you upgrade the image then this will mean deletion of the container and re-creation so it will happen on updates too. the excessively long wait times are due to a rather nasty bug in docker (see link below) with affects people running storage driver 'overlay2', the default for unraid users is btrfs and using this storage driver the chmod/chown takes less than a second to complete! so as you can see quite a difference!. im afraid there is nothing i can really do about this, the chmod/chown has to happen and i cant fix the docker bug, so all that you can do is switch storage driver or just accept the wait for now and hope it gets fixed.

 

issue here:- https://github.com/docker/for-linux/issues/388

 

2 hours ago, wcd said:

Ahhh, and by the way: ENABLE_RPC2_AUTH: "no" does nothing. I have to authenticate nevertheless.

you sure about that?, do you mean authenticate for the web ui? if so thats different.

Edited April 28, 2019 by binhex

[binhex]

9 hours ago, Pirate said:

Weird, when im adding pieces.memory.max.set = 8192M it doesnt work.

 

Im using notepad++ to edit the rtorrent.rc

 

and the log only says:

 

2019-04-28 12:41:53,125 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2019-04-28 12:41:53,133 DEBG 'watchdog-script' stdout output:
Script started, file is /home/nobody/typescript

2019-04-28 12:41:53,213 DEBG 'watchdog-script' stdout output:
Script done, file is /home/nobody/typescript

2019-04-28 12:42:22,308 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted
[info] Waiting for rTorrent process to start listening on port 5000...

2019-04-28 12:42:22,308 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted
[info] Waiting for rTorrent process to start listening on port 5000...

 

*Edit: tried with everything between 2GB to 8GB

attach (dont paste) your rtorrent.rc file and i will give it a spin here and see if i can work out whats going on.

[wcd]

18 minutes ago, binhex said:

this is due to chmod/chown of files/folders inside the container to match the puid and pgid chosen, as you rightly state it happens only on the first run of the container, obviously if you upgrade the image then this will mean deletion of the container and re-creation so it will happen on updates too. the excessively long wait times are due to a rather nasty bug in docker (see link below) with affects people running storage driver 'overlay2', the default for unraid users is btrfs and using this storage driver the chmod/chown takes less than a second to complete! so as you can see quite a difference!. im afraid there is nothing i can really do about this, the chmod/chown has to happen and i cant fix the docker bug, so all that you can do is switch storage driver or just accept the wait for now and hope it gets fixed.

issue here:- https://github.com/docker/for-linux/issues/388

Thanks for this explanation. But the stange thing is... Your deluge container starts instantly (same environment... same puid pgid, same storage driver). This is from the log of your arch-delugevpn container:

2019-04-28 10:59:32.499692 [info] ENABLE_PRIVOXY defined as 'no'
2019-04-28 10:59:33.321485 [info] Starting Supervisor...

What is different with the chmode/chown -R on die deluge docker? Maybe this consideration helps.

 

Quote

you sure about that?, do you mean authenticate for the web ui? if so thats different.

I mean the rutorrent webui on port 9080. What du you mean with different?

Edited April 28, 2019 by wcd

[binhex]

1 minute ago, wcd said:

What is different with the chmode/chown -R on die deluge docker? Maybe this consideration helps.

hmm that is a bit odd, its the same code just different files/folders to alter, perhaps there are just significantly less in deluge, i would have to check but that would be the only explanation i can think of.

 

2 minutes ago, wcd said:

I mean the rutorrent webui on port 9080. What du you mean with different?

web ui authentication is handled separately to rpc2, which is generally used by other applications to communicate with rtorrent/rutorrent (such as sonarr, radarr, medusa etc).

[wcd]

17 minutes ago, binhex said:

hmm that is a bit odd, its the same code just different files/folders to alter, perhaps there are just significantly less in deluge, i would have to check but that would be the only explanation i can think of.

For another test I configured and started your arch-qbittorrentvpn container. Everything works. 0.8s on first start to do the chmod -R.

docker-compose.yml: https://textuploader.com/1ddox

log of the first start: https://textuploader.com/1ddog

 

17 minutes ago, binhex said:

web ui authentication is handled separately to rpc2, which is generally used by other applications to communicate with rtorrent/rutorrent (such as sonarr, radarr, medusa etc).

OK, Understood. So if I want to disable the authentification for the webui I have to edit the /config/nginx/config/nginx.conf?

 

 

[Pirate]

9 hours ago, binhex said:

attach (dont paste) your rtorrent.rc file and i will give it a spin here and see if i can work out whats going on.

Here u have the current rtorrent.rc file, hope that u spot something unusual.

rtorrent.rc

[binhex]

2 hours ago, Pirate said:

Here u have the current rtorrent.rc file, hope that u spot something unusual.

rtorrent.rc 5.09 kB · 0 downloads

you are copying in non ascii characters, see screenshot below, note the ? symbols in there, this is probably your issue:-

 

 

here is a clean copy of your config file attached, not tested it but i would expect it to work.

 

 

rtorrent.rc

[Pirate]

2 hours ago, binhex said:

you are copying in non ascii characters, see screenshot below, note the ? symbols in there, this is probably your issue:-

 

 

here is a clean copy of your config file attached, not tested it but i would expect it to work.

 

 

rtorrent.rc 5.08 kB · 1 download

Tried it but didnt work, so i deleted the docker and reinstalled it and now it works.

Thanks for the help Binhex.

[wcd]

On 4/28/2019 at 11:18 PM, wcd said:

For another test I configured and started your arch-qbittorrentvpn container. Everything works. 0.8s on first start to do the chmod -R.

docker-compose.yml: https://textuploader.com/1ddox

log of the first start: https://textuploader.com/1ddog

 

OK, Understood. So if I want to disable the authentification for the webui I have to edit the /config/nginx/config/nginx.conf?

 

 

@binhex Did you see my post from sunday ? Is there anything more I can test to sort things out?

[binhex]

19 hours ago, wcd said:

@binhex Did you see my post from sunday ? Is there anything more I can test to sort things out?

if the 10 min delay only happens on first run of the container then it is def linked to the chown, same code as all the other containers so i can only assume its due to the number of files/folders, as you can see from the code below the number of files/folders touched for this container are significantly more than the other images (due to more moving parts), so it must be due to that, not much i can do about it im afraid, that overlay2 bug is a kicker!.

 

# define comma separated list of paths 
install_paths="/etc/webapps,/usr/share/webapps,/usr/share/nginx/html,/etc/nginx,/etc/php,/run/php-fpm,/var/lib/nginx,/var/log/nginx,/etc/privoxy,/home/nobody,/etc/webapps/flood,/usr/share/autodl-irssi"

 

 

[jraid]

I've having trouble seeding, after creating a new rutorrent web user via the provided createuser.sh script.

I can finish torrents successfully but after they hash check and get moved, they enter a 0%, "Download registered as completed, but hash check returned unfinished chunks." state.

I assume it's a permission error, I deleted the default web user - but the folder permissions look okay and I don't know why the web user is affecting anything on the file system. Any tips? Any log files to check for rtorrent? I don't see anything in supervisor log.

 

Edit: well now I tried to install the LogOff plugin and got a PHP error, followed by deleting the plugin's folder (original state) and breaking rutorrent completely:

Bad response from server: (200 [parsererror,getplugins]) SyntaxError: expected expression, got ';'

 

Edited May 7, 2019 by jraid

[markomax]

Privoxy has stopped working for me after pulling the latest version of this. I usually use Privoxy with Sonarr/Radarr/Lidarr/Jackett but they no longer work when I use hostname: localhost and port: 8118. I noticed that there were some new settings for RPC2 and RPC2_AUTH.  Is there some sort of username and password required for Privoxy too now?

[binhex]

Privoxy has stopped working for me after pulling the latest version of this. I usually use Privoxy with Sonarr/Radarr/Lidarr/Jackett but they no longer work when I use hostname: localhost and port: 8118. I noticed that there were some new settings for RPC2 and RPC2_AUTH.  Is there some sort of username and password required for Privoxy too now?

Delete /config/privoxy/ folder and restart container

Sent from my EML-L29 using Tapatalk

[ZChadwick]

I'm having an issue with the image not actually starting. Did a docker pull for it on Ubuntu 18.10.

 

Start the container and cockpit shows this as terminal readout:

 

Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2019-05-15 22:09:14.207768 [info] System information Linux df8fadd85e18 4.18.0-18-generic #19-Ubuntu SMP Tue Apr 2 18:13:16 UTC 2019 x86_64 GNU/Linux
2019-05-15 22:09:14.334125 [info] PUID defined as '0'
2019-05-15 22:09:18.432100 [info] PGID defined as '0'
2019-05-15 22:09:19.287521 [info] UMASK defined as '000'
2019-05-15 22:09:19.412451 [info] Permissions already set for volume mappings
2019-05-15 22:09:19.553561 [info] VPN_ENABLED defined as 'yes'
2019-05-15 22:09:19.627185 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CAToronto.ovpn
dos2unix: converting file /config/openvpn/CAToronto.ovpn to Unix format...
2019-05-15 22:09:21.670743 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198'
2019-05-15 22:09:21.797690 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com'
2019-05-15 22:09:21.926709 [info] VPN_PORT defined as '1198'
2019-05-15 22:09:22.028138 [info] VPN_PROTOCOL defined as 'udp'
2019-05-15 22:09:22.151914 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-05-15 22:09:22.208972 [info] VPN_PROV defined as 'pia'
2019-05-15 22:09:22.333398 [info] LAN_NETWORK defined as '192.168.1.0/24'
2019-05-15 22:09:22.459349 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2019-05-15 22:09:22.585034 [info] VPN_USER defined as **
2019-05-15 22:09:22.710369 [info] VPN_PASS defined as **
2019-05-15 22:09:22.836480 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-05-15 22:09:22.962125 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-05-15 22:09:23.087987 [info] ENABLE_PRIVOXY defined as 'no'
2019-05-15 22:09:23.214494 [info] ENABLE_FLOOD defined as 'both'
2019-05-15 22:09:23.341198 [warn] ENABLE_AUTODL_IRSSI not defined (via -e ENABLE_AUTODL_IRSSI), defaulting to 'no'
2019-05-15 22:09:23.467948 [warn] ENABLE_RPC2 not defined (via -e ENABLE_RPC2), defaulting to 'yes'
2019-05-15 22:09:23.593995 [warn] ENABLE_RPC2_AUTH not defined (via -e ENABLE_RPC2_AUTH), defaulting to 'yes'

Unfortunately it just sits there and never really starts. I've left it sitting for hours with no change. I've deleted the container, redownloaded a few times, but no luck. Any ideas?

 

Also to add, I have your Sonarr, Radarr, and Sabnzbd containers running without issues. I was also running the delugevpn without issue but wanted to try rtorrent. This is the only container I've run into any issues with.

Edited May 15, 2019 by ZChadwick

[noob32]

Hey!

 

I've setup the container on my Synology NAS. The setup worked out, I can access flood, get an answer from port 8118, but cannot acces the WebUI under 9080. Could anyone help me out?

[rikdegraaff]

Just wanted to change the ratio settings in RuTorrent, 'cause all my torrents stop at 1.000

So gone to config button en clicked on ratio groups

Here you can see the ratio groups, I've set all the torrents to group 8, but doesn't change anything...

 

My Upload ETA is set to 150%.

Has that something to do with stopping at 1.000

[binhex]

On 5/18/2019 at 10:06 PM, rikdegraaff said:

Just wanted to change the ratio settings in RuTorrent, 'cause all my torrents stop at 1.000

So gone to config button en clicked on ratio groups

Here you can see the ratio groups, I've set all the torrents to group 8, but doesn't change anything...

 

My Upload ETA is set to 150%.

Has that something to do with stopping at 1.000

try setting min,% value to 150, i dont use ratio groups but im assuming its hitting a min% of 100 (as in ratio 1.0) and stopping.

[rikdegraaff]

Seems to work with min,% value set to 150.

Thanks, @binhex