[Support] binhex - rTorrentVPN

pantoner · September 28, 2022

I've been having issues with this container causing a general protection fault within unraid. This causes unraid to freeze and I'm unable to access the GUI or restart any images. I don't see anything weird in the logs when this happens. Can anyone assist in helping me track this down?

Sep 27 20:31:35 unraid kernel: traps: lsof[6612] general protection fault ip:14642ad574ee sp:a608de866260c89e error:0 in libc-2.36.so[14642ad3f000+16b000]
Sep 27 20:33:28 unraid kernel: traps: lsof[14737] general protection fault ip:1519959054ee sp:658ac0c0c6e69be5 error:0 in libc-2.36.so[1519958ed000+16b000]

EDIT: I resolved that issue by downgrading to 6.10.3 but still having issues with this container killing my docker instance when downloading torrents.

EDIT 2: Not sure why but the container was having issues with a large amount of downloading torrents. I've reached 20+ with no issues. I had problems when radarr send about 80 at once.

unraid-diagnostics-20220927-2044.zip

Edited October 5, 2022 by pantoner

Distinguished · October 12, 2022

On 9/28/2022 at 2:46 AM, pantoner said:

I've been having issues with this container causing a general protection fault within unraid. This causes unraid to freeze and I'm unable to access the GUI or restart any images. I don't see anything weird in the logs when this happens. Can anyone assist in helping me track this down?

Sep 27 20:31:35 unraid kernel: traps: lsof[6612] general protection fault ip:14642ad574ee sp:a608de866260c89e error:0 in libc-2.36.so[14642ad3f000+16b000]
Sep 27 20:33:28 unraid kernel: traps: lsof[14737] general protection fault ip:1519959054ee sp:658ac0c0c6e69be5 error:0 in libc-2.36.so[1519958ed000+16b000]

EDIT: I resolved that issue by downgrading to 6.10.3 but still having issues with this container killing my docker instance when downloading torrents.

EDIT 2: Not sure why but the container was having issues with a large amount of downloading torrents. I've reached 20+ with no issues. I had problems when radarr send about 80 at once.

unraid-diagnostics-20220927-2044.zip 206.4 kB · 0 downloads

I am also having this issue, still on 6.9.2. I thought my server memory modules were going bad, happy to see this is not just me...

Wirby · November 2, 2022

Hello,

I'm currently using this container with a PIA subscription, and I'm thinking to move to Proton VPN. I can't find the required options to set to use a custom VPN connection (VPN_PROV=custom) using Wireguard (VPN_CLIENT=wireguard), could someone please give me some details ?

Thanks in advance.

Regards

n90r · November 12, 2022

On 11/12/2021 at 12:35 AM, RoachBot said:

I'm having an issue where the binhex-rtorrentvpn container fails to restart and will not respond to STOP or KILL. It even blocks stopping the Unraid array or restarting the server gracefully. This happens about every other month and I can't figure out why.

I usually find out because the GUI is not responding.

2021-11-11 13:15:41,950 DEBG 'rutorrent-script' stderr output:
2021/11/11 13:15:41 [error] 4896#4896: *2477 upstream timed out (110: Unknown error) while reading response header from upstream, client: 10.10.20.127, server: localhost, request: "GET /php/getplugins.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "10.10.20.100:9181", referrer: "http://10.10.20.100:9181/"


2021-11-11 13:16:53,790 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '30168'

