Jump to content
binhex

[Support] binhex - rTorrentVPN

1512 posts in this topic Last Reply

Recommended Posts

Posted (edited)
7 minutes ago, binhex said:

i would say a stable maximum will be something within the boundaries of your hardware

Sorry if it was ambiguous but my question was actually how much torrents one can have in ruTorrent with your 512MB PHP memory setting without getting any major issues. With the default 128MB it's usually around 4000 torrents. I have been able to find only a handful of posts which say increasing PHP memory can make ruTorrent stable with 4k+ torrents but nothing a little more specific. I do know that rTorrent can work even with 20k torrents but ruTorrent is the limiting factor.

So I'm just searching for someone who can say e.g. "I am using rTorrentVPN with 9000 torrents without any major issue, just a little bit laggy". I'm not asking "what's the perfect PHP memory size setting". Just want to know how much I can push rTorrentVPN with your out of the box modified settings.

Edited by Paradido

Share this post


Link to post
Just now, Paradido said:

Sorry if it was ambiguous but my question was actually how much torrents one can have in ruTorrent with your 512MB PHP memory setting without getting any major issues. With the default 128MB it's usually around 4000 torrents. I could find only a handful of posts which say increasing PHP memory can make ruTorrent stable with 4k+ but nothing specific.

So I'm just searching for someone who can say e.g. "I am using rTorrentVPN with 9000 torrents without any major issue, just a little bit laggy".

ahh ok, i certainly cant comment on that im afraid as i tend to have a very low number of active torrents, myabe somebody else will chip in, failing that you could always ask on the rtorrent github repo as an 'issue' there might be some way of calculating it perhaps.

Share this post


Link to post

I can never get past 200 before everything stops but I feel like it's an issue with my hardware, I just haven't identified what yet.

Share this post


Link to post
Posted (edited)

How do I get Flood frontend working?

I set ENABLE_FLOOD to yes in docker settings.

Some thing about preventing rutorrent from starting since Flood is enabled in log. Docker start without any problem.

No webinterface at all at port 9080 anylonger. Am I doing this wrong?

 

Edit:

Ok changed to "no" and now Im not even get rutorrent interface back.

Have restarted docker several times :(

NO idea what could have been messed up by just changing the variable from no to yes and then back to no

Edited by Johan76
Stopped working at all

Share this post


Link to post
11 hours ago, binhex said:

sounds good to me, tbh i am no expert when it comes to the details of rtorrent config, the currently bundled rtorrent.rc is a carbon copy taken from the github repo with a few tweaks to enable dht etc, so its just the default config 

 

i can change this to what you are suggesting so that new users will pick up the change, im being lazy here and not looking this up, just want to confirm the above would mean it still could fallback to plaintext if required, right?, i dont want new users to start complaining that speeds are low due to not being able to connect to all peers.

 

I think so. Have a look at the documentation bellow:

Quote

encryption = option,...

Set how rtorrent should deal with encrypted Bittorrent connections. By default, encryption is disabled, equivalent to specifying the option none. Alternatively, any number of the following options may be specified:

allow_incoming (allow incoming encrypted connections), try_outgoing (use encryption for outgoing connections), require (disable unencrypted handshakes), require_RC4 (also disable plaintext transmission after the initial encrypted handshake), enable_retry (if the initial outgoing connection fails, retry with encryption turned on if it was off or off if it was on), prefer_plaintext (choose plaintext when peer offers a choice between plaintext transmission and RC4 encryption, otherwise RC4 will be used)

enable_retry will turn off encryption in the second case.

 

So basically the difference is that 1) Tries plain text first and then retry with encryption. If client can do both it will prefer plaintext 2) Tries encryption first and then retry plain text. If client can do both it will prefer encryption.

 

Both strategies, in theory, will allow the user to connect with any kind of peer.

 

Effects on speed are somewhat hard to predict. All things being equal, plaintext is probably faster. However, if the ISP is traffic shaping, encryption will probably boost the speeds. 

 

Maybe go for 1 when VPN is enabled and 2 otherwise?

Share this post


Link to post
Posted (edited)
6 hours ago, Johan76 said:

How do I get Flood frontend working?

I set ENABLE_FLOOD to yes in docker settings.

Some thing about preventing rutorrent from starting since Flood is enabled in log. Docker start without any problem.

No webinterface at all at port 9080 anylonger. Am I doing this wrong?

 

Edit:

Ok changed to "no" and now Im not even get rutorrent interface back.

Have restarted docker several times :(

NO idea what could have been messed up by just changing the variable from no to yes and then back to no

Flood listens in port 3000.

Rutorrent listens in port 9080 and 9443 (Https).

If you want both you can set ENABLE_FLOOD to BOTH. 

Be warned that, while it looks great, flood uses a lot of memory and is not as feature complete as rutorrent. With 1k torrents Flood's Node.js process is using quite a bit of memory, plus the UI lags so much that it's barely usable; Rutorrent is still doing "reasonably" fine.

 

As for rutorrent not starting, try to start from scratch. Delete the container, pull the latest image and start with a fresh volume / host folder bound to the container's /config folder.

Edited by Cat_Seeder

Share this post


Link to post
11 hours ago, Spies said:

I can never get past 200 before everything stops but I feel like it's an issue with my hardware, I just haven't identified what yet.

Just sharing one of the links that I've sent you in private yesterday in case anyone else hits the same issue. Please ignore the Haproxy specific tweaks: https://medium.com/@pawilon/tuning-your-linux-kernel-and-haproxy-instance-for-high-loads-1a2105ea553e

 

Number of open files, max TCP connections and "reservation" times can all affect the end result when dealing with a large amount of torrents. I'm on Linux (not Unraid) and had to fine tune the host to get it all working with 1k+ torrents.

  • Like 1

Share this post


Link to post
11 hours ago, Johan76 said:

No webinterface at all at port 9080 anylonger. Am I doing this wrong?

wrong port, flood uses port 3000

Share this post


Link to post
5 hours ago, Cat_Seeder said:

 

I think so. Have a look at the documentation bellow:

enable_retry will turn off encryption in the second case.

 

So basically the difference is that 1) Tries plain text first and then retry with encryption. If client can do both it will prefer plaintext 2) Tries encryption first and then retry plain text. If client can do both it will prefer encryption.

 

