[Support] binhex - DelugeVPN


8421 posts in this topic Last Reply

Recommended Posts

Meh crap.  Boy did I just screw the pooch.  I had an old Docker container that I was fighting with (not working) and gave up on for a while.  The other day I decided to manually update the container to try again and didn't bother to look at the documentation.  The application seemed to run just fine.  When did the container change to allow traffic without the VPN?  That just bit me in the ass.  😲

 

I realize it's all my fault.  Like every bit.  But the nice thing about this container was that I could trust that nothing could leak out.  Using the same environmental variables I had with my old setup I didn't realize I wasn't protected.  Before if the VPN didn't work neither did Deluge.

 

I should have checked the new variables since it had been so long.  I should have probably tested the connection too.  Don't be a dumbass like me.

 

Ugh. 

Link to post
  • Replies 8.4k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

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

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

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

Meh crap.  Boy did I just screw the pooch.  I had an old Docker container that I was fighting with (not working) and gave up on for a while.  The other day I decided to manually update the container to try again and didn't bother to look at the documentation.  The application seemed to run just fine.  When did the container change to allow traffic without the VPN?  That just bit me in the ass.  
 
I realize it's all my fault.  Like every bit.  But the nice thing about this container was that I could trust that nothing could leak out.  Using the same environmental variables I had with my old setup I didn't realize I wasn't protected.  Before if the VPN didn't work neither did Deluge.
 
I should have checked the new variables since it had been so long.  I should have probably tested the connection too.  Don't be a dumbass like me.
 
Ugh. 
It hasn't changed, as long as VPN_ENABLED=yes then you will not be able to access the web UI unless the VPN is established, no IP leakage.

Sent from my EML-L29 using Tapatalk

Link to post
4 hours ago, binhex said:

It hasn't changed, as long as VPN_ENABLED=yes then you will not be able to access the web UI unless the VPN is established, no IP leakage.

Sent from my EML-L29 using Tapatalk
 

Hmmm...  That wasn't in my list of environmental variables from my old install from 1.5 years ago.  I most likely missed adding it back in the day when I was playing around.  I had it working perfectly at one time.  I then updated the Docker container eventually and everything fell apart and it stopped working for me.  Eventually I just gave up because I honestly don't torrent all that much.  The other day I felt like playing around with it again and I just carried over my existing settings.  At any rate it was my stupid mistake.  I'll give it a go again and try to be more careful.  😂

 

[EDIT]

 

Oh snap.  I just realized my variable list is so long that I didn't scroll down to the bottom.  It is there and it is set to yes.  It's entirely possible that the VPN credentials are wrong but that that shouldn't have caused the leak, right?  I did test it with IPMagnet after the fact and it's not using the VPN.

Edited by clambert
Link to post
Hmmm...  That wasn't in my list of environmental variables from my old install from 1.5 years ago.  I most likely missed adding it back in the day when I was playing around.  I had it working perfectly at one time.  I then updated the Docker container eventually and everything fell apart and it stopped working for me.  Eventually I just gave up because I honestly don't torrent all that much.  The other day I felt like playing around with it again and I just carried over my existing settings.  At any rate it was my stupid mistake.  I'll give it a go again and try to be more careful.  
 
[EDIT]
 
Oh snap.  I just realized my variable list is so long that I didn't scroll down to the bottom.  It is there and it is set to yes.  It's entirely possible that the VPN credentials are wrong but that that shouldn't have caused the leak, right?  I did test it with IPMagnet after the fact and it's not using the VPN.
If the credentials are wrong then the tunnel won't be established and thus the web ui and daemon won't start. What VPN provider are you using?

Sent from my EML-L29 using Tapatalk

Link to post



I did test it with IPMagnet after the fact and it's not using the VPN.


If it's still in this state then please post full log, I would love to see what is causing this, ideally with debug turned on.

Sent from my EML-L29 using Tapatalk

Link to post
1 hour ago, binhex said:


 

 


If it's still in this state then please post full log, I would love to see what is causing this, ideally with debug turned on.

Sent from my EML-L29 using Tapatalk
 

 

Ok, I already had debug set to true.  I just deleted the log to start fresh, started the container, went to IPMagnet, and downloaded the torrent.  The IP matched my public IP.  Attached is the log you requested.  I'm sure it's something stupid I've done.  Thanks for the help!

 

I'm using PIA and just checked the credentials.  They seem to be valid.  I have DelugeVPN running on my Synology NAS for what it's worth.

