[Support] binhex - rTorrentVPN

JonathanM · April 26, 2017

51 minutes ago, binhex said:

this is done via openvpn "up" script and should run every time the tunnel gets disconnected

I've seen this behaviour as well in the delugeVPN container, perhaps you could schedule a cron to reverify every hour or so? I'm not sure that the current method is catching changes consistently.

binhex · April 26, 2017

50 minutes ago, jonathanm said:

I've seen this behaviour as well in the delugeVPN container

i dont set the external ip at all for deluge as it doesnt need/have this setting??, listen interface != external ip address, and this (as in the listen interface ip address) is actually checked every 30 secs for delugevpn.

Edited April 26, 2017 by binhex

JonathanM · April 26, 2017

1 hour ago, binhex said:

i dont set the external ip at all for deluge as it doesnt need/have this setting??, listen interface != external ip address, and this (as in the listen interface ip address) is actually checked every 30 secs for delugevpn.

Sorry, I just figured it was a generic VPN thing. Occasionally (twice a week or so) deluge will say everything is ok, but there is no traffic. Stop the container, start it back, and everything starts downloading. I assumed my VPN IP or port had changed but deluge hadn't gotten the message.

Wob76 · April 28, 2017

On 4/26/2017 at 10:21 PM, binhex said:

So i have code in place that will trigger the update of the configured external ip address used for rtorrent (in "rutorrent webui/bittorrent/ip host to report to tracker") every time there is a drop of the vpn tunnel, this is done via openvpn "up" script and should run every time the tunnel gets disconnected (due to vpn/isp dropout). Ive just had a look at the external ip my instance has and it matches what im seeing via the proxy, so i will keep an eye out for this occurring and dig into it if i see it happen.

Thanks binhex, it seems to work most of the time, just once every week or 2 it doesn't seem to update. I usually just check whenever I notice no traffic, sometimes it matches othertimes it seems to be a stale IP.

Wob

binhex · April 29, 2017

Sorry, I just figured it was a generic VPN thing. Occasionally (twice a week or so) deluge will say everything is ok, but there is no traffic. Stop the container, start it back, and everything starts downloading. I assumed my VPN IP or port had changed but deluge hadn't gotten the message.

That's odd the listen interface in deluge will be checked every 30 secs so little chance of stale entries. OK next time it happens could you please post the supervisord.log it might give me a clue as to what is going on.

Thanks.

Sent from my SM-G900F using Tapatalk

Fma965 · April 30, 2017

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/sbin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/etc/webapps/flood/node_modules/.bin:/usr/lib/node_modules/npm/bin/node-gyp-bin:/etc/webapps/flood/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle [email protected]~start: CWD: /etc/webapps/flood
11 silly lifecycle [email protected]~start: Args: [ '-c', 'node server/bin/www' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `node server/bin/www`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:194:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:194:7)
14 verbose stack     at maybeClose (internal/child_process.js:899:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /etc/webapps/flood
17 verbose Linux 4.4.0-72-generic
18 verbose argv "/usr/bin/node" "/usr/sbin/npm" "start"
19 verbose node v7.9.0
20 verbose npm  v4.5.0
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start: `node server/bin/www`
23 error Exit status 1
24 error Failed at the [email protected] start script 'node server/bin/www'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the flood package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error     node server/bin/www
24 error You can get information on how to open an issue for this project with:
24 error     npm bugs flood
24 error Or if that isn't available, you can get their info via:
24 error     npm owner ls flood
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]

Can't get Flood to work at all, looked in supervisor log but nothing of any use, dug deeper found this on the tmux session for flood. any help?

upon extensive testing it seems if i use the latest version straight away, the config files don't work, if i use a older version and let that older version generate the files then it works, even after i update the docker to the latest version, maybe this will help solve the problem with flood.

let me know if need any further info.

Edited April 30, 2017 by Fma965

MyKroFt · May 1, 2017

need some direction on where to look...

AFTER the last docker update - my forwarded port from airvpn will no longer get thru to the docker. The docker startup logs says its using the correct port, but when I got to airvpn and do a port forward test it does not connected - hence my downloads are now about 70k