Both strategies, in theory, will allow the user to connect with any kind of peer.

 

Effects on speed are somewhat hard to predict. All things being equal, plaintext is probably faster. However, if the ISP is traffic shaping, encryption will probably boost the speeds. 

 

Maybe go for 1 when VPN is enabled and 2 otherwise?

excellent, thanks for the doc paste, in that case i think we are pretty safe to go with:-

protocol.encryption.set = allow_incoming,try_outgoing,enable_retry

it may result in slightly lower (probably talking less than a second) initial connection times to peers if the peer doesn't support encryption, as it would need to switch back to plain text but it would still be able to connect to the peer ok which is the main concern. So i am happy this wont result in decremental numbers of connections to peers.

 

obviously this change will only effect new users, if anybody wants to make use of the above then they will need to modify their rtorrent.rc file manually, just to be clear this is NOT required in order to prevent ip leakage, it is purely a nice tweak to improve (slightly) security for non vpn users of this image out of the box.

  • Like 1
  • Upvote 1

Share this post


Link to post

So, it appears the VPN isn't working for me (everything works great with the VPN off, but with it on I get output like this roughly 30 seconds after OpenVPN is fired up:

2019-03-12 11:36:45,451 DEBG 'start-script' stdout output:
Tue Mar 12 11:36:45 2019 [UNDEF] Inactivity timeout (--ping-exit), exiting

2019-03-12 11:36:45,451 DEBG 'start-script' stdout output:
Tue Mar 12 11:36:45 2019 SIGTERM[soft,ping-exit] received, process exiting

I'm connecting to VPN Unlimited, and I've tried using both username/password and a private key in my .ovpn file to connect. The .ovpn file was pulled forward from an old Docker file that is no longer supported and broke when I upgraded to Ubuntu 18.04 which worked perfectly. The only change I made to the OpenVPN config file was to add the port. Once I did that, it ran all the way thru to starting the VPN but still failed.

 

Are there any things I could look at first? Should I upload a full log? I'm fairly competent with Linux, but OpenVPN remains a mystery to me.

Share this post


Link to post
Flood listens in port 3000.
Rutorrent listens in port 9080 and 9443 (Https).
If you want both you can set ENABLE_FLOOD to BOTH. 
Be warned that, while it looks great, flood uses a lot of memory and is not as feature complete as rutorrent. With 1k torrents Flood's Node.js process is using quite a bit of memory, plus the UI lags so much that it's barely usable; Rutorrent is still doing "reasonably" fine.
 
As for rutorrent not starting, try to start from scratch. Delete the container, pull the latest image and start with a fresh volume / host folder bound to the container's /config folder.
Got it working by removing as you said.
Had to remove everything and choose enable flood. Then flood work.

Cannot switch between flood/rutorrent just by changing variable and restarting docker. Need to remove everything between switches. However I found out I preferred rutorrent so switched back

Skickat från min SM-G950F via Tapatalk

Share this post


Link to post
wrong port, flood uses port 3000
Yup noticed. Had to reinstall as well to get it working but helped alot to use correct port

Skickat från min SM-G950F via Tapatalk

Share this post


Link to post

I feel like the watchdog script is too aggressive as deeming rtorrent down and restarting the docker. Can I change the timeout somewhere?

Share this post


Link to post
I feel like the watchdog script is too aggressive as deeming rtorrent down and restarting the docker. Can I change the timeout somewhere?
It's not based on a timeout, and it doesn't restart the container, it checks to see if the rtorrent process is listening and also that the process is present, so you can't really change either of these.

Sent from my EML-L29 using Tapatalk

  • Like 1

Share this post


Link to post
Posted (edited)

Hi, 

 

Bare with my I am quite new to docker. I have a problem that I am not sure how to fix. I have searched the internet but cannot really seem to fix it. So I am using Kitematic for windows because I find it easy with a GUI to handle the containers. I downloaded rtorrentvpn. I used the following values (see image). The ports were set automatically. I have understood that you must publish port in order to access container from outside the network and this seems to be in placed when i look in the output of the "Docker inspect ..." command. But I only want to access it from within my own network but from another device, so over wifi for example. I wouldnt mind to access it from outside aswell but then I have to make my host reachable.

So I can access the rtorrent through http://localhost:32862/

but I cannot access it through host ip as said in the guide from another device connected to the same network. I cannot even access it with this address from the host: 
http://<host ip>:9080/

I have replaced host ip with my computers ip from https://www.myip.com/. I have also tried 192.168.99.100:9080, which i found online that is the default docker machine. I am not sure how to access rtorrent with host ip, can anyone please help me? 

Please keep in mind all this is new to me.
 