supervisord.log

Link to post
1 hour ago, clambert said:

Ok, I already had debug set to true.  I just deleted the log to start fresh, started the container, went to IPMagnet, and downloaded the torrent.  The IP matched my public IP.  Attached is the log you requested.  I'm sure it's something stupid I've done.  Thanks for the help!

 

I'm using PIA and just checked the credentials.  They seem to be valid.  I have DelugeVPN running on my Synology NAS for what it's worth.

supervisord.log

ok ive spotted the problem, in short you have defined VPN_ENABLED as 'Yes', but valid values are 'yes' or 'no' case sensitive!, the check then says - if value is not 'yes' then vpn is not enabled.

 

i can code around this by checking only for a case insensitive value of 'no' instead, thus unless the value is 'no' then always assume the value is 'yes', this should prevent anybody else from getting into this situation.

 

looking at your logs i think when you do set it to a valid value you will find the web ui wont load, as you have some reading to do to get this working on synology platform, i know this is working fine for synology users but there are hoops to jump through, sadly i cant remember what they are but im sure a post on a synology forum should get you the answer.

Link to post
19 minutes ago, binhex said:

ok ive spotted the problem, in short you have defined VPN_ENABLED as 'Yes', but valid values are 'yes' or 'no' case sensitive!, the check then says - if value is not 'yes' then vpn is not enabled.

 

i can code around this by checking only for a case insensitive value of 'no' instead, thus unless the value is 'no' then always assume the value is 'yes', this should prevent anybody else from getting into this situation.

 

looking at your logs i think when you do set it to a valid value you will find the web ui wont load, as you have some reading to do to get this working on synology platform, i know this is working fine for synology users but there are hoops to jump through, sadly i cant remember what they are but im sure a post on a synology forum should get you the answer.

Ah. Ok. Thanks for the info. All this kinda rings true to the problems I was having before when I gave up after updating. I just couldn't get the UI to load. My assumption at the time was that I couldn't get the Docker container running. Now that I know there is a solution out there I'll starting digging around in the Synology forums. For what it's worth changing the value to 'yes' does prevent my WebUI from loading. Thank you for the point in the right direction.

Link to post
1 minute ago, clambert said:

Ah. Ok. Thanks for the info. All this kinda rings true to the problems I was having before when I gave up after updating. I just couldn't get the UI to load. My assumption at the time was that I couldn't get the Docker container running. Now that I know there is a solution out there I'll starting digging around in the Synology forums. For what it's worth changing the value to 'yes' does prevent my WebUI from loading. Thank you for the point in the right direction.

no problems, its helped me too, as its another thing i can nail down to prevent this from happening to anybody else, so its all good.

Link to post

Is there any way to make the VPN connection in binhex - DelugeVPN cover the entire server instead of just Deluge?  More specifically, I would like to have the VPN tunnel also cover the Linux|Server Shout-IRC docker.  I know there are dockers and plugins that can be installed to cover the whole server, but they don't have a kill switch the way that binhex - DelugeVPN does and I don't want that to ever be exposed.

 

Thanks,

craigr

Link to post
2 hours ago, craigr said:

More specifically, I would like to have the VPN tunnel also cover the Linux|Server Shout-IRC docker

if what you are after is just using the vpn tunnel for this other container then your best bet is to use the built in proxy server (privoxy) and configure shout-irc to use that.

Link to post
On 12/29/2018 at 11:15 PM, Gog said:

What do you mean?  Your VPN provider is not using a username and password to authenticate you?

 

There is also this feature in your ovpn file that doesn't seem to be supported: block-outside-dns

 

I'm using a self hosted OpenVPN server. Certificate based authentication.

 

On 12/31/2018 at 11:41 AM, binhex said:

VPS is not supported im afraid, no LAN means no easy way to access deluge over public ip and prevent ip leakage. 

Don't know exactly what I did, but after fiddling around with open VPN server settings I got it working 😀

 

 

Link to post
20 hours ago, binhex said:

if what you are after is just using the vpn tunnel for this other container then your best bet is to use the built in proxy server (privoxy) and configure shout-irc to use that.

Sorry, maybe an obvious question, but not to me.  Is privoxy built into your deluge, Shout-IRC, or unRAID?  It sounds like a perfect solution, but I have never used it before...

 

Thanks and kind regards,

craigr

