I'm getting the following over and over again in the log. But i don't see any error.
 
2017-08-11 22:14:26,869 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '212.92.116.6'
2017-08-11 22:14:26,870 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '27739'
2017-08-11 22:14:27,003 DEBG 'rtorrent-script' stdout output:
[debug] VPN incoming port is 27739
[debug] VPN IP is 10.37.10.6
[debug] rTorrent incoming port is 27739
[debug] rTorrent IP is 10.37.10.6
2017-08-11 22:14:57,004 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
2017-08-11 22:14:57,134 DEBG 'rtorrent-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.37.10.6'
2017-08-11 22:14:57,141 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '212.92.116.6'
2017-08-11 22:14:57,141 DEBG 'rtorrent-script' stdout output:
[debug] Incoming port for tunnel is '27739'
2017-08-11 22:14:57,275 DEBG 'rtorrent-script' stdout output:
[debug] VPN incoming port is 27739
[debug] VPN IP is 10.37.10.6
[debug] rTorrent incoming port is 27739
[debug] rTorrent IP is 10.37.10.6
 

There is no error, you got debug on

Sent from my SM-G935F using Tapatalk

Is there any chance of IP leakage with this docker? I don't want to use it if there is a risk that my home public IP will be leaked using PIA.
 
Also what does ENABLE_FLOOD do?

No chance of IP leakage, flood is alternative web UI (beta)

Sent from my SM-G935F using Tapatalk

5 hours ago, binhex said:

There is no error, you got debug on

Sent from my SM-G935F using Tapatalk
 

 

Why am I unable to access the webui then? I just keep getting "ERR_CONNECTION_TIMED_OUT" and this is on both DelugeVPN and rtorrentVPN. Your other containers (sonarr, radarr) work fine.

 

Attaching the new log.

supervisord.log

 
Why am I unable to access the webui then? I just keep getting "ERR_CONNECTION_TIMED_OUT" and this is on both DelugeVPN and rtorrentVPN. Your other containers (sonarr, radarr) work fine.
 
Attaching the new log.
supervisord.log

Your lan_network is incorrectly defined, see my faq for details, link will be in this thread no doubt several times

Sent from my SM-G935F using Tapatalk

42 minutes ago, binhex said:

Your lan_network is incorrectly defined, see my faq for details, link will be in this thread no doubt several times

Sent from my SM-G935F using Tapatalk
 

 

That's got it. Thank you, sir. If I can get this configured and working with Sonarr and Radarr, I'll send you some beer money.

Is this expected behavior?

 

I have several instances of this docker and when I update one, this immediately shows on the others. When I update the remaining instances, nothing gets pulled and they update without issue. Curious as to what is going on. Otherwise, the docker works great and all work wonderfully.

 

Edited August 13, 20178 yr by TheRefugee

Is this expected behavior?
 
I have several instances of this docker and when I update one, this immediately shows on the others. When I update the remaining instances, nothing gets pulled and they update without issue. Curious as to what is going on. Otherwise, the docker works great and all work wonderfully.
 

Completely expected, not sure why you have multiple containers defined though for the same image.

Sent from my SM-G935F using Tapatalk

3 hours ago, binhex said:

Completely expected, not sure why you have multiple containers defined though for the same image.

Sent from my SM-G935F using Tapatalk
 

 

I'm not certain of the correct terminology for containers/docker/images. Do I have my ports set up properly so each container is operating independently? I have multiple containers because I was told that rutorrent can only handle 3,500-6000 torrents before the webgui stops working properly. I don't have nearly that many now but I separated TV, Movies and books into their own container because it is not out of the question that I would start to push the upper limits of what rutorrent can handle.

For some reason I can no longer connect to rTorrent. I haven't made any changes, so I guess it must have happened after the last update.

It connects and gets an ip from the vpn provider, starts privoxy, but fails to start rTorrent.

Any ideas?

 

Here's the log.

 

Quote

2017-08-13 21:14:39,508 DEBG 'start-script' stdout output:
Sun Aug 13 21:14:39 2017 Initialization Sequence Completed

2017-08-13 21:15:03,686 DEBG 'rtorrent-script' stdout output:
[warn] Wait for rTorrent process to start aborted

2017-08-13 21:15:33,803 DEBG 'rtorrent-script' stdout output:
[info] rTorrent not running

2017-08-13 21:15:33,804 DEBG 'rtorrent-script' stdout output:
[info] Removing any rtorrent session lock files left over from the previous run...

2017-08-13 21:15:33,804 DEBG 'rtorrent-script' stdout output:
[info] Attempting to start rTorrent...

2017-08-13 21:15:33,805 DEBG 'rtorrent-script' stdout output:
Script started, file is /home/nobody/typescript

2017-08-13 21:15:33,823 DEBG 'rtorrent-script' stdout output:
Script done, file is /home/nobody/typescript

2017-08-13 21:16:02,919 DEBG 'rtorrent-script' stdout output:
[warn] Wait for rTorrent process to start aborted

2017-08-13 21:16:33,035 DEBG 'rtorrent-script' stdout output:
[info] rTorrent not running
 

I also seem to have the same problem as dagarth. rtorrent runs if I log in to the docker and run it manually via the CLI.

19 hours ago, TheRefugee said:

 

I'm not certain of the correct terminology for containers/docker/images. Do I have my ports set up properly so each container is operating independently? I have multiple containers because I was told that rutorrent can only handle 3,500-6000 torrents before the webgui stops working properly. I don't have nearly that many now but I separated TV, Movies and books into their own container because it is not out of the question that I would start to push the upper limits of what rutorrent can handle.

 