Kitematic_2019-03-14_22-05-44.thumb.png.9b12def5841b5145cc3c41b7ad09d9d3.pngKitematic_2019-03-14_22-05-57.png.91981a9769f6453e2404173488080ce5.png

Edited by geoyil

Share this post


Link to post
20 hours ago, geoyil said:

Hi, 

 

Bare with my I am quite new to docker. I have a problem that I am not sure how to fix. I have searched the internet but cannot really seem to fix it. So I am using Kitematic for windows because I find it easy with a GUI to handle the containers. I downloaded rtorrentvpn. I used the following values (see image). The ports were set automatically. I have understood that you must publish port in order to access container from outside the network and this seems to be in placed when i look in the output of the "Docker inspect ..." command. But I only want to access it from within my own network but from another device, so over wifi for example. I wouldnt mind to access it from outside aswell but then I have to make my host reachable.

So I can access the rtorrent through http://localhost:32862/

but I cannot access it through host ip as said in the guide from another device connected to the same network. I cannot even access it with this address from the host: 
http://<host ip>:9080/

I have replaced host ip with my computers ip from https://www.myip.com/. I have also tried 192.168.99.100:9080, which i found online that is the default docker machine. I am not sure how to access rtorrent with host ip, can anyone please help me? 

Please keep in mind all this is new to me.
 

Kitematic_2019-03-14_22-05-44.thumb.png.9b12def5841b5145cc3c41b7ad09d9d3.pngKitematic_2019-03-14_22-05-57.png.91981a9769f6453e2404173488080ce5.png

I would probably drop Kinematic all together and go native (e.g., Docker Desktop). I'm not familiar with Kitematic, but it seems to be binding ports to localhost only (e.g. -p 127.0.0.1:32862:9080 instead of -p 9080:9080).

The CLI is not that hard to learn; plus not having to deal with Docker Toolbox / VirtualBox will make your life easier.

  • Like 1

Share this post


Link to post
Posted (edited)
On 3/15/2019 at 6:59 PM, Cat_Seeder said:

I would probably drop Kinematic all together and go native (e.g., Docker Desktop). I'm not familiar with Kitematic, but it seems to be binding ports to localhost only (e.g. -p 127.0.0.1:32862:9080 instead of -p 9080:9080).

The CLI is not that hard to learn; plus not having to deal with Docker Toolbox / VirtualBox will make your life easier.

I did this, It works fine thank you.

 

Another question, I wanted to try with VPN and I was successfull to access the webui for rtorrents. I am using a custom one, ProtonVPN. They have a free one I wanted to just try with. Anyway my problem is that the torrents are sometimes not downloading, they are red (error). I am trying to download the Ubuntu torrent from the official page so I know it is not the torrent because I tried this without VPN (worked great). Sometimes the torrent is red (error) but still downloading..

It does say in the bottom of rutorrent that "6881: Port status is unknown"

 

What is wrong here and what do I need to do?

 

Here is the log:

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