Link to post
Sorry, maybe an obvious question, but not to me.  Is privoxy built into your deluge, Shout-IRC, or unRAID?  It sounds like a perfect solution, but I have never used it before...
 
Thanks and kind regards,
craigr
Privoxy is built into all of the VPN enabled docker images I have produced, so yes it's built into delugevpn

Sent from my EML-L29 using Tapatalk

Link to post

I am pretty new to UnRAID and docker containers (only been using for a few weeks now).  I have everything setup but having issues with getting deluge to open the WebUI once I enable VPN and  Privoxy.  Once I enable these two options, and click on WebUI, I am getting the following message in Safari...

 

'Safari Can't Connect to the Server Safari can't open page "xxx.xxx.x.xxx:8112" because Safari can't connect to the server "xxx.xxx.x.xxx".'

 

The binhex-delugevpn configuration is as follows...

 

Host Port 1: 8112

Host Port 2: 58846

Host Port 3: 58946

Host Port 4: 58946

Host Port 5: 8118

Host Path 2: /mnt/user/Downloads/

Key 1: yes

Key 2: user id for PIA

Key 3: password for PIA

Key 4: blank

Key 5: blank

Key 6:  yes

Key 7: yes

Key 8:  xxx.xxx.x.0/24

Key 9: 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

Key 10: false

Key 11: 000

Key 12: 99

key 13: 100

 

In the supervisor.log file, this is what is listed...

 

[info] Deluge listening interface IP 0

[warn] Exit code 7 from curl != 0
[info] 11 retries left
[info] Retrying in 10 secs...

 

Would anyone know what the issue is?  Any help would be great.  

Edited by JohnSracic
Link to post

first I must admit that I haven't read all the posts here but I have a question.

 

I am about to install Deluge / VPN, Sonnar , Couch Potato and jackett onto my Unraid, but before I do. is there a way to test / check that all the traffic from the 4 Dockers are going through the VPN as the last thing I what is a letter from my ISP.

Link to post
1 minute ago, chris_netsmart said:

first I must admit that I haven't read all the posts here but I have a question.

 

I am about to install Deluge / VPN, Sonnar , Couch Potato and jackett onto my Unraid, but before I do. is there a way to test / check that all the traffic from the 4 Dockers are going through the VPN as the last thing I what is a letter from my ISP.

yes, point all apps at privoxy, then shutdown delugevpn, if any of the apps can still search then they arent configure correctly, if none of them can search then its working as designed - start delugevpn again.

Link to post
3 minutes ago, binhex said:

yes, point all apps at privoxy, then shutdown delugevpn, if any of the apps can still search then they arent configure correctly, if none of them can search then its working as designed - start delugevpn again.

thanks for the info,  I can see how I can test the app's but how can I test Deulge ?

 

Edited by chris_netsmart
Link to post

Hello all, pretty new here and new to all of this Docker stuff. Have an issue at the moment. I changed some drives around, and then ended up having to recreate my docker containers. Now, the deluge docker is saying that Permission is denied on the directories it's supposed to be using, but it's using the same directory links and such that it was using before I had to re-do my dockers. It's not making sense to me, and I'm unsure how to go about fixing it or getting help, so I wanted to post here and see if anyone would be able to help. 

 

I have used spaceinvaderone's videos, googled, can't find a working fix. Please let me know what I need to do to be able to get some help!

Link to post
25 minutes ago, trurl said:

First link in the Docker FAQ:

 

Thank you... I'm not real sure why I didn't notice that at first. Here is the Run and the Log.

 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='' -e 'VPN_PASS'='' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.50.0/24' -e 'NAME_SERVERS'='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' -e 'DEBUG'='true' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 

6f727dbce026583b38f4e32e10bdf156d85d25f8638383d16d4235693e2e80a7

The command finished successfully!

 

Quote

ErrorWarningSystemArrayLogin



2019-01-10 17:03:12,857 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2019-01-10 17:03:12,857 DEBG 'start-script' stdout output:
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.17.0.2 6f727dbce026

2019-01-10 17:03:12,860 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2019-01-10 17:03:12,863 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.2

2019-01-10 17:03:12,865 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2019-01-10 17:03:12,870 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2019-01-10 17:03:12,872 DEBG 'start-script' stdout output:
[info] Adding 192.168.50.0/24 as route via docker eth0

2019-01-10 17:03:12,873 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-01-10 17:03:12,873 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

