[Support] binhex - rTorrentVPN


Recommended Posts

So I'm not seeing any guides for this.  I've downloaded the container and left everything default except /data I pointed to my /media/downloads folder.

 

I put my VPN information in, select wireguard, then save everything. I then go and run the program (it doesn't) so it creates the directories needed.  Then I place my VPN config file (for wireguard) into the folder.

 

After this I start rtorrent and go to settings. I never seems to want to save any of my settings. There is no "Apply" option just an OK so I select it. Then I go and load a test torrent (Ubuntu iso).  Now at the bottom I see a red stop sign saying my port is blocked. The download starts anyway but stays rather limited of around 1MB/sec.  I also don't recognize the IP i'm looking at so I'm guessing that's my outside IP to the house.  

 

I have ATT and log into the BWG-210 router and go to port forwarding and open the ports 6500-6900. I think it's using port 6881. I assign that port to my tower but ATT's BWG only gives me the option of TDP, UDP, or TDP/UDP.  Is this really causing a problem? I thought an open port was an open port?  When I go back into rtorrent I'm not seeing any changes even though the gateway is showing the port as being open. I tried to change the port within rtorrent but again, nothing ever saves, and this is getting frustrating.  

What's going on and what do I need to do?

Link to comment
4 hours ago, FlyingTexan said:

. I tried to change the port within rtorrent but again, nothing ever saves

see Q1:-https://github.com/binhex/documentation/blob/master/docker/faq/rtorrentvpn.md

 

 

5 hours ago, FlyingTexan said:

log into the BWG-210 router and go to port forwarding and open the ports 6500-6900

see Q15:-  https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to comment

I'm having trouble with something relatively simple that I'd like to incorporate into rtorrent/RuTorrent. I'm running Binhex's rutorrent container on Unraid Docker, and I want the ability to have a change in label / category of the torrent move all the associate files into the related subfolder within my broader Downloads share. I want this to work whether the file is actively seeding, downloading, finished etc. I know qBt does this so I would think rTorrent through a script can accomplish the same task.

I'm relatively new to scripting on rutorrent / docker / unraid so any beginner tips to figure this out would be very much appreciated :)

Link to comment
2021/12/30 23:26:01 [error] 1209#1209: *15045 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.163:9090"

I Keep getting this error and my rtorrent WEBUI keeps timing out especially when something is actively being downloaded or uploaded at higher speeds. even apps like radarr and sonarr have trouble connecting and adding files. CPU usage is never pegged over 3-5%. Whats going on??

 

supervisord.log

 

 

Link to comment

Hi,

 

I'm having some issues trying to set-up the docker without VPN. I have changed the /data folder but, how should i proceed with the other options that refer to the VPN?

 

Other issue I'm having is that rTorrent is not uploading practically anything (including torrents with leechers). I think it is because I need to open some port on my router, but I'm not sure which one is it. I assume it is the listening port that ruTorrent lists on the settings, but should I add anything on the docker config? Or just open it on my router and point it to the unraid server?

 

Thanks in advance

Link to comment

 

On 12/31/2021 at 7:35 AM, slyk said:
2021/12/30 23:26:01 [error] 1209#1209: *15045 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.163:9090"

I Keep getting this error and my rtorrent WEBUI keeps timing out especially when something is actively being downloaded or uploaded at higher speeds. even apps like radarr and sonarr have trouble connecting and adding files. CPU usage is never pegged over 3-5%. Whats going on??

 

supervisord.log 342.28 kB · 0 downloads

 

 

 

have started getting the same error. 

 

[error] 1028#1028: *24559 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.19.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.18:9080"

 

the container failed to stop after this... I managed to stop docker but it failed to start then. I rebooted the server and it hung on shut down. After a hard restart this container will not start. I have tried changing the vpn server and re installing the container no joy atm.  

 

EDIT

 

Randomly started working again this morning. Must have just been a PIA issue. 

supervisord.log

Edited by tazire
Link to comment

I'm not sure what's going wrong with the initialization, but it is not starting and keeps looping.

 

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

2022-01-04 10:58:34.956811 [info] Host is running unRAID
2022-01-04 10:58:34.974090 [info] System information Linux 1636a1458d1a 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-01-04 10:58:34.994086 [info] OS_ARCH defined as 'x86-64'
2022-01-04 10:58:35.013377 [info] PUID defined as '99'
2022-01-04 10:58:35.045986 [info] PGID defined as '100'
2022-01-04 10:58:35.076876 [info] UMASK defined as '000'
2022-01-04 10:58:35.096160 [info] Permissions already set for '/config'
2022-01-04 10:58:35.117162 [info] Deleting files in /tmp (non recursive)...
2022-01-04 10:58:35.139950 [info] VPN_ENABLED defined as 'no'
2022-01-04 10:58:35.157225 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2022-01-04 10:58:35.176995 [info] ENABLE_AUTODL_IRSSI defined as 'no'
2022-01-04 10:58:35.196298 [info] ENABLE_RPC2 defined as 'yes'
2022-01-04 10:58:35.217448 [info] ENABLE_RPC2_AUTH defined as 'yes'
2022-01-04 10:58:35.237541 [info] RPC2_USER defined as 'admin'
2022-01-04 10:58:35.259433 [warn] RPC2_PASS not defined (via -e RPC2_PASS), using randomised password (password stored in '/config/nginx/security/rpc2_pass')
2022-01-04 10:58:35.279405 [info] ENABLE_WEBUI_AUTH defined as 'yes'
2022-01-04 10:58:35.298871 [info] WEBUI_USER defined as 'admin'
2022-01-04 10:58:35.320888 [warn] WEBUI_PASS not defined (via -e WEBUI_PASS), using randomised password (password stored in '/config/nginx/security/webui_pass')
2022-01-04 10:58:38.089460 [info] Starting Supervisor...
2022-01-04 10:58:38.089460 [info] Starting Supervisor...
2022-01-04 10:58:38,293 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2022-01-04 10:58:38,293 INFO Set uid to user 0 succeeded
2022-01-04 10:58:38,295 INFO supervisord started with pid 7
2022-01-04 10:58:39,297 INFO spawned: 'logrotate-script' with pid 121
2022-01-04 10:58:39,298 INFO spawned: 'pyrocore-script' with pid 122
2022-01-04 10:58:39,299 INFO spawned: 'rutorrent-script' with pid 123
2022-01-04 10:58:39,299 INFO spawned: 'shutdown-script' with pid 124
2022-01-04 10:58:39,300 INFO spawned: 'start-script' with pid 125
2022-01-04 10:58:39,301 INFO spawned: 'watchdog-script' with pid 126
2022-01-04 10:58:39,301 INFO reaped unknown pid 8 (exit status 0)
2022-01-04 10:58:39,310 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2022-01-04 10:58:39,310 INFO success: logrotate-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-04 10:58:39,310 INFO success: pyrocore-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-04 10:58:39,310 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-04 10:58:39,310 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-04 10:58:39,310 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-04 10:58:39,310 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-04 10:58:39,310 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 23238435871952 for <Subprocess at 23238435869792 with name start-script in state RUNNING> (stdout)>
2022-01-04 10:58:39,311 DEBG fd 30 closed, stopped monitoring <POutputDispatcher at 23238435871808 for <Subprocess at 23238435869792 with name start-script in state RUNNING> (stderr)>
2022-01-04 10:58:39,311 INFO exited: start-script (exit status 0; expected)
2022-01-04 10:58:39,311 DEBG received SIGCHLD indicating a child quit
2022-01-04 10:58:39,311 DEBG 'watchdog-script' stdout output:
[info] rTorrent config file already exists, skipping copy

2022-01-04 10:58:39,336 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2022-01-04 10:58:39,336 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2022-01-04 10:58:39,337 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2022-01-04 10:58:39,337 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2022-01-04 10:58:39,360 DEBG 'watchdog-script' stdout output:
Script done.

2022-01-04 10:58:39,468 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23238437530880 for <Subprocess at 23238437530208 with name pyrocore-script in state RUNNING> (stdout)>
2022-01-04 10:58:39,468 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23238435870656 for <Subprocess at 23238437530208 with name pyrocore-script in state RUNNING> (stderr)>
2022-01-04 10:58:39,468 INFO exited: pyrocore-script (exit status 0; expected)
2022-01-04 10:58:39,468 DEBG received SIGCHLD indicating a child quit
2022-01-04 10:58:50,407 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...

2022-01-04 10:59:20,430 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2022-01-04 10:59:20,431 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2022-01-04 10:59:20,434 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2022-01-04 10:59:20,437 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2022-01-04 10:59:20,480 DEBG 'watchdog-script' stdout output:
Script done.

2022-01-04 10:59:20,430 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2022-01-04 10:59:20,431 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2022-01-04 10:59:20,434 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2022-01-04 10:59:20,437 DEBG 'watchdog-script' stdout output:
Script started, output log file is '/home/nobody/typescript'.

2022-01-04 10:59:20,480 DEBG 'watchdog-script' stdout output:
Script done.

2022-01-04 10:59:31,589 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...

Link to comment

I'm having trouble running this container with Hashicorp Nomad as the orchestrator. I have given the container `net_admin` privileges, as well as running it globally privileged with `privileged = true`, with both bridge and host networks, but it seems that at some point the init script halts or ends up with a silent error that doesn't display what's wrong. From reading the logs it seems that the rtorrent process doesn't start up, but there seems to be no indication as to why, and that is with `DEBUG=yes` I am using a custom vpn provider, and all the config files including ovpn are working on docker-compose, which I am migrating away from.

 

Are there any other privileges that are needed for the container to work properly? I am currently running `binhex/arch-rtorrentvpn:v3.10-01` which, as mentioned above, works with docker-compose. Also, worth mentioning is that when I set `VPN_ENABLED=no`, then the container seems to start up properly.

 

Here's a hastebin of the container logs: https://www.toptal.com/developers/hastebin/rejecihudu.yaml

And here are the interfaces found in the container:

[root@2fb55f5c7112 /]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0@if2187: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 62:3e:1a:a3:25:3b brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.26.64.95/20 brd 172.26.79.255 scope global eth0
       valid_lft forever preferred_lft forever
3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
    link/none
    inet <>/22 brd <> scope global tun0
       valid_lft forever preferred_lft forever
Edited by 7thSon
Link to comment
On 11/30/2021 at 5:19 PM, casperse said:

Almost ready to give up and move on to another solution but I must admit I have most trust on Binhex and the security built in these dockers...Can anyone give any input on why this isnt working? Cheers

 

 

I really need some help trouble shooting this!

 

1) I got the delugevpn working but I would like to use the rTorrent 🙂