2019-03-16 14:55:53.754369 [info] System information Linux 1bf24515ba1e 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux
2019-03-16 14:55:53.777256 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-03-16 14:55:53.894608 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-03-16 14:55:53.971004 [info] UMASK defined as '000'
2019-03-16 14:55:53.991692 [info] Permissions already set for volume mappings
2019-03-16 14:55:54.012484 [info] VPN_ENABLED defined as 'yes'
2019-03-16 14:55:54.039579 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/us-free-01.protonvpn.com.tcp.ovpn
dos2unix: converting file /config/openvpn/us-free-01.protonvpn.com.tcp.ovpn to Unix format...
2019-03-16 14:55:54.079789 [info] VPN remote line defined as 'remote us-free-01.protonvpn.com 443'
2019-03-16 14:55:54.119903 [info] VPN_REMOTE defined as 'us-free-01.protonvpn.com'
2019-03-16 14:55:54.143366 [info] VPN_PORT defined as '443'
2019-03-16 14:55:54.171317 [info] VPN_PROTOCOL defined as 'tcp-client'
2019-03-16 14:55:54.190518 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-03-16 14:55:54.210652 [info] VPN_PROV defined as 'custom'
2019-03-16 14:55:54.229716 [info] LAN_NETWORK defined as '192.168.1.0/24'
2019-03-16 14:55:54.248860 [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-03-16 14:55:54.269020 [info] VPN_USER defined as 'changed'
2019-03-16 14:55:54.288514 [info] VPN_PASS defined as 'changed'
2019-03-16 14:55:54.307512 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-03-16 14:55:54.325812 [info] ENABLE_PRIVOXY defined as 'no'
2019-03-16 14:55:54.343934 [info] ENABLE_FLOOD defined as 'no'
2019-03-16 14:55:54.362401 [info] ENABLE_AUTODL_IRSSI defined as 'yes'
2019-03-16 15:00:26.243449 [info] Starting Supervisor...
2019-03-16 15:00:26,511 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2019-03-16 15:00:26,512 INFO Set uid to user 0 succeeded
2019-03-16 15:00:26,516 INFO supervisord started with pid 7
2019-03-16 15:00:27,519 INFO spawned: 'start-script' with pid 147
2019-03-16 15:00:27,521 INFO spawned: 'pyrocore-script' with pid 148
2019-03-16 15:00:27,524 INFO spawned: 'rutorrent-script' with pid 149
2019-03-16 15:00:27,532 INFO spawned: 'flood-script' with pid 150
2019-03-16 15:00:27,535 INFO spawned: 'irssi-script' with pid 151
2019-03-16 15:00:27,537 INFO spawned: 'watchdog-script' with pid 152
2019-03-16 15:00:27,539 INFO spawned: 'privoxy-script' with pid 154
2019-03-16 15:00:27,540 INFO reaped unknown pid 8
2019-03-16 15:00:27,541 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-03-16 15:00:27,543 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-03-16 15:00:27,546 INFO success: pyrocore-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-03-16 15:00:27,546 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-03-16 15:00:27,546 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-03-16 15:00:27,546 INFO success: irssi-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-03-16 15:00:27,546 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-03-16 15:00:27,546 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-03-16 15:00:27,557 DEBG 'watchdog-script' stdout output:
[info] rTorrent config file doesnt exist, copying default to /config/rtorrent/config/...

2019-03-16 15:00:27,565 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2019-03-16 15:00:27,566 DEBG 'flood-script' stdout output:
[info] Flood not enabled, skipping starting Flood Web UI

2019-03-16 15:00:27,567 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 140143884507904 for <Subprocess at 140143883406584 with name flood-script in state RUNNING> (stderr)>
2019-03-16 15:00:27,567 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 140143883353984 for <Subprocess at 140143883406584 with name flood-script in state RUNNING> (stdout)>
2019-03-16 15:00:27,567 INFO exited: flood-script (exit status 0; expected)
2019-03-16 15:00:27,568 DEBG received SIGCLD indicating a child quit
2019-03-16 15:00:27,569 DEBG fd 37 closed, stopped monitoring <POutputDispatcher at 140143883451064 for <Subprocess at 140143883405288 with name privoxy-script in state RUNNING> (stdout)>
2019-03-16 15:00:27,570 DEBG fd 41 closed, stopped monitoring <POutputDispatcher at 140143883451496 for <Subprocess at 140143883405288 with name privoxy-script in state RUNNING> (stderr)>
2019-03-16 15:00:27,570 INFO exited: privoxy-script (exit status 0; expected)
2019-03-16 15:00:27,570 DEBG received SIGCLD indicating a child quit
2019-03-16 15:00:27,620 DEBG 'watchdog-script' stderr output:
dos2unix: 
2019-03-16 15:00:27,621 DEBG 'watchdog-script' stderr output:
converting file /config/rtorrent/config/rtorrent.rc to Unix format...

2019-03-16 15:00:27,725 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-03-16 15:00:27,727 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-03-16 15:00:27,729 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2019-03-16 15:00:27,732 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2019-03-16 15:00:27,733 DEBG 'pyrocore-script' stdout output:
WARNING  Configuration file '/config/pyrocore/config.ini' not found, use the command 'pyroadmin --create-config' to create it!

2019-03-16 15:00:27,735 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-03-16 15:00:27,737 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-03-16 15:00:27,743 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2019-03-16 15:00:27,753 DEBG 'pyrocore-script' stdout output:
WARNING  Configuration file '/config/pyrocore/config.py' not found!

2019-03-16 15:00:27,757 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2019-03-16 15:00:27,760 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-03-16 15:00:27,762 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/bash-completion.default' written!

2019-03-16 15:00:27,765 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/bash-completion' written!

2019-03-16 15:00:27,772 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/default-16.rc.default' written!

2019-03-16 15:00:27,774 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/default-16.rc' written!

2019-03-16 15:00:27,777 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/default-256.rc.default' written!

2019-03-16 15:00:27,779 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/default-256.rc' written!

2019-03-16 15:00:27,782 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/default-8.rc.default' written!

2019-03-16 15:00:27,785 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/default-8.rc' written!

2019-03-16 15:00:27,788 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/happy-pastel.rc.default' written!

2019-03-16 15:00:27,790 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/happy-pastel.rc' written!

2019-03-16 15:00:27,795 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/solarized-blue.rc.default' written!

2019-03-16 15:00:27,798 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/solarized-blue.rc' written!

2019-03-16 15:00:27,802 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/solarized-yellow.rc.default' written!

2019-03-16 15:00:27,805 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/color-schemes/solarized-yellow.rc' written!

2019-03-16 15:00:27,807 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...

2019-03-16 15:00:27,809 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/4.9.125-linuxkit

2019-03-16 15:00:27,810 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/config.ini.default' written!

2019-03-16 15:00:27,810 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2019-03-16 15:00:27,811 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2019-03-16 15:00:27,812 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2019-03-16 15:00:27,813 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/config.ini' written!

2019-03-16 15:00:27,816 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/config.py.default' written!

2019-03-16 15:00:27,818 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/config.py' written!

2019-03-16 15:00:27,819 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2019-03-16 15:00:27,820 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.9.125-linuxkit

2019-03-16 15:00:27,821 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2019-03-16 15:00:27,822 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/logging.cron.ini.default' written!

2019-03-16 15:00:27,822 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-03-16 15:00:27,822 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'

2019-03-16 15:00:27,824 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/logging.cron.ini' written!

2019-03-16 15:00:27,834 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/logging.scripts.ini.default' written!

2019-03-16 15:00:27,836 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/logging.scripts.ini' written!

2019-03-16 15:00:27,839 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/logging.torque.ini.default' written!

2019-03-16 15:00:27,842 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/logging.torque.ini' written!

2019-03-16 15:00:27,845 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent-pyro.rc.default' written!

2019-03-16 15:00:27,846 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2019-03-16 15:00:27,847 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent-pyro.rc' written!

2019-03-16 15:00:27,850 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2019-03-16 15:00:27,851 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-03-16 15:00:27,852 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 

2019-03-16 15:00:27,853 DEBG 'start-script' stdout output:
--------------------

2019-03-16 15:00:27,853 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/00-default.rc.default' written!

2019-03-16 15:00:27,855 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/00-default.rc' written!

2019-03-16 15:00:27,859 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/auto-scrape.rc.default' written!

2019-03-16 15:00:27,861 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/auto-scrape.rc' written!

2019-03-16 15:00:27,865 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/bind-navigation-keys.rc.default' written!

2019-03-16 15:00:27,867 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/bind-navigation-keys.rc' written!

2019-03-16 15:00:27,870 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/categories.rc.default' written!

2019-03-16 15:00:27,873 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/categories.rc' written!

2019-03-16 15:00:27,876 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/collapse-built-in-views.rc.default' written!

2019-03-16 15:00:27,878 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/collapse-built-in-views.rc' written!

2019-03-16 15:00:27,881 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/commands.rc.default' written!

2019-03-16 15:00:27,884 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/commands.rc' written!

2019-03-16 15:00:27,886 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/helper-methods.rc.default' written!

2019-03-16 15:00:27,888 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/helper-methods.rc' written!

2019-03-16 15:00:27,891 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/logging.rc.default' written!

2019-03-16 15:00:27,893 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/logging.rc' written!

2019-03-16 15:00:27,895 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/quick-help.rc.default' written!

2019-03-16 15:00:27,898 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/quick-help.rc' written!

2019-03-16 15:00:27,903 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/theming.rc.default' written!

2019-03-16 15:00:27,903 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-03-16 15:00:27,904 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2019-03-16 15:00:27,905 DEBG 'start-script' stdout output:
--------------------

2019-03-16 15:00:27,905 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/theming.rc' written!

2019-03-16 15:00:27,907 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-03-16 15:00:27,908 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/timestamps.rc.default' written!

2019-03-16 15:00:27,909 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/timestamps.rc' written!

2019-03-16 15:00:27,912 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/torque.rc.default' written!

2019-03-16 15:00:27,914 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/torque.rc' written!

2019-03-16 15:00:27,918 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-datasize.rc.default' written!

2019-03-16 15:00:27,920 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-datasize.rc' written!

2019-03-16 15:00:27,922 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-indemand.rc.default' written!

2019-03-16 15:00:27,924 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-indemand.rc' written!

2019-03-16 15:00:27,926 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-last_xfer.rc.default' written!

2019-03-16 15:00:27,928 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-last_xfer.rc' written!

2019-03-16 15:00:27,932 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-messages.rc.default' written!

2019-03-16 15:00:27,934 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-messages.rc' written!

2019-03-16 15:00:27,937 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-ratio.rc.default' written!

2019-03-16 15:00:27,938 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-ratio.rc' written!

2019-03-16 15:00:27,941 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-tagged.rc.default' written!

2019-03-16 15:00:27,943 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-tagged.rc' written!

2019-03-16 15:00:27,947 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-trackers.rc.default' written!

2019-03-16 15:00:27,950 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-trackers.rc' written!

2019-03-16 15:00:27,950 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 WARNING: file 'credentials.conf' is group or others accessible

2019-03-16 15:00:27,950 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Sat Mar 16 15:00:27 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10

2019-03-16 15:00:27,953 DEBG 'start-script' stdout output:
[info] OpenVPN started

2019-03-16 15:00:27,953 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-uploaded.rc.default' written!

2019-03-16 15:00:27,954 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-03-16 15:00:27,954 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 NOTE: --fast-io is disabled since we are not using UDP

2019-03-16 15:00:27,955 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/rtorrent.d/view-uploaded.rc' written!

2019-03-16 15:00:27,956 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication

2019-03-16 15:00:27,957 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication

2019-03-16 15:00:27,957 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]209.58.147.210:443