ahh yes thats fine, your ports looks good to me, just make sure you have a separate /config path for each as well right. im not sure of the limits for rutorrent, but i thought it was higher than that, more like 20,000 but i might be wrong.

After the last update, I have the same problem as @Dagarth and @doremi.

 

I'm stuck on:
 

Quote

2017-08-15 04:38:16,900 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for rTorrent process to start...

2017-08-15 04:38:17,905 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for rTorrent process to start...

2017-08-15 04:38:18,910 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for rTorrent process to start...

2017-08-15 04:38:19,915 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for rTorrent process to start...

2017-08-15 04:38:20,919 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for rTorrent process to start...

2017-08-15 04:38:21,924 DEBG 'rtorrent-script' stdout output:
[debug] Waiting for rTorrent process to start...

2017-08-15 04:38:22,929 DEBG 'rtorrent-script' stdout output:
[warn] Wait for rTorrent process to start aborted

 

 

7 hours ago, lastOne said:

After the last update, I have the same problem as @Dagarth and @doremi.

 

I'm stuck on:
 

 

 

ok guys i will take a look at lunch and see if i can reproduce this.

Thanks. Let us know if you need any more info that might help. 

well @Dagarth @doremi @lastOne i have done some testing and i cant replicate the issue, so im assuming this is either some corruption of your plugins and/or corruption of rtorrent settings. i can successfully create a container from scratch with no pre-existing configuration and it starts successfully with normal access to the rutorrent web ui and full port forwarding working (for pia) and the correct external ip assigned.

 

so with that in mind i think we need to try and reset some stuff and see what the cause is:-

 

1. delete /config/rutorrent/plugins/ folder and reboot the container - if this doesn't fix it move onto 2.

2. rename /config/rtorrent/rtorrent.rc to /config/rtorrent/rtorrent.rc.old and reboot the container - if this doesn't fix it move onto 3.

3. rename host path for /config to suffix with '_old' e.g. /mnt/cache/appdata/rutorrent_old and reboot the container - this will fix it (tested).

 

if you had to go with step 3 then you will need to copy across from the old path the /config/openvpn/ folder to the newly created /config, you are probably safe to also copy your rtorrent.rc file too, the only last things to do would then be to tweak any settings for the rutorrent web ui that have been reset.

 

Thanks for looking into it binhex.

I tried all the steps, but it still didn't work. When I disabled the vpn, i could access the web ui though.

After deleting the container and starting from scratch, I'm still getting the same problem with the rtorrent not starting, but this time i can access the ui even with the vpn enabled.

The weird thing is that the plugins button has dissappeared, and also the portion that shows the torrent files.

 

 

The appdata folder looks like this now with folders missing

 

compared to this one before

 

Anyway, I'll have a look again later on in case I have done something wrong, and wait to see if it worked for @doremi and @lastOne

44 minutes ago, Dagarth said:

Thanks for looking into it binhex.

I tried all the steps, but it still didn't work. When I disabled the vpn, i could access the web ui though.

After deleting the container and starting from scratch, I'm still getting the same problem with the rtorrent not starting, but this time i can access the ui even with the vpn enabled.

The weird thing is that the plugins button has dissappeared, and also the portion that shows the torrent files.

 

 

The appdata folder looks like this now with folders missing

 

compared to this one before

 

Anyway, I'll have a look again later on in case I have done something wrong, and wait to see if it worked for @doremi and @lastOne

 

i suspect you didnt do this:-

 

Quote

if you had to go with step 3 then you will need to copy across from the old path the /config/openvpn/ folder to the newly created /config

 

but lets see in the logs, please follow this procedure:-

 

 

Edited August 16, 20178 yr by binhex

I've tried all the above points... no go, then I remove the container, add it again... as soon as I set vpn to false everything works, with vpn on... I can connect to webUI but it`s empty

1 minute ago, lastOne said:

I've tried all the above points... no go, then I remove the container, add it again... as soon as I set vpn to false everything works, with vpn on... I can connect to webUI but it`s empty

 

ok please follow this procedure:-

 

 

as I said:

- with VPN on, webUI it open but it`s empty;

- with VPN off, webUI opens and all my torrents are there;

 

supervisord_novpn.log

supervisord_vpn.log

Edited August 16, 20178 yr by lastOne

@lastOne @binhex @Dagarth FYI, my issue seems to be resolved on the last update.

[mention=69145]lastOne[/mention] [mention=11148]binhex[/mention] [mention=75727]Dagarth[/mention] FYI, my issue seems to be resolved on the last update.

Yeah I spotted your issue (and possibly the other guys) in the log and worked around the problem, but it was getting late so I pushed the build button and went to bed. So I'm not 100% happy with the fix, so I will tweak it again today, so if you see another update then please pull it down and let me know if it's still ok.

Sent from my SM-G935F using Tapatalk

I recreated the container and everything is working fine now. Thanks!

13 minutes ago, Dagarth said:

I recreated the container and everything is working fine now. Thanks!

 

thats good news, as stated above i currently have a new build running with a more robust fix than what i put in last night, it would be great if you could pull this down and test thats its still working ok, ive done testing locally but its very difficult to reproduce the problem exactly as im with a different provider and the delay i think is due to additional config pushed to the client (airvpn). 

 

the build should be available in around 30 mins from this post date.

Everything's still working after the latest update. Thanks again for looking into it.