what should I look for?

Thanks

Myk

btw, config has not changed in the last 2+ months - just docker updates when it states there is on - the delugevpn docker to airvpn forwarded port is working just fine....

binhex · May 2, 2017

15 hours ago, MyKroFt said:

need some direction on where to look...

AFTER the last docker update - my forwarded port from airvpn will no longer get thru to the docker. The docker startup logs says its using the correct port, but when I got to airvpn and do a port forward test it does not connected - hence my downloads are now about 70k

what should I look for?

Thanks

Myk

btw, config has not changed in the last 2+ months - just docker updates when it states there is on - the delugevpn docker to airvpn forwarded port is working just fine....

The changes made shouldn't cause any issues with the incoming port, im assuming you've tried restarting the container?, if you want to try reverting back then take a look at my sig general docker faq q11 to rollback to the previous tagged release.

edit - just so you are aware im doing a new build now, this is to do with fixing up alternative webui, "flood" and not to do with your issue.

Edited May 2, 2017 by binhex

binhex · May 5, 2017

On 2017-4-28 at 2:05 AM, Wob76 said:

Thanks binhex, it seems to work most of the time, just once every week or 2 it doesn't seem to update. I usually just check whenever I notice no traffic, sometimes it matches othertimes it seems to be a stale IP.

Wob

hi Wob, can you please do the same if this occurs, i would like to see whats going on in the log, you might need to turn on debug:-

"OK next time it happens could you please post the supervisord.log it might give me a clue as to what is going on."

binhex · May 5, 2017

On 2017-4-30 at 6:23 PM, Fma965 said:


0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/sbin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/etc/webapps/flood/node_modules/.bin:/usr/lib/node_modules/npm/bin/node-gyp-bin:/etc/webapps/flood/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle [email protected]~start: CWD: /etc/webapps/flood
11 silly lifecycle [email protected]~start: Args: [ '-c', 'node server/bin/www' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `node server/bin/www`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:194:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:194:7)
14 verbose stack     at maybeClose (internal/child_process.js:899:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /etc/webapps/flood
17 verbose Linux 4.4.0-72-generic
18 verbose argv "/usr/bin/node" "/usr/sbin/npm" "start"
19 verbose node v7.9.0
20 verbose npm  v4.5.0
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start: `node server/bin/www`
23 error Exit status 1
24 error Failed at the [email protected] start script 'node server/bin/www'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the flood package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error     node server/bin/www
24 error You can get information on how to open an issue for this project with:
24 error     npm bugs flood
24 error Or if that isn't available, you can get their info via:
24 error     npm owner ls flood
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]

Can't get Flood to work at all, looked in supervisor log but nothing of any use, dug deeper found this on the tmux session for flood. any help?

upon extensive testing it seems if i use the latest version straight away, the config files don't work, if i use a older version and let that older version generate the files then it works, even after i update the docker to the latest version, maybe this will help solve the problem with flood.

let me know if need any further info.

Just a FYI the flood ui got rebuilt again in the last image, it works fine for me, give it a spin (if you havent already).

Fma965 · May 5, 2017

Just now, binhex said:

Just a FYI the flood ui got rebuilt again in the last image, it works fine for me, give it a spin (if you havent already).

I was having strange issues with rtorrent so moved to transmission vpn docker but if you still want me to test it i can do.

Thanks.

poots · May 7, 2017

I've just recently started having problems where torrents communicated from Sonarr/CouchPotato are added paused and can't be started, there seems to be no available peers. The same torrents will go fine if using BlackHole.

I'm connecting through a VPN, and I have the little "49160: Port is closed". I'm not sure if that's auspicious, but I'm not sure where I forward ports (is it my router? or VPN?). The setup was working up until recently.

Has anyone had similar symptoms?

Kir · May 10, 2017

Could someone direct me at the instructions on how to get this docker to work with IPVanish? Is it feasible at all they don't seem to support port forwarding?

Thank you!

binhex · May 10, 2017

Could someone direct me at the instructions on how to get this docker to work with IPVanish? Is it feasible at all they don't seem to support port forwarding?

Thank you!

If they don't support port forwarding then no it's not feasible