2019-03-16 15:00:27,958 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 Socket Buffers: R=[87380->87380] S=[16384->16384]

2019-03-16 15:00:27,958 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:27 2019 Attempting to establish TCP connection with [AF_INET]209.58.147.210:443 [nonblock]

2019-03-16 15:00:27,961 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/conky/conkyrc.default' written!

2019-03-16 15:00:27,963 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/conky/conkyrc' written!

2019-03-16 15:00:27,966 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/conky/rtorstat.txt.default' written!

2019-03-16 15:00:27,968 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/conky/rtorstat.txt' written!

2019-03-16 15:00:27,970 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/irc_status.txt.default' written!

2019-03-16 15:00:27,972 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/irc_status.txt' written!

2019-03-16 15:00:27,976 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/json.default' written!

2019-03-16 15:00:27,978 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/json' written!

2019-03-16 15:00:27,980 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/orphans.txt.default' written!

2019-03-16 15:00:27,982 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/orphans.txt' written!

2019-03-16 15:00:27,985 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/rtorstat.html.default' written!

2019-03-16 15:00:27,986 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/templates/rtorstat.html' written!

2019-03-16 15:00:27,989 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/torque.ini.default' written!

2019-03-16 15:00:27,991 DEBG 'pyrocore-script' stdout output:
INFO     Configuration file '/config/pyrocore/torque.ini' written!

2019-03-16 15:00:27,992 DEBG 'pyrocore-script' stdout output:
INFO     Creating u'/config/pyrocore/log'...

2019-03-16 15:00:27,994 DEBG 'pyrocore-script' stdout output:
INFO     Creating u'/config/pyrocore/data'...

