[Support] binhex - rTorrentVPN


Recommended Posts

2 hours ago, binhex said:

new image got built a day or two ago.

I just did a quick test before going to work, I can do some more once I get back, but it looks like I'm getting the same results as before. I can ping the container, but no webui and sonarr/radarr can't access it.

Link to comment

Hi binhex, everything worked great for me up until today and now when I start the container I get this. I searched this thread and saw some people reporting it months ago and last year, but their problem was solved since then. I tried removing the rtorrent.rc file as suggested and also to start from scratch, but it still doesn't work. Will appreciate your help, thank you.

 

2018-12-20 20:37:47,845 DEBG received SIGCLD indicating a child quit                                                                                                                                                                                        
2018-12-20 20:37:47,848 DEBG 'irssi-script' stdout output:                                                                                                                                                                                                  
[info] Autodl-irssi not enabled, skipping startup                                                                                                                                                                                                           
                                                                                                                                                                                                                                                            
2018-12-20 20:37:47,849 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 140540345675720 for <Subprocess at 140540345672552 with name irssi-script in state RUNNING> (stdout)>                                                                   
2018-12-20 20:37:47,849 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 140540345700792 for <Subprocess at 140540345672552 with name irssi-script in state RUNNING> (stderr)>                                                                   
2018-12-20 20:37:47,850 INFO exited: irssi-script (exit status 0; expected)                                                                                                                                                                                 
2018-12-20 20:37:47,850 DEBG received SIGCLD indicating a child quit                                                                                                                                                                                        
2018-12-20 20:37:47,936 DEBG 'watchdog-script' stderr output:                                                                                                                                                                                               
dos2unix: converting file /config/rtorrent/config/rtorrent.rc to Unix format...                                                                                                                                                                             
                                                                                                                                                                                                                                                            
2018-12-20 20:37:48,071 DEBG 'watchdog-script' stdout output:                                                                                                                                                                                               
[info] rTorrent not running                                                                                                                                                                                                                                 
                                                                                                                                                                                                                                                            
2018-12-20 20:37:48,071 DEBG 'watchdog-script' stdout output:                                                                                                                                                                                               
[info] Removing any rTorrent session lock files left over from the previous run...                                                                                                                                                                          
                                                                                                                                                                                                                                                            
2018-12-20 20:37:48,077 DEBG 'watchdog-script' stdout output:                                                                                                                                                                                               
[info] Attempting to start rTorrent...                                                                                                                                                                                                                      
                                                                                                                                                                                                                                                            
2018-12-20 20:37:48,090 DEBG 'watchdog-script' stdout output:                                                                                                                                                                                               
Script started, file is /home/nobody/typescript                                                                                                                                                                                                             
                                                                                                                                                                                                                                                            
2018-12-20 20:37:48,142 DEBG 'watchdog-script' stdout output:                                                                                                                                                                                               
error creating /tmp/tmux-99 (Permission denied)                                                                                                                                                                                                             
                                                                                                                                                                                                                                                            
2018-12-20 20:37:48,251 DEBG 'watchdog-script' stdout output:                                                                                                                                                                                               
Script done, file is /home/nobody/typescript                                                                                                                                                                                                                
                                                                                                                                                                                                                                                            
2018-12-20 20:38:17,551 DEBG 'watchdog-script' stdout output:                                                                                                                                                                                               
[warn] Wait for rTorrent process to start aborted                                                                                                                                                                                                           
[info] Waiting for rTorrent process to start listening on port 5000... 

 

Edited by tomllic
Link to comment
2 hours ago, binhex said:

are you running this with privileged = true/yes ? im assuming not.

I did not, but I did not run it in privileged before either and it worked just fine. But I saw your post and decided to try anyway. So I'm running privileged now but I still get the same result. Any help would be appreciated, thank you.

 

 

2018-12-21 14:13:24,180 DEBG 'watchdog-script' stdout output:                                                                                            
Script started, file is /home/nobody/typescript                                                                                                          
                                                                                                                                                         
2018-12-21 14:13:24,192 DEBG 'watchdog-script' stdout output:                                                                                            
error creating /tmp/tmux-99 (Permission denied)                                                                                                          
                                                                                                                                                         
2018-12-21 14:13:24,204 DEBG 'watchdog-script' stdout output:                                                                                            
Script done, file is /home/nobody/typescript 