Sent from my SM-G900F using Tapatalk

Kir · May 12, 2017

Hmm, just read some people managed to get IPVanish to work with torrents.

JonathanM · May 12, 2017

45 minutes ago, Kir said:

Hmm, just read some people managed to get IPVanish to work with torrents.

Working is a very vague term. It will probably download some torrents ok, and will upload some to the clients that you are downloading from while connected, but you would not be able to seed, and as soon as you finish the download all connections will drop. Many torrents probably won't work at all, depending on the tracker and peers.

inkubux · May 14, 2017

Thanks for your great docker.

I do have some issues with the webui.

I'm able to see the webui but I have RCP errors, here is a screenshot

I also attached a log

2017-05-14 16:17:46.590326 [info] Starting Supervisor...
2017-05-14 16:17:47,878 CRIT Set uid to user 0
2017-05-14 16:17:47,879 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
2017-05-14 16:17:47,886 INFO supervisord started with pid 7
2017-05-14 16:17:48,896 INFO spawned: 'flood-script' with pid 119
2017-05-14 16:17:48,900 INFO spawned: 'start-script' with pid 120
2017-05-14 16:17:48,903 INFO spawned: 'rtorrent-script' with pid 121
2017-05-14 16:17:48,906 INFO spawned: 'rutorrent-script' with pid 122
2017-05-14 16:17:48,910 INFO spawned: 'privoxy-script' with pid 123
2017-05-14 16:17:48,922 DEBG 'flood-script' stdout output:
[info] Flood not enabled, skipping starting Flood Web UI

2017-05-14 16:17:48,923 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-14 16:17:48,923 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-14 16:17:48,923 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-14 16:17:48,924 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-14 16:17:48,925 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-14 16:17:48,926 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47988725084960 for <Subprocess at 47988723550760 with name flood-script in state RUNNING> (stderr)>
2017-05-14 16:17:48,934 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47988725087552 for <Subprocess at 47988723550760 with name flood-script in state RUNNING> (stdout)>
2017-05-14 16:17:48,935 INFO exited: flood-script (exit status 0; expected)
2017-05-14 16:17:48,935 DEBG received SIGCLD indicating a child quit
2017-05-14 16:17:48,936 DEBG 'rtorrent-script' stdout output:
[info] rTorrent config file already exists, skipping copy

2017-05-14 16:17:48,938 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2017-05-14 16:17:48,941 DEBG 'rtorrent-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2017-05-14 16:17:48,945 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2017-05-14 16:17:48,946 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 47988725014040 for <Subprocess at 47988723551696 with name privoxy-script in state RUNNING> (stderr)>
2017-05-14 16:17:48,946 DEBG fd 27 closed, stopped monitoring <POutputDispatcher at 47988644563640 for <Subprocess at 47988723551696 with name privoxy-script in state RUNNING> (stdout)>
2017-05-14 16:17:48,946 INFO exited: privoxy-script (exit status 0; expected)
2017-05-14 16:17:48,947 DEBG received SIGCLD indicating a child quit
2017-05-14 16:17:48,983 DEBG 'start-script' stdout output:
[info] VPN default certs defined, copying to /config/openvpn/...

2017-05-14 16:17:49,007 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2017-05-14 16:17:49,021 DEBG 'start-script' stderr output:
dos2unix:
2017-05-14 16:17:49,022 DEBG 'start-script' stderr output:
converting file /config/openvpn/openvpn.ovpn to Unix format...

2017-05-14 16:17:49,168 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2017-05-14 16:17:49,179 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-05-14 16:17:49,187 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2017-05-14 16:17:49,196 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-05-14 16:17:49,205 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2017-05-14 16:17:49,225 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.0/24 as route via docker eth0

2017-05-14 16:17:49,227 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2017-05-14 16:17:49,229 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0

2017-05-14 16:17:49,230 DEBG 'start-script' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7
192.168.2.0/24 via 172.17.0.1 dev eth0

2017-05-14 16:17:49,231 DEBG 'start-script' stdout output:
--------------------

2017-05-14 16:17:49,280 DEBG 'start-script' stdout output:
[warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'
[info] Ubuntu users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

2017-05-14 16:17:49,280 DEBG 'start-script' stdout output:
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/iptable_mangle.ko'

2017-05-14 16:17:49,332 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2017-05-14 16:17:49,650 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-05-14 16:17:49,655 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 udp -m udp --sport 1198 -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.2.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -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 udp -m udp --dport 1198 -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.2.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2017-05-14 16:17:49,657 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2017-05-14 16:17:49,935 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-05-14 16:17:51,810 DEBG 'rtorrent-script' stdout output:
[info] rTorrent not running
[info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.39.10.6 different, marking for reconfigure

2017-05-14 16:17:58,087 DEBG 'rtorrent-script' stdout output:
[info] Removing any rtorrent session lock files left over from the previous run...

2017-05-14 16:17:58,091 DEBG 'rtorrent-script' stdout output:
[info] Attempting to start rTorrent...

2017-05-14 16:17:58,095 DEBG 'rtorrent-script' stdout output:
Script started, file is /home/nobody/typescript

2017-05-14 16:17:58,143 DEBG 'rtorrent-script' stdout output:
Script done, file is /home/nobody/typescript

2017-05-14 16:17:58,292 DEBG 'rutorrent-script' stdout output:
[info] rtorrent started, setting up rutorrent...
[info] Setting PHP timezone to UTC...

2017-05-14 16:17:58,324 DEBG 'rutorrent-script' stdout output:
[info] nginx cert files already exists, skipping copy

2017-05-14 16:17:58,327 DEBG 'rutorrent-script' stdout output:
[info] nginx security file already exists, skipping copy
[info] nginx config file already exists, skipping copy

2017-05-14 16:17:58,331 DEBG 'rutorrent-script' stdout output:
[info] rutorrent conf folder already exists, skipping copy

2017-05-14 16:17:58,337 DEBG 'rutorrent-script' stdout output:
[info] rutorrent share folder already exists, skipping copy

2017-05-14 16:17:58,343 DEBG 'rutorrent-script' stdout output:
[info] copying rutorrent plugins to container...

2017-05-14 16:17:58,376 DEBG 'rutorrent-script' stdout output:
[info] starting php-fpm...

2017-05-14 16:17:58,429 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

2017-05-14 16:17:58,441 DEBG 'rutorrent-script' stdout output:
[info] starting nginx...

2017-05-14 16:17:59,172 DEBG 'rtorrent-script' stdout output:
[info] rTorrent started

2017-05-14 16:17:59,173 DEBG 'rtorrent-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2017-05-14 16:17:59,183 DEBG 'rtorrent-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

2017-05-14 16:17:59,194 DEBG 'rtorrent-script' stdout output:
[info] nginx running
[info] Initialising ruTorrent plugins...

2017-05-14 16:17:59,287 DEBG 'rtorrent-script' stdout output:
[info] ruTorrent plugins initialised

2017-05-14 16:18:03,775 DEBG 'rutorrent-script' stderr output:
2017/05/14 16:18:03 [error] 919#919: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.2.32, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.2.29:9080", referrer: "http://192.168.2.29:9080/"


2017-05-14 16:18:32,126 DEBG 'rutorrent-script' stderr output:
2017/05/14 16:18:32 [error] 919#919: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.2.32, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.2.29:9080", referrer: "http://192.168.2.29:9080/"


2017-05-14 16:18:46,122 DEBG 'rutorrent-script' stderr output:
2017/05/14 16:18:46 [error] 919#919: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.2.32, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.2.29:9080", referrer: "http://192.168.2.29:9080/"

Thanks for your help. In the meantime I will use deluge, but I fint it a bit slow.

binhex · May 15, 2017

16 hours ago, inkubux said:

I'm able to see the webui but I have RCP errors, here is a screenshot

very odd, ive had no RCP2 errors at all, infact this is my full time download client at the mo and has been working well, ok can you try just stopping the container, delete all files/folders on /config and start it up to force a reset, see if this then allows you to connect to rtorrent (webui looks ok).

inkubux · May 15, 2017

5 hours ago, binhex said:

very odd, ive had no RCP2 errors at all, infact this is my full time download client at the mo and has been working well, ok can you try just stopping the container, delete all files/folders on /config and start it up to force a reset, see if this then allows you to connect to rtorrent (webui looks ok).

Thanks it actually resolved my issues. I deleted the config files, and recreated the container and now it works flawlessly. It's amazing how fast it is compared to deluge on the VPN :), almost double for me.

Thanks

binhex · May 15, 2017

Thanks it actually resolved my issues. I deleted the config files, and recreated the container and now it works flawlessly. It's amazing how fast it is compared to deluge on the VPN , almost double for me.

Thanks

Impressive isn't it, it doubled my DL/UL rates too.

Sent from my SM-G900F using Tapatalk

Wob76 · May 16, 2017

On 5/5/2017 at 9:06 PM, binhex said:

hi Wob, can you please do the same if this occurs, i would like to see whats going on in the log, you might need to turn on debug:-

"OK next time it happens could you please post the supervisord.log it might give me a clue as to what is going on."

Hi binhex, sorry for the delays, I lost internet for a week and only got around to testing this again.

I enabled debuging, I just did a restart as a torrent was "stuck" and noticed the IP did not update correctly. I can see the correct ip in the debug logs.

2017-05-16 10:54:25,114 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '46.19.142.226'

But the IP showing in rutorrent is still the old IP.

Logs are pretty big with debuging so I have just included a chunk from the end, I hope that is enough, I have changed out my VPN details with xxxx's

Wob

supervisord.txt

inkubux · May 16, 2017

Hi Thanks again for your docker, I've observed a high CPU usage when using it though between 50% to 100% when downloading. When not downloading it goes back to about 4% to 8%

Is anybody having this issue ?

Thanks

RallyAK · May 18, 2017

After upgrading to the latest unRAID OS (6.3.4) I'm no longer able to login to the ruTorrent web gui.

According to the log, the docker appears to be starting fine but I'm getting time out errors when logging in to...

http://<host ip>:9080/

https://<host ip>:9443/

Flood and Privoxy access is also broken.

http://<host ip>:3000/

http://<host ip>:8118

I've restarted the docker and server several times, and have tried using different VPN servers from my primary provider and AirVPN, but I'm still having the same issue.

Here's a portion of my log, IP's and credentials have been edited, let me know if you need anything else to help troubleshoot.

EDIT: I'm able to access the gui if I shut of VPN but prefer not to run that way for very long, for obvious reasons. : |

Anyone else having the same issue?

supervisord.txt

Edited May 20, 2017 by RallyAK
added log

Wob76 · May 18, 2017

On 5/16/2017 at 11:01 AM, Wob76 said:

Hi binhex, sorry for the delays, I lost internet for a week and only got around to testing this again.

I enabled debuging, I just did a restart as a torrent was "stuck" and noticed the IP did not update correctly. I can see the correct ip in the debug logs.

2017-05-16 10:54:25,114 DEBG 'rtorrent-script' stdout output:
[debug] External IP address from tunnel is '46.19.142.226'

But the IP showing in rutorrent is still the old IP.

Logs are pretty big with debuging so I have just included a chunk from the end, I hope that is enough, I have changed out my VPN details with xxxx's

Wob

supervisord.txt

@binhex Any ideas, happened again today, logs look pretty much the same, I can see it detecting a new external IP, but can't see it taking any action.

RallyAK · May 19, 2017

On 5/6/2017 at 6:00 PM, poots said:

I've just recently started having problems where torrents communicated from Sonarr/CouchPotato are added paused and can't be started, there seems to be no available peers. The same torrents will go fine if using BlackHole.

I'm connecting through a VPN, and I have the little "49160: Port is closed". I'm not sure if that's auspicious, but I'm not sure where I forward ports (is it my router? or VPN?). The setup was working up until recently.

Has anyone had similar symptoms?

I'm having a similar issue, after one of the updates a couple weeks ago my listening port went down and I started having peering issues with a number of users. I've tried changing ports on the docker, config and my router but can't get the port to stay up. Not sure what to try next, have you had any luck resolving the issue on your end?

[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