2019-03-16 15:00:27,996 DEBG 'pyrocore-script' stdout output:
INFO     Creating u'/config/pyrocore/run'...

2019-03-16 15:00:27,998 DEBG 'pyrocore-script' stdout output:
INFO     Creating u'/config/pyrocore/htdocs'...

2019-03-16 15:00:27,999 DEBG 'pyrocore-script' stdout output:
INFO     Total time: 0.269 seconds.

2019-03-16 15:00:28,007 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 140143883403416 for <Subprocess at 140143883406008 with name pyrocore-script in state RUNNING> (stdout)>
2019-03-16 15:00:28,007 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 140143883403776 for <Subprocess at 140143883406008 with name pyrocore-script in state RUNNING> (stderr)>
2019-03-16 15:00:28,007 INFO exited: pyrocore-script (exit status 0; expected)
2019-03-16 15:00:28,008 DEBG received SIGCLD indicating a child quit
2019-03-16 15:00:28,959 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:28 2019 TCP connection established with [AF_INET]209.58.147.210:443
Sat Mar 16 15:00:28 2019 TCP_CLIENT link local: (not bound)
Sat Mar 16 15:00:28 2019 TCP_CLIENT link remote: [AF_INET]209.58.147.210:443

2019-03-16 15:00:29,116 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:29 2019 TLS: Initial packet from [AF_INET]209.58.147.210:443, sid=91c4b554 9618ad06

2019-03-16 15:00:29,601 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:29 2019 VERIFY OK: depth=2, C=CH, O=ProtonVPN AG, CN=ProtonVPN Root CA

2019-03-16 15:00:29,601 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:29 2019 VERIFY OK: depth=1, C=CH, O=ProtonVPN AG, CN=ProtonVPN Intermediate CA 1

2019-03-16 15:00:29,601 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:29 2019 VERIFY KU OK
Sat Mar 16 15:00:29 2019 Validating certificate extended key usage
Sat Mar 16 15:00:29 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Sat Mar 16 15:00:29 2019 VERIFY EKU OK
Sat Mar 16 15:00:29 2019 VERIFY OK: depth=0, CN=us-tx-101.protonvpn.com

2019-03-16 15:00:29,921 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:29 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Sat Mar 16 15:00:29 2019 [us-tx-101.protonvpn.com] Peer Connection Initiated with [AF_INET]209.58.147.210:443

2019-03-16 15:00:31,017 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 SENT CONTROL [us-tx-101.protonvpn.com]: 'PUSH_REQUEST' (status=1)

2019-03-16 15:00:31,373 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.8.8.1,sndbuf 524288,rcvbuf 524288,explicit-exit-notify,comp-lzo no,route-gateway 10.7.1.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.7.1.5 255.255.255.0,peer-id 0,cipher AES-256-GCM'
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: timers and/or timeouts modified
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: --explicit-exit-notify can only be used with --proto udp
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: compression parms modified

2019-03-16 15:00:31,375 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Sat Mar 16 15:00:31 2019 Socket Buffers: R=[374400->425984] S=[87040->425984]
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: --ifconfig/up options modified
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: route options modified
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: route-related options modified
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: peer-id set
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: adjusting link_mtu to 1659
Sat Mar 16 15:00:31 2019 OPTIONS IMPORT: data channel crypto options modified
Sat Mar 16 15:00:31 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Sat Mar 16 15:00:31 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Mar 16 15:00:31 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key

2019-03-16 15:00:31,375 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02
Sat Mar 16 15:00:31 2019 TUN/TAP device tun0 opened
Sat Mar 16 15:00:31 2019 TUN/TAP TX queue length set to 100

2019-03-16 15:00:31,375 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sat Mar 16 15:00:31 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-03-16 15:00:31,377 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 /usr/bin/ip addr add dev tun0 10.7.1.5/24 broadcast 10.7.1.255

2019-03-16 15:00:31,378 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 /root/openvpnup.sh tun0 1500 1587 10.7.1.5 255.255.255.0 init

2019-03-16 15:00:31,381 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 /usr/bin/ip route add 209.58.147.210/32 via 172.17.0.1

2019-03-16 15:00:31,383 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.7.1.1

2019-03-16 15:00:31,385 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.7.1.1

2019-03-16 15:00:31,388 DEBG 'start-script' stdout output:
Sat Mar 16 15:00:31 2019 Initialization Sequence Completed

2019-03-16 15:00:31,439 DEBG 'watchdog-script' stdout output:
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.7.1.5 different, marking for reconfigure

2019-03-16 15:00:31,447 DEBG 'watchdog-script' stdout output:
[info] rTorrent not running

2019-03-16 15:00:31,469 DEBG 'irssi-script' stdout output:
Script started, file is /home/nobody/typescript

2019-03-16 15:00:31,495 DEBG 'irssi-script' stdout output:
Script done, file is /home/nobody/typescript

2019-03-16 15:00:31,499 DEBG fd 27 closed, stopped monitoring <POutputDispatcher at 140143883613392 for <Subprocess at 140143883406368 with name irssi-script in state RUNNING> (stdout)>
2019-03-16 15:00:31,499 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 140143883612384 for <Subprocess at 140143883406368 with name irssi-script in state RUNNING> (stderr)>
2019-03-16 15:00:31,499 INFO exited: irssi-script (exit status 0; expected)
2019-03-16 15:00:31,500 DEBG received SIGCLD indicating a child quit
2019-03-16 15:00:32,453 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 209.58.147.210