2021-11-11 13:17:40,840 WARN received SIGTERM indicating exit request
2021-11-11 13:17:40,841 DEBG killing watchdog-script (pid 222) with signal SIGTERM
2021-11-11 13:17:40,841 INFO waiting for logrotate-script, rutorrent-script, shutdown-script, start-script, watchdog-script to die
2021-11-11 13:17:41,842 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 22489151549104 for <Subprocess at 22489151546752 with name watchdog-script in state STOPPING> (stdout)>
2021-11-11 13:17:41,842 DEBG fd 35 closed, stopped monitoring <POutputDispatcher at 22489151549152 for <Subprocess at 22489151546752 with name watchdog-script in state STOPPING> (stderr)>
2021-11-11 13:17:41,843 INFO stopped: watchdog-script (terminated by SIGTERM)
2021-11-11 13:17:41,843 DEBG received SIGCHLD indicating a child quit
2021-11-11 13:17:41,843 DEBG killing start-script (pid 218) with signal SIGTERM
2021-11-11 13:17:42,845 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 22489151548720 for <Subprocess at 22489151546560 with name start-script in state STOPPING> (stdout)>
2021-11-11 13:17:42,845 DEBG fd 30 closed, stopped monitoring <POutputDispatcher at 22489151548576 for <Subprocess at 22489151546560 with name start-script in state STOPPING> (stderr)>
2021-11-11 13:17:42,845 INFO stopped: start-script (terminated by SIGTERM)
2021-11-11 13:17:42,845 DEBG received SIGCHLD indicating a child quit
2021-11-11 13:17:42,846 DEBG killing shutdown-script (pid 217) with signal SIGTERM
2021-11-11 13:17:42,846 DEBG 'shutdown-script' stdout output:
[info] Initialising shutdown of process(es) 'nginx: master process,^/usr/bin/rtorrent' ...

2021-11-11 13:17:42,910 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22489151547808 for <Subprocess at 22489151546176 with name rutorrent-script in state RUNNING> (stdout)>
2021-11-11 13:17:42,910 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 22489151547856 for <Subprocess at 22489151546176 with name rutorrent-script in state RUNNING> (stderr)>
2021-11-11 13:17:42,910 INFO exited: rutorrent-script (exit status 0; expected)
2021-11-11 13:17:42,910 DEBG received SIGCHLD indicating a child quit
2021-11-11 13:17:43,912 INFO waiting for logrotate-script, shutdown-script to die
2021-11-11 13:17:46,915 INFO waiting for logrotate-script, shutdown-script to die
2021-11-11 13:17:49,918 INFO waiting for logrotate-script, shutdown-script to die

@binhex - I have the same issue. It's happening everyday. I have around 2500 torrents and I have plenty of CPU and RAM. Docker is running on SSD - I am not sure what seems to be the problem.

2022-11-11 20:18:50,986 WARN received SIGTERM indicating exit request
2022-11-11 20:18:51,000 DEBG killing watchdog-script (pid 193) with signal SIGTERM
2022-11-11 20:18:51,001 INFO waiting for logrotate-script, rutorrent-script, shutdown-script, start-script, watchdog-script to die
2022-11-11 20:18:51,745 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 22893222987616 for <Subprocess at 22893222987568 with name watchdog-script in state STOPPING> (stdout)>
2022-11-11 20:18:51,745 DEBG fd 35 closed, stopped monitoring <POutputDispatcher at 22893223035088 for <Subprocess at 22893222987568 with name watchdog-script in state STOPPING> (stderr)>
2022-11-11 20:18:51,745 INFO stopped: watchdog-script (terminated by SIGTERM)
2022-11-11 20:18:51,746 DEBG received SIGCHLD indicating a child quit
2022-11-11 20:18:51,746 DEBG killing start-script (pid 192) with signal SIGTERM
2022-11-11 20:18:52,746 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 22893222989536 for <Subprocess at 22893222987376 with name start-script in state STOPPING> (stdout)>
2022-11-11 20:18:52,747 DEBG fd 30 closed, stopped monitoring <POutputDispatcher at 22893222989392 for <Subprocess at 22893222987376 with name start-script in state STOPPING> (stderr)>
2022-11-11 20:18:52,747 INFO stopped: start-script (terminated by SIGTERM)
2022-11-11 20:18:52,747 DEBG received SIGCHLD indicating a child quit
2022-11-11 20:18:52,747 DEBG killing shutdown-script (pid 188) with signal SIGTERM
2022-11-11 20:18:52,747 DEBG 'shutdown-script' stdout output:
[info] Initialising shutdown of process(es) 'nginx: master process,^/usr/bin/rtorrent' ...

2022-11-11 20:18:53,565 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22893222988624 for <Subprocess at 22893222986992 with name rutorrent-script in state RUNNING> (stdout)>
2022-11-11 20:18:53,565 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 22893222988672 for <Subprocess at 22893222986992 with name rutorrent-script in state RUNNING> (stderr)>
2022-11-11 20:18:53,565 INFO exited: rutorrent-script (exit status 0; expected)
2022-11-11 20:18:53,565 DEBG received SIGCHLD indicating a child quit
2022-11-11 20:18:54,566 INFO waiting for logrotate-script, shutdown-script to die
2022-11-11 20:18:57,570 INFO waiting for logrotate-script, shutdown-script to die
2022-11-11 20:19:00,572 INFO waiting for logrotate-script, shutdown-script to die