[warn] Wait for rTorrent process to start aborted                                                                                                        
[info] Waiting for rTorrent process to start listening on port 5000...                                                                                                                                                                                                                                 
^C2018-12-21 14:16:34,198 WARN received SIGINT indicating exit request                                                                                   
2018-12-21 14:16:34,199 INFO waiting for rutorrent-script, watchdog-script to die                                                                        

2018-12-21 14:16:35,200 DEBG killing watchdog-script (pid 68) with signal SIGTERM                                                                        
2018-12-21 14:16:35,201 DEBG fd 27 closed, stopped monitoring <POutputDispatcher at 139818717582184 for <Subprocess at 139818717554088 with name watchdog
-script in state STOPPING> (stdout)>                                                                                                                     
2018-12-21 14:16:35,202 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 139818717582616 for <Subprocess at 139818717554088 with name watchdog
-script in state STOPPING> (stderr)> 

2018-12-21 14:16:35,202 INFO stopped: watchdog-script (terminated by SIGTERM)                                                                            
2018-12-21 14:16:35,203 DEBG received SIGCLD indicating a child quit                                                                                     
2018-12-21 14:16:36,205 DEBG killing rutorrent-script (pid 65) with signal SIGTERM                                                                       
2018-12-21 14:16:36,206 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 139818717555384 for <Subprocess at 139818717553800 with name rutorren
t-script in state STOPPING> (stderr)>                                                                                                                    
2018-12-21 14:16:36,206 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 139818717554952 for <Subprocess at 139818717553800 with name rutorren
t-script in state STOPPING> (stdout)>                                                                                                                    
2018-12-21 14:16:36,206 INFO stopped: rutorrent-script (terminated by SIGTERM)                                                                           
2018-12-21 14:16:36,206 DEBG received SIGCLD indicating a child quit 

 

Link to comment

Need some help running this on synology, I've had it running on an ubuntu VM for a long time but want to move it to my NAS. 

I'm stuck with the error thats been discussed before, but I couldn't find any solution 

 

Quote

2018-12-23 15:30:40,092 DEBG 'rutorrent-script' stdout output:
[info] starting nginx...

2018-12-23 15:30:40,094 DEBG 'rutorrent-script' stderr output:
2018/12/23 15:30:40 [emerg] 2456#2456: open() "/etc/nginx/nginx.conf" failed (13: Permission denied)

2018-12-23 15:30:40,094 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 139753860495912 for <Subprocess at 139753860494976 with name rutorrent-script in state RUNNING> (stdout)>
2018-12-23 15:30:40,094 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 139753860496200 for <Subprocess at 139753860494976 with name rutorrent-script in state RUNNING> (stderr)>
2018-12-23 15:30:40,094 INFO exited: rutorrent-script (exit status 1; not expected)
2018-12-23 15:30:40,094 DEBG received SIGCLD indicating a child quit
2018-12-23 15:30:40,931 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2018-12-23 15:30:40,934 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening

2018-12-23 15:30:40,936 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2018-12-23 15:30:40,939 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...


Capture2.thumb.PNG.3934083185a3371d409653dc231b726d.PNG

I've tried running it with different PUID/GUID

First try was with my regular account "administrator"

PUID = 1026
GUID = 101

administrator@NAS:/volume2/RAID/Docker/Torrent$ id
uid=1026(administrator) gid=100(users) groups=100(users),101(administrators),65536(docker)

Second try was with root

PUID = 0
GUID = 0

administrator@NAS:/volume2/RAID/Docker/Torrent$ id root
uid=0(root) gid=0(root) groups=0(root),2(daemon),19(log)

I have checked the "Execute container using high privilige" in the general settings tab of the container in synology docker GUI. 
I've tried to change permissions on the host's /etc/nginx folder because I thought that's were the permission was struggeling, but it seems like it's inside the container(?)

What else can I try?
 

Quote

administrator@NAS:/volume2/RAID/Docker/Torrent$ docker version
Client:
 Version:      17.05.0-ce
 API version:  1.29
 Go version:   go1.8
 Git commit:   9f07f0e-synology
 Built:        Thu Oct 11 21:32:14 2018
 OS/Arch:      linux/amd64

Server:
 Version:      17.05.0-ce
 API version:  1.29 (minimum version 1.12)
 Go version:   go1.8
 Git commit:   9f07f0e-synology
 Built:        Thu Oct 11 21:32:14 2018
 OS/Arch:      linux/amd64
 Experimental: false
 





 

Link to comment

I cannot get the docker to work on my synology.  I keep getting this error