2) I had this working a year ago, but after doing a total re-install I cant get the rTorrent to run? (No VPN or Strict port forwarding)

 

My configuration is as shown below:

image.thumb.png.c65f55a54c066be70a8b7a50cdd24b44.png

 

Log:

image.png.f69dfb7da0a5169ec7d53f33b463209c.png

 

Error log:

1641568550 C Caught exception: 'Error in option file: ~/.rtorrent.rc:61: Bad return code.'.

 

The access rights is fine (even did a chmod 777, just to make sure)

 

 

 

Link to comment
1 hour ago, casperse said:

Error log:

1641568550 C Caught exception: 'Error in option file: ~/.rtorrent.rc:61: Bad return code.'.

can you attach your rtorrent config file, it should be located at /config/rtorrent/config/rtorrent.rc

Link to comment
50 minutes ago, binhex said:

can you attach your rtorrent config file, it should be located at /config/rtorrent/config/rtorrent.rc

Thanks for helping me!

 

I did a remove all docker templates and docker image and did yet another re-install and I also removed the "perms.txt" just to make sure perms where not the problem and I got the UI to start! 🙂

But my speeds are really slow?

 

So I wonder if I am missing any portforwarding?

So far I thought I only needed the wireguard port 51820/UDP?

Should it be the whole range 51820 - 65535 UDP?