shwa87 · November 25, 2022

I can't find a definitive answer on this - is the flood UI no longer available in this container? I apologize if its been answered somewhere.

binhex · November 25, 2022

I can't find a definitive answer on this - is the flood UI no longer available in this container? I apologize if its been answered somewhere.

Nope it's not

Sent from my 22021211RG using Tapatalk

shwa87 · December 4, 2022

On 12/21/2018 at 8:27 AM, tomllic said:

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

did you ever figure this out? I'm running into this now 4 years later.

Woiiwod · December 10, 2022

Hello everyone,

Borked my Rocky Linux 8 installation. So i installed Rocky Linux 9 and got to spin everything up again but my rtorrent container does not want to work.

I've made sure that iptable mangle is on and that all directories are accessible.

What I can see in top is that rtorrent fills the memory runs in cycles up to 100% then back to 0%. The process also at times uses 90% of the CPU, making even bash sluggish.

I've tried everything I can think of. The log is here:

https://pastebin.com/6gc8Lr1N

Thanks.

binhex · December 10, 2022

Hello everyone,

Borked my Rocky Linux 8 installation. So i installed Rocky Linux 9 and got to spin everything up again but my rtorrent container does not want to work.
I've made sure that iptable mangle is on and that all directories are accessible.
What I can see in top is that rtorrent fills the memory runs in cycles up to 100% then back to 0%. The process also at times uses 90% of the CPU, making even bash sluggish.

I've tried everything I can think of. The log is here:
https://pastebin.com/6gc8Lr1N

Thanks.

I would suspect a bad config file, rename rtorrent.rc file to something else then restart the container, this will then create a default config file.

Sent from my 22021211RG using Tapatalk

Woiiwod · December 11, 2022

On 12/10/2022 at 3:10 PM, binhex said:

I would suspect a bad config file, rename rtorrent.rc file to something else then restart the container, this will then create a default config file.

I also assumed this. So I have already tried to semove the rtorrend.rc file. I have also several times completely whiped the /data directory.

I don't know what to do after giving it a completely blank slate. My docker compose file has worked before, it's just the Rocky Linux version that has changed.

Woiiwod · December 18, 2022

Hello again,

Accidentally left the container running for a couple of days during the week. Completely borked the linux installation, so I've tried again on a fresh install of Rocky linux 9.

A friend said that maybe RL installing podman was the issue. So I made sure to uninstall that and dependencies, then installing docker using their own repo.

Unfortunately I've gotten the same results where the container cycles between using 100% and 0% of memory and CPU.

I've tried to wipe all files, both /config and /data.

I've tried to run it both from my docker compose file, but also as a standalone container from the command line.

I don't think there is much difference, but the new logs are here: https://pastebin.com/it2F6euC

Any input would be helpful. What am I missing here?

Woiiwod · December 19, 2022

I moved over all of my files regarding container configs etc. to my EndevourOS desktop.

I had to remove the rtorrent.rc file, but after that everything spun up and started working.

Docker compose versions are the same and docker versions are one off between the machines.

Running :latest on both.

Is there any more kernel plugin that is required? I saw that when booting up on EndeavorOS that the list is a bit longer compared to my paste above:

2022-12-19 20:09:21,563 DEBG 'start-script' stdout output:
iptable_mangle         16384  0
ip_tables              36864  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               57344  12 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_nat,ip6_tables,ip_tables,iptable_nat,xt_MASQUERADE,iptable_mangle,xt_mark

Thanks.

Green Dragon · December 21, 2022

In rutorrent, I have ratio group actions set to continue seeding regardless of the ratio (I never want them to stop seeding). I do have a ratio group action configured to change the channel to 'delete ok' once the configured seed TIME is met (as you would expect, different per tracker). I do this so that when the time comes for me to manually remove torrents I'll know which have met the trackers seed requirements and can be deleted.