2018-12-27 18:55:08,938 DEBG 'rutorrent-script' stderr output:
2018/12/27 18:55:08 [emerg] 957#957: open() "/etc/nginx/nginx.conf" failed (13: Permission denied)
2018-12-27 18:55:08,939 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 139878450088560 for <Subprocess at 139878450087624 with name rutorrent-script in state RUNNING> (stdout)>
2018-12-27 18:55:08,939 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 139878450088848 for <Subprocess at 139878450087624 with name rutorrent-script in state RUNNING> (stderr)>
2018-12-27 18:55:08,939 INFO exited: rutorrent-script (exit status 1; not expected)
2018-12-27 18:55:08,940 DEBG received SIGCLD indicating a child quit
2018-12-27 18:55:09,546 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...
2018-12-27 18:55:09,555 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening
2018-12-27 18:55:09,562 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...
2018-12-27 18:55:09,570 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

I looked through the thread and found it could be an error with my permissions, I checked

I am using the admin account to run it in the users group  

drwxrwxr-x 1 admin users   20 Dec 27 11:21 .
drwxrwxr-x 1 admin users   38 Dec 27 11:21 ..
-rwxrwxr-x 1 admin users 3694 Dec 27 11:21 nginx.conf

I cannot get the rutorrent WebUI to come up.  I got the deluge to work on this synology but greatly prefer the rutorrent interface.  Let me know if you need anymore information or if there is anything I can try to get it to work.

-Edit:

I completed these steps  https://www.reddit.com/r/synology/comments/4gpf9d/docker_and_apparmor_issue/

It seems to have fixed that stinking point but will I have to run this everytime I restart the box?

Edited by kansurr
Link to comment

How do I increase the 2MiB upload file limit restriction for rutorrent?

 

Untitled.png.439c2de1f530e1f601c6adc80947d74d.png

 

The ngnix upload restriction seems to be 25mb.  The PHP restriction seems to be 20mb.

 

Using latest version from docker hub

~$ sudo docker pull binhex/arch-rtorrentvpn
Using default tag: latest
latest: Pulling from binhex/arch-rtorrentvpn
Digest: sha256:ef7d7f24caebc2ee2ba8c06fd00c3d42e7d9523c05372bdc0c2b94349cd6152d
Status: Image is up to date for binhex/arch-rtorrentvpn:latest

 

Link to comment
On 12/28/2018 at 11:46 PM, jenga201 said:

How do I increase the 2MiB upload file limit restriction for rutorrent?

 

Untitled.png.439c2de1f530e1f601c6adc80947d74d.png

 

The ngnix upload restriction seems to be 25mb.  The PHP restriction seems to be 20mb.

 

Using latest version from docker hub


~$ sudo docker pull binhex/arch-rtorrentvpn
Using default tag: latest
latest: Pulling from binhex/arch-rtorrentvpn
Digest: sha256:ef7d7f24caebc2ee2ba8c06fd00c3d42e7d9523c05372bdc0c2b94349cd6152d
Status: Image is up to date for binhex/arch-rtorrentvpn:latest

 

from my googling this looks like a limit of rtorrent, so not sure it can be changed, however it can be worked around by dropping your torrent into the watched folder.

Link to comment
44 minutes ago, bobbintb said:

I'm having trouble getting an open port. I presume it has to do with the VPN. I opened the port on my router. I don't use PIA. Any idea what I need to do?

Assuming you are using a VPN, the port has to be opened from the VPN provider side. PIA is automatically scripted to work, other providers you may need to configure it manually. There is NO scenario where your router has anything to do with the port through a VPN provider, so you need to close that port.

 

BTW, very few VPN providers actually work with port forwarding, and PIA only has select endpoints that support it.

Link to comment
2 minutes ago, jonathanm said:

Assuming you are using a VPN, the port has to be opened from the VPN provider side. PIA is automatically scripted to work, other providers you may need to configure it manually. There is NO scenario where your router has anything to do with the port through a VPN provider, so you need to close that port.

 

BTW, very few VPN providers actually work with port forwarding, and PIA only has select endpoints that support it.

Yeah, I figured that. My provider has port forwarding but it is extra. How much extra I don't know. Is there anything I can do without needing port forwarding? Change the port rtorrent uses? Networking was never my strong suit.

Link to comment
42 minutes ago, bobbintb said:

Is there anything I can do without needing port forwarding?

With torrents, you really need to be connectible from the outside. Without port forwarding you can't properly seed, and your download speeds will range from abysmal to non-existent.

  • Like 1