2019-03-16 15:00:32,460 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2019-03-16 15:00:32,462 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2019-03-16 15:00:32,464 DEBG 'watchdog-script' stdout output:
Script started, file is /home/nobody/typescript

2019-03-16 15:00:32,481 DEBG 'watchdog-script' stdout output:
Script done, file is /home/nobody/typescript

2019-03-16 15:00:33,085 DEBG 'rutorrent-script' stdout output:
[info] rtorrent started, setting up rutorrent...
[info] Setting PHP timezone to Europe/Stockholm...

2019-03-16 15:00:33,089 DEBG 'rutorrent-script' stdout output:
[info] nginx cert files doesnt exist, copying default to /config/nginx/certs/...

2019-03-16 15:00:33,098 DEBG 'rutorrent-script' stdout output:
[info] nginx security file doesnt exist, copying default to /config/nginx/security/...

2019-03-16 15:00:33,103 DEBG 'rutorrent-script' stdout output:
[info] nginx config file doesnt exist, copying default to /config/nginx/config/...

2019-03-16 15:00:33,114 DEBG 'rutorrent-script' stdout output:
[info] rutorrent conf folder doesnt exist, copying default to /config/rutorrent/conf/...

2019-03-16 15:00:33,155 DEBG 'rutorrent-script' stdout output:
[info] running rsync to copy rutorrent user plugins to the plugins folder inside the container...

2019-03-16 15:00:33,162 DEBG 'rutorrent-script' stdout output:
sending incremental file list

2019-03-16 15:00:33,170 DEBG 'rutorrent-script' stdout output:
README.txt

2019-03-16 15:00:33,171 DEBG 'rutorrent-script' stdout output:
theme/themes/README.txt

2019-03-16 15:00:33,172 DEBG 'rutorrent-script' stdout output:

sent 413 bytes  received 64 bytes  954.00 bytes/sec
total size is 237  speedup is 0.50

2019-03-16 15:00:33,176 DEBG 'rutorrent-script' stdout output:
[info] rutorrent share folder doesnt exist, copying default to /config/rutorrent/share/...

2019-03-16 15:00:33,194 DEBG 'rutorrent-script' stdout output:
[info] starting php-fpm...

2019-03-16 15:00:33,288 DEBG 'rutorrent-script' stderr output:
[NOTICE] [pool www] 'user' directive is ignored when FPM is not running as root
[NOTICE] [pool www] 'group' directive is ignored when FPM is not running as root

2019-03-16 15:00:33,306 DEBG 'rutorrent-script' stdout output:
[info] starting nginx...

2019-03-16 15:00:33,488 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2019-03-16 15:00:33,492 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening

2019-03-16 15:00:33,495 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2019-03-16 15:00:33,499 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

2019-03-16 15:00:33,502 DEBG 'watchdog-script' stdout output:
[info] nginx running
[info] Initialising ruTorrent plugins...

2019-03-16 15:00:33,919 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

2019-03-16 15:01:19,536 DEBG 'rutorrent-script' stderr output:
2019/03/16 15:01:19 [error] 1329#1329: *1 FastCGI sent in stderr: "PHP message: PHP Warning:  fopen(/usr/share/webapps/rutorrent/share/users/admin/settings/uisettings.json): failed to open stream: No such file or directory in /usr/share/webapps/rutorrent/php/getsettings.php on line 7" while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /php/getsettings.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

 

Edited by geoyil

Share this post


Link to post
On 3/15/2019 at 10:28 PM, geoyil said:

I did this, It works fine thank you.

 

Another question, I wanted to try with VPN and I was successfull to access the webui for rtorrents. I am using a custom one, ProtonVPN. They have a free one I wanted to just try with. Anyway my problem is that the torrents are sometimes not downloading, they are red (error). I am trying to download the Ubuntu torrent from the official page so I know it is not the torrent because I tried this without VPN (worked great). Sometimes the torrent is red (error) but still downloading..

It does say in the bottom of rutorrent that "6881: Port status is unknown"

 

What is wrong here and what do I need to do?

 

Here is the log:


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

2019-03-16 14:55:53.754369 [info] System information Linux 1bf24515ba1e 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux
2019-03-16 14:55:53.777256 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-03-16 14:55:53.894608 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-03-16 14:55:53.971004 [info] UMASK defined as '000'
2019-03-16 14:55:53.991692 [info] Permissions already set for volume mappings
2019-03-16 14:55:54.012484 [info] VPN_ENABLED defined as 'yes'
2019-03-16 14:55:54.039579 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/us-free-01.protonvpn.com.tcp.ovpn
dos2unix: converting file /config/openvpn/us-free-01.protonvpn.com.tcp.ovpn to Unix format...
2019-03-16 14:55:54.079789 [info] VPN remote line defined as 'remote us-free-01.protonvpn.com 443'
2019-03-16 14:55:54.119903 [info] VPN_REMOTE defined as 'us-free-01.protonvpn.com'
2019-03-16 14:55:54.143366 [info] VPN_PORT defined as '443'
2019-03-16 14:55:54.171317 [info] VPN_PROTOCOL defined as 'tcp-client'
2019-03-16 14:55:54.190518 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-03-16 14:55:54.210652 [info] VPN_PROV defined as 'custom'
2019-03-16 14:55:54.229716 [info] LAN_NETWORK defined as '192.168.1.0/24'
2019-03-16 14:55:54.248860 [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-03-16 14:55:54.269020 [info] VPN_USER defined as 'changed'
2019-03-16 14:55:54.288514 [info] VPN_PASS defined as 'changed'
2019-03-16 14:55:54.307512 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-03-16 14:55:54.325812 [info] ENABLE_PRIVOXY defined as 'no'
2019-03-16 14:55:54.343934 [info] ENABLE_FLOOD defined as 'no'
2019-03-16 14:55:54.362401 [info] ENABLE_AUTODL_IRSSI defined as 'yes'

 ---- Logs cut -----
 
 2019-03-16 15:00:27,822 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-03-16 15:00:27,822 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'

---- Logs cut -----

2019-03-16 15:00:33,919 DEBG 'watchdog-script' stdout output:
[info] ruTorrent plugins initialised

2019-03-16 15:01:19,536 DEBG 'rutorrent-script' stderr output:
2019/03/16 15:01:19 [error] 1329#1329: *1 FastCGI sent in stderr: "PHP message: PHP Warning:  fopen(/usr/share/webapps/rutorrent/share/users/admin/settings/uisettings.json): failed to open stream: No such file or directory in /usr/share/webapps/rutorrent/php/getsettings.php on line 7" while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /php/getsettings.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

 

 

Humm. I'm not familiar with Proton VPN, but I would check if they support Port Forwarding. Without it you will have a half-baked experience at best. No incoming connections means passive mode. You will get in trouble in private trackers. In public trackers you may not find many (or even any peers)... If you want to set up a VPN always check if they do allow port forwarding and if the port that you have opened is reachable (https://www.yougetsignal.com/tools/open-ports/).
Other than that, while it is not related to your issue, you may not be able to access the webui remotely (see Q2 at

 

Share this post


Link to post

Hi guys :) I'm new to rtorrent-ps and I have read the guide how to install it - but, is it installed in this docker or ? Where do I start ? :) Thanks in advance

 

John

Share this post


Link to post
On 3/18/2019 at 2:16 AM, Cat_Seeder said:

 

Humm. I'm not familiar with Proton VPN, but I would check if they support Port Forwarding. Without it you will have a half-baked experience at best. No incoming connections means passive mode. You will get in trouble in private trackers. In public trackers you may not find many (or even any peers)... If you want to set up a VPN always check if they do allow port forwarding and if the port that you have opened is reachable (https://www.yougetsignal.com/tools/open-ports/).
Other than that, while it is not related to your issue, you may not be able to access the webui remotely (see Q2 at

 

 

Hm, reading the questions posted by Binhex (FAQ) I see that You have to manually make sure that port forwarding is enabled if your VPN support it. Lets say the VPN supports it. What do I have to do on the docker side? From my understanding I should not open it in my router, because the port forwarding happens on the VPN. Am I suppose to change something in rtorrent.rc or somewhere else in docker? I am referring to Q16 in the general support. It says that you should configure the application to use the assigned port. Where do you do this?  

Share this post


Link to post
 
Hm, reading the questions posted by Binhex (FAQ) I see that You have to manually make sure that port forwarding is enabled if your VPN support it. Lets say the VPN supports it. What do I have to do on the docker side? From my understanding I should not open it in my router, because the port forwarding happens on the VPN. Am I suppose to change something in rtorrent.rc or somewhere else in docker? I am referring to Q16 in the general support. It says that you should configure the application to use the assigned port. Where do you do this?  
Yes rtorrent.rc is the file used to configure rTorrent, including incoming port

Sent from my EML-L29 using Tapatalk

Share this post


Link to post
1 minute ago, binhex said:

Yes rtorrent.rc is the file used to configure rTorrent, including incoming port

Sent from my EML-L29 using Tapatalk
 

So the Port range should be changed to only be the port that has been forwarded by VPN provider? 

Share this post


Link to post
So the Port range should be changed to only be the port that has been forwarded by VPN provider? 
Yes

Sent from my EML-L29 using Tapatalk

  • Like 1

Share this post


Link to post

Hi guys,

 

Just sharing (no support needed). I have missconfigured autodl-irssi and ended up with over 3k torrents in the container.

Tonight I got several emails warning me that OOM Killer was running in a loop (since VPN IP changes every time I was also blocked from a tracker for spamming... Again! :().

Out of curiosity I had a look at the running process tab. rtorrent-ps + rutorrent + nginx + PHP were sitting at a cool 1.2 GB. Flood on the other hand quickly goes from 500 MB to 4 GB to 6 GB to OOM. node.js processes are basically eating all available run (not sure if this is expected or a memory leak).

 

What I've learned today:

 

1) Always double check that you have setup autodl-irssi correctly. Do set sane daily limits on every filter.

2) Disable Flood. Honestly, it's not worth it. I've stopped and removed 2700+ torrent files manually. Even with only ~300 torrents Flood was still using ~550 MB memory (a good 4x more than rtorrent + rutorrent combined). At this stage I would say that Flood is only for casual users.

3) Be very careful with VPNs + container auto restart. 

 

Edited by Cat_Seeder

Share this post


Link to post

I was considering using a reverse proxy to make rutorrent accessible from the web (mainly for NZB360), however, I was doing some research before I did so and it seems that RPC2 doesn't require auth (I think it used to?). To test, I removed my username/password from Sonarr, Radarr and NZB360, all three seem to connect without any username/password. Are others seeing this?

 

I don't think I've modified any configuration that would effect this. I've been using this container for a while but I think the deepest thing I've done configuration wise is add my own username/password and delete the default using the scripts.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now