2019-01-10 17:03:12,874 DEBG 'start-script' stdout output:
192.168.50.0/24 via 172.17.0.1 dev eth0

2019-01-10 17:03:12,874 DEBG 'start-script' stdout output:
--------------------
[debug] Modules currently loaded for kernel

2019-01-10 17:03:12,875 DEBG 'start-script' stdout output:
Module Size Used by
dm_mod 110592 1
dax 20480 1 dm_mod
xt_CHECKSUM 16384 1
iptable_mangle 16384 2
ipt_REJECT 16384 2
ebtable_filter 16384 0
ebtables 32768 1 ebtable_filter
veth 16384 0
ip6table_filter 16384 0
ip6_tables 24576 1 ip6table_filter
vhost_net 20480 1
tun 36864 4 vhost_net
vhost 32768 1 vhost_net
tap 20480 1 vhost_net
xt_nat 16384 11
ipt_MASQUERADE 16384 15
iptable_nat 16384 1
nf_conntrack_ipv4 16384 29
nf_defrag_ipv4 16384 1 nf_conntrack_ipv4
nf_nat_ipv4 16384 2 ipt_MASQUERADE,iptable_nat
iptable_filter 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle
nf_nat 24576 2 nf_nat_ipv4,xt_nat
xfs 663552 3
md_mod 49152 3
bonding 110592 0
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
coretemp 16384 0
kvm_intel 196608 8
kvm 364544 1 kvm_intel
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
crc32c_intel 24576 0
ghash_clmulni_intel 16384 0
pcbc 16384 0
aesni_intel 200704 0
aes_x86_64 20480 1 aesni_intel
crypto_simd 16384 1 aesni_intel
cryptd 20480 3 crypto_simd,ghash_clmulni_intel,aesni_intel
hid_logitech_hidpp 32768 0
i2c_i801 24576 0
i2c_core 40960 1 i2c_i801
glue_helper 16384 1 aesni_intel
intel_cstate 16384 0
ahci 40960 13
intel_uncore 102400 0
libahci 28672 1 ahci
mxm_wmi 16384 0
wmi 20480 1 mxm_wmi
intel_rapl_perf 16384 0
hid_logitech_dj 20480 0
pcc_cpufreq 16384 0
e1000e 180224 0
video 40960 0
backlight 16384 1 video
acpi_pad 20480 0
button 16384 0

2019-01-10 17:03:12,877 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle

2019-01-10 17:03:12,877 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-01-10 17:03:12,930 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-01-10 17:03:12,932 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 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.50.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.50.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -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 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.50.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.50.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2019-01-10 17:03:12,932 DEBG 'start-script' stdout output:
--------------------

2019-01-10 17:03:12,932 DEBG 'start-script' stdout output:
[debug] OpenVPN command line:- /usr/bin/openvpn --daemon --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'custom' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_REMOTE '96.9.247.11' --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/us2706.nordvpn.com.tcp.ovpn'
[info] Starting OpenVPN...

2019-01-10 17:03:12,946 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 WARNING: file 'credentials.conf' is group or others accessible
Thu Jan 10 17:03:12 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Thu Jan 10 17:03:12 2019 library versions: OpenSSL 1.1.1 11 Sep 2018, LZO 2.10

2019-01-10 17:03:12,946 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Thu Jan 10 17:03:12 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Thu Jan 10 17:03:12 2019 NOTE: --fast-io is disabled since we are not using UDP

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
[info] OpenVPN started
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Jan 10 17:03:12 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]96.9.247.11:443

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 Socket Buffers: R=[87380->87380] S=[65536->65536]
Thu Jan 10 17:03:12 2019 Attempting to establish TCP connection with [AF_INET]96.9.247.11:443 [nonblock]

2019-01-10 17:03:13,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:13 2019 TCP connection established with [AF_INET]96.9.247.11:443
Thu Jan 10 17:03:13 2019 TCP_CLIENT link local: (not bound)
Thu Jan 10 17:03:13 2019 TCP_CLIENT link remote: [AF_INET]96.9.247.11:443

2019-01-10 17:03:13,983 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:13 2019 TLS: Initial packet from [AF_INET]96.9.247.11:443, sid=3e0e8ba8 d7250e7a

2019-01-10 17:03:14,141 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2019-01-10 17:03:14,141 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA3

2019-01-10 17:03:14,141 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 VERIFY KU OK
Thu Jan 10 17:03:14 2019 Validating certificate extended key usage
Thu Jan 10 17:03:14 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Thu Jan 10 17:03:14 2019 VERIFY EKU OK
Thu Jan 10 17:03:14 2019 VERIFY OK: depth=0, CN=us2706.nordvpn.com

2019-01-10 17:03:14,385 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Thu Jan 10 17:03:14 2019 [us2706.nordvpn.com] Peer Connection Initiated with [AF_INET]96.9.247.11:443

2019-01-10 17:03:15,528 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 SENT CONTROL [us2706.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2019-01-10 17:03:15,655 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,sndbuf 524288,rcvbuf 524288,explicit-exit-notify,comp-lzo no,route-gateway 10.7.7.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.7.7.2 255.255.255.0,peer-id 0,cipher AES-256-GCM'

2019-01-10 17:03:15,655 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --explicit-exit-notify can only be used with --proto udp
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: compression parms modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Thu Jan 10 17:03:15 2019 Socket Buffers: R=[367360->1048576] S=[87040->1048576]
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --ifconfig/up options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: route options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: route-related options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: peer-id set
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: adjusting link_mtu to 1659
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: data channel crypto options modified
Thu Jan 10 17:03:15 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu Jan 10 17:03:15 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jan 10 17:03:15 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jan 10 17:03:15 2019 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02

2019-01-10 17:03:15,655 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 TUN/TAP device tun0 opened

2019-01-10 17:03:15,656 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 TUN/TAP TX queue length set to 100
Thu Jan 10 17:03:15 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Jan 10 17:03:15 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-01-10 17:03:15,656 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip addr add dev tun0 10.7.7.2/24 broadcast 10.7.7.255

2019-01-10 17:03:15,657 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /root/openvpnup.sh tun0 1500 1587 10.7.7.2 255.255.255.0 init

2019-01-10 17:03:15,659 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip route add 96.9.247.11/32 via 172.17.0.1

2019-01-10 17:03:15,660 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.7.7.1

2019-01-10 17:03:15,661 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:15,661 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:15,662 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.7.7.1

2019-01-10 17:03:15,663 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 Initialization Sequence Completed

2019-01-10 17:03:15,669 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,669 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.7.7.2 different, marking for reconfigure

2019-01-10 17:03:15,671 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,672 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-01-10 17:03:15,674 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-01-10 17:03:15,771 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,774 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'
[debug] Attempting to get external IP using Name Server 'ns1.google.com'...
[debug] VPN provider custom is != pia, skipping incoming port detection

2019-01-10 17:03:15,775 DEBG 'privoxy-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,775 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2019-01-10 17:03:15,917 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2019-01-10 17:03:15,918 DEBG 'privoxy-script' stderr output:
2019-01-10 17:03:15.918 14de57074100 Info: Privoxy version 3.0.26
2019-01-10 17:03:15.918 14de57074100 Info: Program name: /usr/bin/privoxy

2019-01-10 17:03:15,919 DEBG 'privoxy-script' stderr output:
2019-01-10 17:03:15.919 14de57074100 Fatal error: can't load re_filterfile '/config/privoxy/default.filter': No such file or directory

2019-01-10 17:03:15,920 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22964851813552 for <Subprocess at 22964851497872 with name privoxy-script in state RUNNING> (stdout)>
2019-01-10 17:03:15,920 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22964851513104 for <Subprocess at 22964851497872 with name privoxy-script in state RUNNING> (stderr)>
2019-01-10 17:03:15,920 INFO exited: privoxy-script (exit status 1; not expected)
2019-01-10 17:03:15,920 DEBG received SIGCLD indicating a child quit
2019-01-10 17:03:15,932 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 96.9.247.12

2019-01-10 17:03:15,977 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:03:15,978 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-01-10 17:03:16,119 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface currently defined as 0.0.0.0
[info] Deluge listening interface will be changed to 0.0.0.0
[info] Saving changes to Deluge config file /config/core.conf...

2019-01-10 17:03:16,267 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-01-10 17:03:17,247 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-01-10 17:03:17,247 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-01-10 17:03:17,247 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:03:47,248 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:47,367 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:47,372 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:03:47,372 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:04:17,373 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:04:17,487 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:04:17,492 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:04:17,492 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:04:47,493 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:04:47,608 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:04:47,614 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:04:47,614 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:05:17,615 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:05:17,728 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:05:17,734 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:05:17,734 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

Sorry, I'm unsure on how to make this smaller!

Edited by BennyD
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.