Nonetheless, once a seeded torrent exceeds a 1:1 upload ratio its marked as finished and seeding stops. I must then go in and manually start them. As configured, the channel does change to 'delete ok' once the configured seed TIME is reached so I know that the ratio rules are otherwise working. In all cases, if the ratio has not yet reached 1:1 then the torrent continues to seed.

I may have narrowed this down to the watchdog script restarting and re-initializing plugins when the VPN IP address expires or otherwise no longer works (network failure?). I think that somewhere in this process any torrents with greater that 1:1 ratio are changed to 'finished' status. I have tried enabling the default ratio group in rtorrent.rc but this does not help.

Anyone else having a similar experience?

EDIT: SOLVED!

After weeks of researching and testing this (and no response here) I seem to have found the reason for the problem! The watchdog script restarts rtorrent whenever there is a problem with the vpn (as indicated above). Part of this restart reinitializes the plugins with the following line in rtorrent.rc and /home/nobody/initplugins.sh:

execute = {/bin/bash,-c,/usr/bin/sleep 10s && /usr/bin/php /usr/share/webapps/rutorrent/php/initplugins.php $WEBUI_USER &}

This 'reset' appears to have the effect of causing any torrents with a ratio of 1:1 or better to stop seeding regardless of configuration. The remarks in the files indicate that it is there so that the plugins 'rss' and 'scheduler' will work properly. I do not use these plugins so I disabled them and commented out the line in both files. So far (48 hours) I have not seen a problem and my initial problem is GONE!

This is a great docker and i sincerely hope this saves someone else the frustration I experienced.

gd

Edited December 29, 2022 by Green Dragon
solved!

anylettuce · December 25, 2022

bit of a odd unusual question. I have setup other dockers with multiple instances and it works. What do I need to do to get 2 rutorrents running?

Halvliter · December 28, 2022

Unraid Version 6.9.2 2021-04-07

binhex-rtorrentvpn - latest version

VPN: Mullvad

I have been running rtorrent with this configuration for 6 months without hiccups, but today all my torrents say:

Quote