Other ports shouldnt be needed when I only want it to use the Wireguard VPN right?

I Also have Strict Port forwarding set to yes...

 

So close now... LOL

 

 

 

 

Link to comment
5 hours ago, binhex said:

can you attach your rtorrent config file, it should be located at /config/rtorrent/config/rtorrent.rc

I actually had the same issue. The issue was that it was trying to make a directory called /data/incomplete. I had changed the /data directory to a different name for my own convenience, but the program was not ready for that. There is no issue if you leave the directory as /data.

Edited by ReDew
Link to comment

I solved my VPN issue above, it was just a permissions issue for the mounted folders.

On another note though; is there any lightweight health check endpoint that can be used to check that the container is working properly? Something like a rest endpoint, or a cli command in the container to check would also be great.

Edited by 7thSon
Link to comment
On 1/7/2022 at 6:47 PM, casperse said:

Thanks for helping me!

 

I did a remove all docker templates and docker image and did yet another re-install and I also removed the "perms.txt" just to make sure perms where not the problem and I got the UI to start! 🙂

But my speeds are really slow?

 

So I wonder if I am missing any portforwarding?

So far I thought I only needed the wireguard port 51820/UDP?

Should it be the whole range 51820 - 65535 UDP?

Other ports shouldnt be needed when I only want it to use the Wireguard VPN right?

I Also have Strict Port forwarding set to yes...

 

So close now... LOL

 

 

 

 

 

Thanks @ReDew that must have ben it! - during re-install I kept it default to /Data no "-" on the incomplete folder like before

 

I have it downloading but its not uploading any data (0) so I am back to ports opening?

How to check if I am connectable to seed?

Running through PIA Wiregurad what ports should I create NAT for?

I am running in "Bridge mode" and not on Proxynet

Link to comment
Quote

How to check if I am connectable to seed?

@casperse There is a section at the bottom of the ui that displays your ip:port with either a green check mark or a red exclamation mark saying the port is open or closed. This will determine your connectability. I found I had to change my settings in the rtorrent.rc file to make them load on boot. The format for identifying the port must be #-# (5678-6789 for example). My vpn (Mullvad) only lets me generate random individual ports to associate with my wireguard key, so my input for the rtorrent.rc file had to be 5678-5678 to limit it to that one port on boot.

Edited by ReDew
Link to comment
On 1/9/2022 at 11:25 PM, ReDew said:

@casperse There is a section at the bottom of the ui that displays your ip:port with either a green check mark or a red exclamation mark saying the port is open or closed. This will determine your connectability. I found I had to change my settings in the rtorrent.rc file to make them load on boot. The format for identifying the port must be #-# (5678-6789 for example). My vpn (Mullvad) only lets me generate random individual ports to associate with my wireguard key, so my input for the rtorrent.rc file had to be 5678-5678 to limit it to that one port on boot.

Thanks! I found this line in the rtorrent.rc file:

 

# Port range to use for listening.
#
#network.port_range.set = 49160-49160

 

So is it enough to just uncomment this line and set it to ex.

network.port_range.set = 58550-58550

Link to comment
8 minutes ago, casperse said:

Thanks! I found this line in the rtorrent.rc file:

 

# Port range to use for listening.
#
#network.port_range.set = 49160-49160

 

So is it enough to just uncomment this line and set it to ex.

network.port_range.set = 58550-58550

Yeah.

Link to comment

iam using this container for over a year and it works without any problems. a few weeks ago i noticed that autdl-irssi kind of dies after 24/h. My ISP gives me a new IP-Address every 24/h and somehow irssi cant survive this process (I guess). So I have to restart the container every day which is very annoying. Iam using the latest image.

 

Is there a bug in irssi or did something change in the image which produces this bug? How can i debug this? Is there a irssi log or something?

Link to comment

I use this container for some time now and it always worked without any problems.

However, lately some torrents are giving me trouble, because I can't download them.

 

When I add the torrent (manually or via RSS) its status is "Queue" and I can't force recheck or tell it to start.

However, if I add another torrent file (a new one, that I never downloaded before), it gets added and start downloading the files.

Usually this happens with some (but not all) files that gets loaded using RSS, specially if the previous release got deleted.

 

When I try to change the location of file (clicking "Save to..."), I get the following error

XMLRPC Error: Duplicate filename found. [getsavepath]

 

I tried to google this error, but got no results...

 

Any help is appreciated, thanks in advance.

Link to comment
4 minutes ago, 3dee said:

Hey guys,

 

rTorrent is filling up my docker.img since 1-2 days. I've been using this container for almost a year now and never ran into this issue before. Docker.img is set to 30GB.

 

grafik.png.2bc1160e7de69e2027f7ef74e777ece6.png

 

557045203_Screenshot2022-01-19at12-01-33ServerPCDocker.thumb.png.09e671f6f94ab708acd9b949c3038a0f.png

 

 

I recently reached 1000 Torrents in rTorrent, not sure if that could be the reason maybe? Any ideas for that?

 

I just deleted my old Docker.img and set up the containers again but rTorrent just filled it all up again.

check incomplete and completed definitions in rutorrent and your rtorrent.rc file, they should be targetting /data/ (assuming you are using the default volume names).

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

check incomplete and completed definitions in rutorrent and your rtorrent.rc file, they should be targetting /data/ (assuming you are using the default volume names).

 

Thanks for reply, the reason was a torrent with error "Low disk space". I deleted it and all the docker.img usage disappeared. I guess due to my pre reservation of disk space setting.

Link to comment
  • 2 weeks later...

Copying rtorrent session folder was sufficient.

 

However, I have mapped all my shares individually. 

/download/movies /  ->  /mnt/user/movies/downloads/
/download/series/  ->  /mnt/user/series/

etc

 

When I press the "add torrent" button the default directory is /data/incomplete/. 

I have chosen the "Default directory for downloads" to be "/download/"

 

How can I change this?

Link to comment
On 1/4/2022 at 5:27 PM, ReDew said:

I'm not sure what's going wrong with the initialization, but it is not starting and keeps looping.

 

.....

 

2022-01-04 10:59:31,589 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...

 

I am currently having a very similar issue. The container works on first run after barebones install & basic VPN config, but any subsequent restart of the container or the Unraid host causes the startup loop that you posted. 

 

/mnt/user/Media is mapped to /data in the container, permissions look OK, I'm a bit stuck now and would appreciate any advice. Thanks.

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.