Link to comment
On 1/1/2019 at 5:35 PM, jonathanm said:

With torrents, you really need to be connectible from the outside. Without port forwarding you can't properly seed, and your download speeds will range from abysmal to non-existent.

 

I feel like this is a myth that gets touted around a lot. I use TorGuardVPN with this thread's namesake container and there is no port forwarding going on, yet I can get multiple Mb going in both directions without a problem. So I don't think port forwarding/direct connection is as important as it seems.

Link to comment
6 hours ago, deusxanime said:

 

I feel like this is a myth that gets touted around a lot. I use TorGuardVPN with this thread's namesake container and there is no port forwarding going on, yet I can get multiple Mb going in both directions without a problem. So I don't think port forwarding/direct connection is as important as it seems.

Depends on the specific torrent and tracker. Very popular torrents on some public trackers can work ok, because your client can connect to other clients that are actively transmitting data in both directions. If there is nobody you are currently downloading from that needs data you have, you will not be able to seed at all. Responsible torrenting involves allowing others to download from you as well as just downloading from them, and all private trackers that I am aware of will not allow you to participate without seeding and keeping a positive upload ratio.

 

It's definitely not a myth, it's a fact about how the torrent protocol works. Many torrent clients actively seek to prioritize traffic to clients that have healthy connections, so if you aren't connectable, you will have a hard time downloading on many lightly populated swarms.

Link to comment
3 hours ago, jonathanm said:

Depends on the specific torrent and tracker. Very popular torrents on some public trackers can work ok, because your client can connect to other clients that are actively transmitting data in both directions. If there is nobody you are currently downloading from that needs data you have, you will not be able to seed at all. Responsible torrenting involves allowing others to download from you as well as just downloading from them, and all private trackers that I am aware of will not allow you to participate without seeding and keeping a positive upload ratio.

 

It's definitely not a myth, it's a fact about how the torrent protocol works. Many torrent clients actively seek to prioritize traffic to clients that have healthy connections, so if you aren't connectable, you will have a hard time downloading on many lightly populated swarms.

I'm on multiple private trackers and have been able to seed with no problem and keep my ratio quite good. 

Link to comment

REally Happy with the work that has gone into this sdocker container.  

 

I was able to get the Rutorrent standard container working but needed to integrate with my VPN.

I have docker running on ubuntu 18 

VPN provider is Nordvpn 

 

I can get it started / running but cannot access the webui on 9080 or 9443 

 

https://hub.docker.com/r/binhex/arch-rtorrentvpn/

 

Running it like

 

docker run -d     --cap-add=NET_ADMIN     -p 9080:9080     -p 9443:9443     -p 8118:8118     -p 3000:3000     --name=rtorrentvpn     -v /mnt/downloads/:/data     -v /mnt/config:/config     -v /etc/localtime:/etc/localtime:ro     -e VPN_ENABLED=yes     -e VPN_USER=username     -e VPN_PASS=pass     -e VPN_PROV=custom     -e ENABLE_PRIVOXY=yes     -e ENABLE_FLOOD=yes     -e ENABLE_AUTODL_IRSSI=yes     -e LAN_NETWORK=192.168.0.0/16     -e NAME_SERVERS=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     -e DEBUG=false     -e PHP_TZ=America/Toronto    -e UMASK=000     -e PUID=1000     -e PGID=999 binhex/arch-rtorrentvpn
 

I can load the Flood UI 

I think I can access Privoxy (Invalid header received from client. ) port 8118 

 

it seems nginx is not running 

 

It was rightly so with Flood Enabled (D'oh)   

 

with flood no enabled it works. 

 

My bad !! 

 

 

Edited by nikko-wolf
Update
Link to comment

Would it make sense that the rtorrent process seems to be restarting at times?

I see that the proc runningtime is 30m 

 

and had a blip of disconnectivity from the webui in 9080 

 

I am still fighting with sonarr regarding Auto transfering of files 

 

with /mnt/downloads being the  /data dir 

 which gets me /mnt/downloads/incomplete 

 would I be seeing them in /mnt/downloads/complete  when done (so sonarr can find them ?)

 

 

 

 

 

Link to comment

I have fixed the auto transferring with sonarr

 

I had mapped the /mnt/downloads (host) to /dowloads  (in sonarr container) 

it should reallt be /mnt/downloads : /data  

 

Things are working rather nicely  Kudos to the Rutorrwent vpn integration 

 

I struggled with building a nord VPN  container and trying to link rutorrent container too it  (i'll need much more docker experience) 

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