Tracker: [Couldn't resolve host name]

I have tried rebooting the docker several times, but no luck. What can I do now?

EDIT:

Tried a reboot of the server, and now the logs show this:

Spoiler

OS_ARCH=x86-64
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/nobody/bin
PGID=100
PHP_TZ=UTC
PIPESTATUS=([0]="0")
PPID=7
PS4='+ '
PUID=99
PWD=/
RPC2_PASS=Geirolav69
RPC2_USER=admin
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
STRICT_PORT_FORWARD=yes
SUPERVISOR_ENABLED=1
SUPERVISOR_GROUP_NAME=start-script
SUPERVISOR_PROCESS_NAME=start-script
TERM=xterm
TZ=Europe/Berlin
UID=0

0
VPN_CLIENT=wireguard
VPN_CONFIG=/config/wireguard/wg0.conf
VPN_DEVICE_TYPE=wg0
VPN_ENABLED=yes
VPN_INPUT_PORTS=
VPN_OPTIONS=
VPN_OUTPUT_PORTS=
VPN_PASS='vpn password'
VPN_PROV=custom
VPN_REMOTE_PORT=51820
VPN_REMOTE_PROTOCOL=udp
VPN_REMOTE_SERVER=185.120.144.98
VPN_USER='vpn username'
WEBUI_PASS=Geirolav69
WEBUI_USER=admin
_='[debug] Environment variables defined as follows'
[debug] Directory listing of files in /config/wireguard/ as follows

2022-12-28 16:24:33,846 DEBG 'watchdog-script' stdout output:
[info] rTorrent config file already exists, skipping copy

2022-12-28 16:24:33,853 DEBG 'start-script' stdout output:
total 4
drwxrwxr-x 1 nobody users 16 Dec 28 09:35 .
drwxrwxr-x 1 nobody users 376 Dec 28 09:35 ..
-rwxrwxr-x 1 nobody users 303 Dec 28 09:35 wg0.conf

2022-12-28 16:24:33,853 DEBG 'start-script' stdout output:
[debug] Contents of WireGuard config file '/config/wireguard/wg0.conf' as follows...

2022-12-28 16:24:33,854 DEBG 'start-script' stdout output:
[Interface]
PostUp = '/root/wireguardup.sh'
PostDown = '/root/wireguarddown.sh'
PrivateKey = 0C+6pt2Wua+aqFlSxvRVxDMqtWEzhijOwqGBgr+IO3M=
Address = 10.68.0.247/32
DNS = 193.138.218.74

[Peer]
PublicKey = fdEVvu79A9F/VcI0sDK+7RNWBt1Yg2OYXo7O+fliKF8=
AllowedIPs = 0.0.0.0/0
Endpoint = 185.120.144.98:51820
2022-12-28 16:24:33,857 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2022-12-28 16:24:33,860 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2022-12-28 16:24:33,862 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2022-12-28 16:24:33,865 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2022-12-28 16:24:33,868 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2022-12-28 16:24:33,871 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2022-12-28 16:24:33,875 DEBG 'start-script' stdout output:
185.120.144.98

2022-12-28 16:24:33,885 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2022-12-28 16:24:33,886 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.10.28-Unraid

2022-12-28 16:24:33,886 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2022-12-28 16:24:33,887 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2022-12-28 16:24:33,888 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'
[debug] Show name servers defined for container

2022-12-28 16:24:33,888 DEBG 'start-script' stdout output:
nameserver 84.200.69.80
nameserver 37.235.1.174
nameserver 1.1.1.1
nameserver 37.235.1.177
nameserver 84.200.70.40
nameserver 1.0.0.1

2022-12-28 16:24:33,888 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint 185.120.144.98

2022-12-28 16:24:34,200 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22778927361760 for <Subprocess at 22778927361088 with name pyrocore-script in state RUNNING> (stdout)>
2022-12-28 16:24:34,200 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22778925787552 for <Subprocess at 22778927361088 with name pyrocore-script in state RUNNING> (stderr)>
2022-12-28 16:24:34,201 INFO exited: pyrocore-script (exit status 0; expected)
2022-12-28 16:24:34,201 DEBG received SIGCHLD indicating a child quit
2022-12-28 16:25:04,040 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 57916
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; 185.120.144.98. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
. 3303 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022122800 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 115 msec
;; SERVER: 84.200.69.80
;; WHEN: Wed Dec 28 16:25:03 2022
;; MSG SIZE rcvd: 107

2022-12-28 16:25:04,040 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2022-12-28 16:25:04,041 DEBG 'start-script' stdout output:
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.17.0.2 eceba8dcdcad

2022-12-28 16:25:04,066 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2022-12-28 16:25:04,071 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2022-12-28 16:25:04,075 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.2

2022-12-28 16:25:04,079 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2022-12-28 16:25:04,088 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2022-12-28 16:25:04,091 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2022-12-28 16:25:04,092 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2022-12-28 16:25:04,094 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
192.168.1.0/24 via 172.17.0.1 dev eth0

2022-12-28 16:25:04,094 DEBG 'start-script' stdout output:
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.2
local 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2
--------------------
[debug] Modules currently loaded for kernel

2022-12-28 16:25:04,097 DEBG 'start-script' stdout output:
Module Size Used by
xt_nat 16384 5
xt_tcpudp 16384 15
nvidia_uvm 1105920 0
veth 24576 0
xt_conntrack 16384 2
nf_conntrack_netlink 45056 0
nfnetlink 16384 2 nf_conntrack_netlink
xt_addrtype 16384 2
br_netfilter 24576 0
xfs 671744 2
md_mod 45056 2
nvidia_drm 49152 0
nvidia_modeset 1175552 1 nvidia_drm
drm_kms_helper 163840 1 nvidia_drm
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
nvidia 35172352 2 nvidia_uvm,nvidia_modeset
drm 356352 4 drm_kms_helper,nvidia,nvidia_drm
backlight 16384 1 drm
agpgart 32768 1 drm
iptable_nat 16384 1
xt_MASQUERADE 16384 8
nf_nat 40960 3 xt_nat,iptable_nat,xt_MASQUERADE
nf_conntrack 110592 5 xt_conntrack,nf_nat,xt_nat,nf_conntrack_netlink,xt_MASQUERADE
nf_defrag_ipv6 16384 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
wireguard 81920 0
curve25519_x86_64 32768 1 wireguard
libcurve25519_generic 49152 2 curve25519_x86_64,wireguard
libchacha20poly1305 16384 1 wireguard
chacha_x86_64 28672 1 libchacha20poly1305
poly1305_x86_64 28672 1 libchacha20poly1305
ip6_udp_tunnel 16384 1 wireguard
udp_tunnel 20480 1 wireguard
libblake2s 16384 1 wireguard
blake2s_x86_64 20480 1 libblake2s
libblake2s_generic 20480 1 blake2s_x86_64
libchacha 16384 1 chacha_x86_64
ip6table_filter 16384 1
ip6_tables 28672 1 ip6table_filter
iptable_filter 16384 1
ip_tables 28672 2 iptable_filter,iptable_nat
x_tables 28672 9 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_nat,ip6_tables,ip_tables,xt_MASQUERADE
bonding 114688 0
sb_edac 24576 0
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
coretemp 16384 0
crct10dif_pclmul 16384 1
crc32_pclmul 16384 0
crc32c_intel 24576 2
ghash_clmulni_intel 16384 0
aesni_intel 364544 0
crypto_simd 16384 1 aesni_intel
cryptd 16384 2 crypto_simd,ghash_clmulni_intel
isci 102400 0
glue_helper 16384 1 aesni_intel
libsas 73728 1 isci
rapl 16384 0
i2c_i801 24576 0
scsi_transport_sas 32768 2 isci,libsas
intel_cstate 16384 0
i2c_smbus 16384 1 i2c_i801
wmi_bmof 16384 0
i2c_core 45056 5 drm_kms_helper,nvidia,i2c_smbus,i2c_i801,drm
e1000e 180224 0
wmi 24576 1 wmi_bmof
intel_uncore 131072 0
ahci 40960 3
libahci 28672 1 ahci
button 16384 0

2022-12-28 16:25:04,169 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2022-12-28 16:25:04,171 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 185.120.144.98/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 9443 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 185.120.144.98/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 9443 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT

2022-12-28 16:25:04,172 DEBG 'start-script' stdout output:
--------------------

2022-12-28 16:25:04,175 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2022-12-28 16:25:04,188 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-12-28 16:25:04,198 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-12-28 16:25:04,200 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-12-28 16:25:04,217 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.68.0.247/32 dev wg0

2022-12-28 16:25:04,225 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2022-12-28 16:25:04,236 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2022-12-28 16:25:04,257 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2022-12-28 16:25:04,258 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2022-12-28 16:25:04,259 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2022-12-28 16:25:04,260 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2022-12-28 16:25:04,264 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2022-12-28 16:25:04,267 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2022-12-28 16:25:04,280 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2022-12-28 16:25:04,284 DEBG 'start-script' stdout output:
[debug] Waiting for valid local and gateway IP addresses from tunnel...

2022-12-28 16:25:05,301 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.68.0.247'

2022-12-28 16:25:05,302 DEBG 'start-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-12-28 16:25:05,403 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-12-28 16:26:35,397 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

2022-12-28 16:26:35,501 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

The ERROR-message is this:

Quote

insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2022-12-28 16:24:33,888 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'
[debug] Show name servers defined for container

What can cause this to suddenly happen ? And more importantly, how to fix it ?

EDIT: SOLVED!

I generated a new .conf-file from Mullvad, and that solved it!

supervisord.log

Edited December 29, 2022 by Halvliter
upload new file

fonzie · December 28, 2022

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?

Capronicus · December 28, 2022

4 hours ago, 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?

Running into this issue as well, worked fine for months but suddenly torrents barely download if at all, will update here should I find something.

doubleopinter · December 30, 2022

On 12/28/2022 at 5:37 AM, Halvliter said:

Unraid Version 6.9.2 2021-04-07

binhex-rtorrentvpn - latest version

VPN: Mullvad

I have been running rtorrent with this configuration for 6 months without hiccups, but today all my torrents say:

Funny you had this happen as I had the exact same issue. Turns out Mullvad actually had a bunch of server changes on Dec 28th. One of mine went offline as well and I had the exact same issue.

doubleopinter · December 30, 2022

For all who are running this as a container via docker, are you just pulling from docker hub or are you building it locally from source? The docker hub version is pretty old by now.

deusxanime · December 31, 2022

On 12/28/2022 at 10: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?

I've kind of seen similar things. I've been using this rTorrent container for a while (at least a couple years, probably more) with TorGuard VPN and it worked great up until recently. The past few months or so it just kind of stopped working well. I use Medusa and Radarr to grab stuff, but downloads have really fallen off. It takes a day or two sometimes for the magnets sent over from Medusa/Radarr to rTorrent to resolve into actual files (sometimes they never do even) and then it is a crapshoot whether the thing will actually download or not.

I have to frequently manually go in and grab .torrent files, generally from rar bg, to catch up and when I load them in to rTorrent it doesn't seem to really work with the .torrent files at all, they just spin and never download or connect to the tracker (which may be due to the only tracker really being in there is rar bg). But I can load the same .torrent files in to my uTorrent v2.2.1 which runs on a Windows 10 VM with the TorGuard client on it, and things work fine there.

I'm not really sure if the issue is rTorrent the program, the tracker(s), VPN, protocol, or something specific to the container, so it is hard to pinpoint where the problem lies.

BlackRoc · January 2, 2023

I've been using this sin about 2015. no problem. in the last week I've not been able to get stuff automatically. I started looking at the logs of the apps that weren't acting right, mainly the -arrs, Radarr, and Sonarr. I noticed that they were complaining about Privoxy. I've been using this version of rTorrent to use the privoxy through it. I turned off 'use proxy' in Radarr and Sonarr and now they are working as expected.

Not sure how binhex or whoever combined them but that needs to be looked into.

TrCl · January 8, 2023

Hi @binhex! Are you planning to update the container to rutorrent 4.0 that was released last week? Thanks for all your hard work

ryry · January 14, 2023

I took a look through the pages (w/search) and didn't find anyone else who has this issue. Is there something I can add to the "edit" page to resolve this? Somethign to set the local mtu setting to 1570 to match potentially?

log output from container:

2023-01-13 18:51:27,188 DEBG 'start-script' stdout output:
2023-01-13 18:51:27 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1569', remote='link-mtu 1570'
2023-01-13 18:51:27 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'

It looks like the sort of solution may be discussed here but I don't know how to set it up in unraid.

https://serverfault.com/questions/957485/how-can-i-fix-link-mtu-and-tun-mtu-are-used-inconsistently-warnings-in-openvpn

Edited January 14, 2023 by ryry

uraid · January 14, 2023

On 12/30/2022 at 4:48 AM, doubleopinter said:

For all who are running this as a container via docker, are you just pulling from docker hub or are you building it locally from source? The docker hub version is pretty old by now.

Just built locally from source to get new rutorrent v4.0 and works great.
Had to replace the `root/install.sh` file line 102 with this one (to get around `git://` deprecation) https://github.com/pyroscope/pyrocore/pull/117/:

git clone -b update-to-head-patch "https://github.com/stevezau/pyrocore.git" "/opt/pyrocore" && cd "/opt/pyrocore"

-------------------------------------------------------------------------------------------------------------------

EDIT: If someone encounters an error with the `autodl-irssi` plugin:

autodl-irssi: __init2: ex: Exception info: No content elem with id autodl-prefs-contents-upload

Change the code inside the container in the folder `/usr/share/webapps/rutorrent/plugins/autodl-irssi/` to this pull request:

https://github.com/autodl-community/autodl-rutorrent/pull/58

-------------------------------------------------------------------------------------------------------------------

EDIT2: If you encounter an error with the `throttle` plugin like so:

throttle: Plugin failed to start.

It's because of this commit: https://github.com/Novik/ruTorrent/commit/06222a00375bdd0f1f1b5b58bda29e7025316428

It means the first part of the commit (editing `/usr/share/webapps/rutorrent/conf/config.php`) wasn't applied.

Simply add the line:

$throttleMaxSpeed = 327625*1024;

to your `/usr/share/webapps/rutorrent/conf/config.php` file and enjoy!

Edited January 14, 2023 by uraid

Johnster · January 18, 2023

On 1/9/2023 at 12:36 AM, TrCl said:

Hi @binhex! Are you planning to update the container to rutorrent 4.0 that was released last week? Thanks for all your hard work

Also interested.

[Support] binhex - rTorrentVPN

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

binhex

Beta

binhex

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment