[Support] binhex - DelugeVPN


8722 posts in this topic Last Reply

Recommended Posts

18 minutes ago, binhex said:


I've never seen or heard of this, how are you identifying the country location?

Sent from my SM-G900F using Tapatalk
 

Nevermind it seems to go through the correct VPN gateway 

 

Whois database/query at a torrent ip check site detects the ip as Russia even though it is infact Netherlands.  

Edited by fc0712
Link to post
  • Replies 8.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A n

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

Posted Images

@binhex apologies if this has been mentioned in this thread (wish there was a search within thread feature). Facing issue with Web UI constantly breaks connection, with about 300 Torrents running. If i use the web url, it will just break connection w/o doing anything "The connection to the web-server has been lost!". If i use a Thin client, the connection will stay up longer, unless I change something i.e. remove a torrent, then same results. When I open connection manager, it just shows a grey plug, if i hit refresh or connect again, it will show a red dot for some time, then it will go back green eventually, and I can connect again.


 

The below example, came back on its own after abount a minute, but, no new connect message. 


[INFO    ] 10:49:48 rpcserver:206 Deluge Client connection made from: *:61030 -- Thin client
[INFO    ] 10:49:50 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. -- clicked remove torrent
[INFO    ] 10:50:27 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:50:27 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:50:43 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:50:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:51:42 torrentmanager:635 Torrent * removed by user: * -- Finally removed torrent 
[INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:52:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:52:51 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:52:55 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:52:55 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:54:17 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:54:17 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:54:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:55:49 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:55:49 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:56:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:56:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:56:44 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:56:44 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:57:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:57:52 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:58:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:58:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:58:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:59:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:59:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:59:05 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:59:05 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:59:14 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:59:14 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 11:00:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:00:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume

 

 

Is this just me being impatient, or should I really be able to remove torrents, or make changes, with a quicker response time?

 

 

 

 

 

 

 

 

 

\

Link to post
5 minutes ago, The_Doctor said:

@binhex apologies if this has been mentioned in this thread (wish there was a search within thread feature). Facing issue with Web UI constantly breaks connection, with about 300 Torrents running. If i use the web url, it will just break connection w/o doing anything "The connection to the web-server has been lost!". If i use a Thin client, the connection will stay up longer, unless I change something i.e. remove a torrent, then same results. When I open connection manager, it just shows a grey plug, if i hit refresh or connect again, it will show a red dot for some time, then it will go back green eventually, and I can connect again.


 


The below example, came back on its own after abount a minute, but, no new connect message. 


[INFO    ] 10:49:48 rpcserver:206 Deluge Client connection made from: *:61030 -- Thin client
[INFO    ] 10:49:50 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. -- clicked remove torrent
[INFO    ] 10:50:27 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:50:27 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:50:43 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:50:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:51:42 torrentmanager:635 Torrent * removed by user: * -- Finally removed torrent 
[INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:52:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:52:51 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:52:55 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:52:55 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:54:17 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:54:17 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:54:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:55:49 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:55:49 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:56:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:56:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:56:44 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:56:44 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:57:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:57:52 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:58:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:58:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:58:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 10:59:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:59:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:59:05 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:59:05 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 10:59:14 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 10:59:14 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 11:00:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:00:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume

 

 

Is this just me being impatient, or should I really be able to remove torrents, or make changes, with a quicker response time?

 

 

 

 

 

 

 

 

 

\

 

 

 

 

Here is another example from the thin client. Im trying to remove 8 seeders, and the connection from the thin client goes grey, but no connection drop in logs.

Its almost like the connection drops until all the requested changes are completed, but taking over a minute to remove just one torrent?

 

 

In this example the last part of the log is when the Thin client started to respond again. It seems once again, only after it completed the requested task.

 

[INFO    ] 11:10:26 rpcserver:206 Deluge Client connection made from: *:64030
[INFO    ] 11:11:06 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:11:06 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 11:11:23 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:12:25 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:12:25 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 11:13:56 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:13:56 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:14:58 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:14:58 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:14:58 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:16:00 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:16:00 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:16:00 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:16:58 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:16:58 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[WARNING ] 11:16:58 torrent:987 Unable to delete the torrent file: [Errno 2] No such file or directory: '/config/state/8c303f2bd419951f8f9c68678689a543860eebbc.torrent'
[INFO    ] 11:16:58 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:18:01 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:18:01 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:18:01 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:19:03 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:19:03 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:19:03 torrentmanager:737 Saving the state at: /config/state/torrents.state

INFO    ] 11:20:03 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:20:03 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:20:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:21:03 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:21:03 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:21:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:22:04 torrentmanager:635 Torrent * removed by user: *
[INFO    ] 11:22:04 torrentmanager:737 Saving the state at: /config/state/torrents.state
[INFO    ] 11:23:50 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:23:51 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
[INFO    ] 11:23:53 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
[INFO    ] 11:23:53 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume

 

 

 

 

 

 

 

 

\

Link to post

Hello,

 

I've just installed this docker (I'm not an advanced docker user). I have reviewed various articles/videos and believe that I've set it up correctly. Could someone take a look at the log below? (I've replaced my username and password with xxx).

 

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

2017-05-31 20:53:52.005419 [info] Host is running unRAID
2017-05-31 20:53:52.041658 [info] System information Linux 08b4d2999eb0 4.9.30-unRAID #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017 x86_64 GNU/Linux
2017-05-31 20:53:52.088792 [info] PUID defined as '99'
2017-05-31 20:53:52.127630 [info] PGID defined as '100'
2017-05-31 20:53:52.172138 [info] UMASK defined as '000'
2017-05-31 20:53:52.217192 [info] Permissions already set for volume mappings
2017-05-31 20:53:52.261187 [info] VPN_ENABLED defined as 'yes'
2017-05-31 20:53:52.301476 [info] VPN_PROV defined as 'pia'
2017-05-31 20:53:52.345228 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'
2017-05-31 20:53:52.383023 [info] VPN_PORT defined as '1198'
2017-05-31 20:53:52.427223 [info] VPN_PROTOCOL defined as 'udp'
2017-05-31 20:53:52.467936 [info] LAN_NETWORK defined as '192.168.1.0/24'
2017-05-31 20:53:52.512362 [info] NAME_SERVERS defined as '8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177'
2017-05-31 20:53:52.554658 [info] VPN_USER defined as 'xxx'
2017-05-31 20:53:52.593504 [info] VPN_PASS defined as 'xxx'
2017-05-31 20:53:52.629806 [info] VPN_DEVICE_TYPE defined as 'tun'
2017-05-31 20:53:52.669655 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2017-05-31 20:53:52.717715 [info] STRONG_CERTS defined as 'no'
2017-05-31 20:53:52.759200 [info] ENABLE_PRIVOXY defined as 'no'
2017-05-31 20:53:52.794935 [info] Setting permissions on files/folders inside container...
2017-05-31 20:53:53,257 CRIT Set uid to user 0
2017-05-31 20:53:53,257 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2017-05-31 20:53:53,260 INFO supervisord started with pid 6
2017-05-31 20:53:54,261 INFO spawned: 'start-script' with pid 111
2017-05-31 20:53:54,262 INFO spawned: 'deluge-script' with pid 112
2017-05-31 20:53:54,264 INFO spawned: 'deluge-web-script' with pid 113
2017-05-31 20:53:54,265 INFO spawned: 'privoxy-script' with pid 114
2017-05-31 20:53:54,271 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2017-05-31 20:53:54,271 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-31 20:53:54,271 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-31 20:53:54,271 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-31 20:53:54,271 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-31 20:53:54,273 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2017-05-31 20:53:54,274 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2017-05-31 20:53:54,276 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2017-05-31 20:53:54,277 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 47035645370024 for <Subprocess at 47035644270208 with name privoxy-script in state RUNNING> (stderr)>
2017-05-31 20:53:54,278 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 47035644203088 for <Subprocess at 47035644270208 with name privoxy-script in state RUNNING> (stdout)>
2017-05-31 20:53:54,278 DEBG 'start-script' stdout output:
[info] VPN default certs defined, copying to /config/openvpn/...

2017-05-31 20:53:54,279 INFO exited: privoxy-script (exit status 0; expected)
2017-05-31 20:53:54,280 DEBG received SIGCLD indicating a child quit
2017-05-31 20:53:54,280 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2017-05-31 20:53:54,286 DEBG 'start-script' stderr output:
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...

2017-05-31 20:53:54,335 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2017-05-31 20:53:54,337 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2017-05-31 20:53:54,341 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2017-05-31 20:53:54,347 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2017-05-31 20:53:54,352 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2017-05-31 20:53:54,360 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2017-05-31 20:53:54,361 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2017-05-31 20:53:54,362 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.5 
192.168.1.0/24 via 172.17.0.1 dev eth0 

2017-05-31 20:53:54,362 DEBG 'start-script' stdout output:
--------------------

2017-05-31 20:53:54,366 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2017-05-31 20:53:54,418 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2017-05-31 20:53:54,478 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2017-05-31 20:53:54,480 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 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -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 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -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-31 20:53:54,481 DEBG 'start-script' stdout output:
--------------------

2017-05-31 20:53:54,481 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2017-05-31 20:53:54,488 DEBG 'start-script' stdout output:
[info] OpenVPN started

Any help would be much appreciated. If required my local IP is: 192.168.1.x and it appears the CIDR is correct. The WebUI appears to not load despite triple checking credentials.

 

Thanks!

Link to post
2017-05-31 15:44:48,733 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP x.x.x.x different, marking for reconfigur

Just trying to setup deluge-vpn and having the above issue/error (at least from what I can tell; also unable to access webui however I think that may be because of the error above. 

Link to post
14 hours ago, The_Doctor said:

apologies if this has been mentioned in this thread (wish there was a search within thread feature). Facing issue with Web UI constantly breaks connection, with about 300 Torrents running. If i use the web url, it will just break connection w/o doing anything "The connection to the web-server has been lost!". If i use a Thin client, the connection will stay up longer, unless I change something i.e. remove a torrent, then same results. When I open connection manager, it just shows a grey plug, if i hit refresh or connect again, it will show a red dot for some time, then it will go back green eventually, and I can connect again.

 

This sounds more like an issue with Deluge itself than the containerisation of Deluge, you're probably better off posting this on the Deluge forum, you will need to supply all traceback's (if there are any in the log, i have no idea how deluge deals with 300+ torrents, it could well not cope well with that quantity of torrents so another option is to try rtorrentvpn, this has a track record of being able to cope with a lot of torrents (1000+) and still be reasonably reactive to changes.

Link to post
12 hours ago, thejamkel said:

Any help would be much appreciated. If required my local IP is: 192.168.1.x and it appears the CIDR is correct. The WebUI appears to not load despite triple checking credentials.

 

my sig, help link

Link to post
12 hours ago, paramehdic said:

2017-05-31 15:44:48,733 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP x.x.x.x different, marking for reconfigur

Just trying to setup deluge-vpn and having the above issue/error (at least from what I can tell; also unable to access webui however I think that may be because of the error above. 

 

the above isn't either an issue or error, my sig help link.

Link to post
2 minutes ago, thejamkel said:

Hi there,

 

Thank you for the response. I've read through the FAQ and believe i have done everything correctly. I'm not sure what to do next.

 

-James

 

click on the link in my sig called 'help' and do the steps.

Link to post
13 minutes ago, binhex said:

 

click on the link in my sig called 'help' and do the steps.

 

Hi,

 

I have ensured I applied the IPtables config then rebooted the server. Reinstalled the docker with debug set to true. At the current time in the appdata directory only openvpn seems to be present. I do not see any Deluge related files.

 

Log file below: I waited 10 minutes before taking a paste.

 

https://hastebin.com/qowokequxi.scala

 

Thanks so much for taking the time.

 

-James

Link to post
3 minutes ago, thejamkel said:

 

Hi,

 

I have ensured I applied the IPtables config then rebooted the server. Reinstalled the docker with debug set to true. At the current time in the appdata directory only openvpn seems to be present. I do not see any Deluge related files.

 

Log file below: I waited 10 minutes before taking a paste.

 

https://hastebin.com/qowokequxi.scala

 

Thanks so much for taking the time.

 

-James

 

you're a victim of ISP DNS hijacking, basically BT is redirecting certain DNS queries to their crappy webpage, you can see this via the dns query:-

 

2017-06-01 09:35:47,422 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint nl.privateinternetaccess.com

2017-06-01 09:35:47,440 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 48522
;; flags: qr rd ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; nl.privateinternetaccess.com.	IN	A

;; ANSWER SECTION:
nl.privateinternetaccess.com.	30	IN	A	213.120.234.114
nl.privateinternetaccess.com.	30	IN	A	213.120.234.150

 

in short nl.privateinternetaccess.com does NOT resolve to IP address 213.120.234.114, that is a BT owned IP address, you need to either turn off "BT Protect" or change the name server your router is pointing at to something like google (8.8.8.8 and 8.8.4.4.) and all your hosts on your lan too.

 

click here for details http://213.120.234.114/

Link to post
1 minute ago, binhex said:

 

you're a victim of ISP DNS hijacking, basically BT is redirecting certain DNS queries to their crappy webpage, you can see this via the dns query:-

 


2017-06-01 09:35:47,422 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint nl.privateinternetaccess.com

2017-06-01 09:35:47,440 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 48522
;; flags: qr rd ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; nl.privateinternetaccess.com.	IN	A

;; ANSWER SECTION:
nl.privateinternetaccess.com.	30	IN	A	213.120.234.114
nl.privateinternetaccess.com.	30	IN	A	213.120.234.150

 

in short nl.privateinternetaccess.com does NOT resolve to IP address 213.120.234.114, that is a BT owned IP address, you need to either turn off "BT Protect" or change the name server your router is pointing at to something like google (8.8.8.8 and 8.8.4.4.) and all your hosts on your lan too.

 

click here for details http://213.120.234.114/

Awesome. Thank you for taking a look. I will switch off BT protect (I didnt know it was enabled). The desktop PIA client was working so i missed reading into that.

 

Thanks again. On a side note will you be publishing an NZBget vpn docker? I tend to use your dockers as they are always reliable.

 

-James

Link to post
11 hours ago, binhex said:

 

This sounds more like an issue with Deluge itself than the containerisation of Deluge, you're probably better off posting this on the Deluge forum, you will need to supply all traceback's (if there are any in the log, i have no idea how deluge deals with 300+ torrents, it could well not cope well with that quantity of torrents so another option is to try rtorrentvpn, this has a track record of being able to cope with a lot of torrents (1000+) and still be reasonably reactive to changes.

 

 

I had a feeling this was more of a Deluge issue, but thought I would check with you first. Thanks for taking a look, ill bring it over to the other forum, and check out Rtorrentvpn.

Link to post

I feel like I'm 99% of the way to having this setup correctly but not quite there. Right now, all my downloads are stuck at 0.0% and 0 connections/peers/etc. Tracker status says connection refused typically. However, meta-data seems to download. The VPN is up and working (VPN enabled=yes) and I have access to the gui. I was able to connect to the container terminal docker -it.....yada yada. I can ping sites. A curl ipinfo.io/ip brings up an IP that is not my ISP provided IP.

 

As I said, 99% of the way there but no downloads, no peers. I've given it days, tried more popular files, etc. At this point, I suspect my VPN provider (VPNUnlimited) is blocking needed ports but I'm hoping to exhaust other obvious solutions before switching.

 

Thanks!

Link to post

Hi Coopooc

 

Does your VPN provider have incoming port restriction?  You might have to configure that in deluge. 

 

Without that setting, my deluge downloads but does not upload so it might not be that but food for thoughts.

Link to post
On 5/31/2017 at 4:09 PM, paramehdic said:

2017-05-31 15:44:48,733 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP x.x.x.x different, marking for reconfigur

Just trying to setup deluge-vpn and having the above issue/error (at least from what I can tell; also unable to access webui however I think that may be because of the error above. 

I figured out that if you use us-newyorkcity.privateinternetaccess.com it will hang at the above message, once I switched to nl or ca pia servers working fine.

Link to post

Hi @binhex

 

my VPN provider released an updated certificate and I just tried to update it here.

The openvpn protocol is TCP-CLIENT 

But when I define this in the VPN_PROTOCOL variable the iptables command does not like it.

iptables v1.6.1: unknown protocol "tcp-client" specified

When I change it to TCP the openvpn command complains:

[debug] OpenVPN command line '/usr/bin/openvpn --cd /config/openvpn --config /config/openvpn/swissvpn.ovpn --daemon --dev tun0 --remote connect.swissvpn.net 1194  --proto tcp --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --setenv VPN_PROV custom --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart --auth-user-pass credentials.conf --log-append /config/supervisord.log'
Options error: --proto tcp is ambiguous in this context.  Please specify --proto tcp-server or --proto tcp-client
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4

I have now hardcoded the tcp-client value in your openvpn.sh script and defined VPN_PROTOCOL = tcp and that works.

The same variable needs to have two different values at different points in the scripts.

# define common command lne parameters for openvpn
openvpn_cli="/usr/bin/openvpn --cd /config/openvpn --config ${VPN_CONFIG} --daemon --dev ${VPN_DEVICE_TYPE}0 --remote ${VPN_REMOTE} ${VPN_PORT} --proto tcp-client --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --setenv VPN_PROV ${VPN_PROV} --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart"

But obviously that is not a permanent solution.

Any chance you could look into this sometime?

 

EDIT: if it helps, the provider is SWISSVPN.net

Edited by roland
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.