Jump to content
binhex

[Support] binhex - DelugeVPN

4977 posts in this topic Last Reply

Recommended Posts

2 hours ago, phillibl said:

I am not getting good speeds while using PIA.  I'm using Ubuntu and Linux Mint torrents to test due to high availability.  Using DelugeVPN and QbittorentVPN connecting to PIA servers with and without portforwarding, which according to PIA Speed Test connect with my full speed, I get 1/8th of my full speed.  Setting VPN_Enabled=no I get full speed.  

 

I tried different settings within the clients like UPNP disabled and uPT(?) disabled with no improvement. 

 

Is there anything else to try?

see link below, Q6.

https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613

 

Share this post


Link to post

Binhex, thank you for this great docker I have been using it for a long time and without any issues. Really appreciate it. However, I reside in Turkey and recently all OpenVPN servers were blocked as a government policy. So it seems that whatever I add as a VPN server the deluge can't find its way out. I'm currently using NordVpn as my VPN client and on my main computer and obfuscated servers are actually active. Is there a way to make deluge use these special servers or is my only option is to use the docker is without the VPN. I'm actually a newbie when it comes to these setting configurations and I would like to continue using VPN on the docker so if there is any other changes that I could make your help will be very much appreciated. 

 

Thanks,

 

PS. Sorry if this was asked before I searched but couldn't find any related questions.

Share this post


Link to post
2 hours ago, odyseus8 said:

Is there a way to make deluge use these special servers

you can switch to any openvpn server by editing the /config/openvpn/<filename>.ovpn file and changing the 'remote' line to match the server or endpoint you want to connect to, then restart the container.

Share this post


Link to post

I'm having a little trouble with this. I am attempting to set this up with a Torguard port forward. When I set the OVPN file to connect to a standard Torguard server on port 443 it will connect, and I am able to access the WebUI. But When I try to connect to my dedicated IP for my forwarded port I am not able to access the WebUI, although I can tell there are some packets being transmitted.

 

Any ideas what might be going on?

Share this post


Link to post

I recently replaced my boot usb and updated to 6.6.6 after that I couldnt get the webUI to load. removed delugevpn and reinstalled it making sure to get the certs and ovpn files from previous post on this thread. I get "this site cant be reached" when trying to access the webUI. Here is my log file is there something I am not seeing that is causing a problem? Thanks in advance.

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

2019-02-09 02:19:53.128503 [info] System information Linux bde1bca90b56 4.18.20-unRAID #1 SMP Fri Nov 23 11:38:16 PST 2018 x86_64 GNU/Linux
2019-02-09 02:19:53.160571 [info] PUID defined as '99'
2019-02-09 02:19:53.193084 [info] PGID defined as '100'
2019-02-09 02:19:53.236612 [info] UMASK defined as '000'
2019-02-09 02:19:53.266099 [info] Permissions already set for volume mappings
2019-02-09 02:19:53.298564 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2019-02-09 02:19:53.328636 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2019-02-09 02:19:53.358057 [info] VPN_ENABLED defined as 'yes'
2019-02-09 02:19:53.393679 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Switzerland.ovpn
dos2unix: converting file /config/openvpn/Switzerland.ovpn to Unix format...
2019-02-09 02:19:53.436936 [info] VPN remote line defined as 'remote swiss.privateinternetaccess.com 1198'
2019-02-09 02:19:53.466947 [info] VPN_REMOTE defined as 'swiss.privateinternetaccess.com'
2019-02-09 02:19:53.496949 [info] VPN_PORT defined as '1198'
2019-02-09 02:19:53.530456 [info] VPN_PROTOCOL defined as 'udp'
2019-02-09 02:19:53.560158 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-02-09 02:19:53.589789 [info] VPN_PROV defined as 'pia'
2019-02-09 02:19:53.620922 [info] LAN_NETWORK defined as '192.168.0.1/24'
2019-02-09 02:19:53.652903 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2019-02-09 02:19:53.695327 [info] VPN_USER defined as 'removed'
2019-02-09 02:19:53.727363 [info] VPN_PASS defined as 'removed'
2019-02-09 02:19:53.763064 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-02-09 02:19:53.792415 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-02-09 02:19:53.820422 [info] ENABLE_PRIVOXY defined as 'yes'
2019-02-09 02:19:53.850257 [info] Starting Supervisor...
2019-02-09 02:19:54,213 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-02-09 02:19:54,213 INFO Set uid to user 0 succeeded
2019-02-09 02:19:54,216 INFO supervisord started with pid 8
2019-02-09 02:19:55,218 INFO spawned: 'start-script' with pid 149
2019-02-09 02:19:55,219 INFO spawned: 'watchdog-script' with pid 150
2019-02-09 02:19:55,221 INFO spawned: 'privoxy-script' with pid 151
2019-02-09 02:19:55,221 INFO reaped unknown pid 9
2019-02-09 02:19:55,225 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
[debug] Environment variables defined as follows
BASH=/bin/bash
BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="/root/start.sh")
BASH_VERSINFO=([0]="5" [1]="0" [2]="0" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")
BASH_VERSION='5.0.0(1)-release'
DEBUG=true
DELUGE_DAEMON_LOG_LEVEL=info
DELUGE_WEB_LOG_LEVEL=info
DIRSTACK=()
ENABLE_PRIVOXY=yes
EUID=0

2019-02-09 02:19:55,226 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-09 02:19:55,226 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-09 02:19:55,226 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-09 02:19:55,226 DEBG 'start-script' stdout output:
GROUPS=()
HOME=/home/nobody
HOSTNAME=bde1bca90b56
HOSTTYPE=x86_64
HOST_OS=Unraid
IFS=$' \t\n'
LANG=en_GB.UTF-8
LAN_NETWORK=192.168.0.1/24
MACHTYPE=x86_64-pc-linux-gnu
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
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PGID=100
PIPESTATUS=([0]="0")
PPID=8
PS4='+ '
PUID=99
PWD=/
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
STRICT_PORT_FORWARD=yes
SUPERVISOR_ENABLED=1
SUPERVISOR_GROUP_NAME=start-script
SUPERVISOR_PROCESS_NAME=start-script
TERM=xterm
TZ=America/Los_Angeles
UID=0
UMASK=000
VPN_CONFIG=/config/openvpn/Switzerland.ovpn
VPN_DEVICE_TYPE=tun0
VPN_ENABLED=yes
VPN_OPTIONS=
VPN_PASS=removed
VPN_PORT=1198
VPN_PROTOCOL=udp
VPN_PROV=pia
VPN_REMOTE=swiss.privateinternetaccess.com
VPN_USER=removed
_='[debug] Environment variables defined as follows'
[debug] Directory listing of files in /config/openvpn as follows

2019-02-09 02:19:55,226 DEBG 'watchdog-script' stdout output:
[info] Deluge-web config file doesn't exist, copying default...

2019-02-09 02:19:55,228 DEBG 'privoxy-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:19:55,228 DEBG 'watchdog-script' stdout output:
[info] Deluge config file doesn't exist, copying default...

2019-02-09 02:19:55,229 DEBG 'start-script' stdout output:
total 16
drwxrwxr-x 1 nobody users  126 Feb  9 02:19 .
drwxrwxr-x 1 nobody users   78 Feb  9 02:19 ..
-rwxrwxr-x 1 nobody users 2025 Nov 12 15:33 ca.rsa.2048.crt
-rwxrwxr-x 1 nobody users   20 Feb  9 01:53 credentials.conf
-rwxrwxr-x 1 nobody users  869 Nov 12 15:33 crl.rsa.2048.pem
-rwxrwxr-x 1 nobody users 3175 Feb  9 02:19 Switzerland.ovpn

2019-02-09 02:19:55,230 DEBG 'watchdog-script' stderr output:
dos2unix: 
2019-02-09 02:19:55,230 DEBG 'watchdog-script' stderr output:
converting file /config/core.conf to Unix format...

2019-02-09 02:19:55,231 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:19:55,268 DEBG 'start-script' stdout output:
[debug] Contents of ovpn file /config/openvpn/Switzerland.ovpn as follows...

2019-02-09 02:19:55,268 DEBG 'start-script' stdout output:
remote swiss.privateinternetaccess.com 1198
client
dev tun
proto udp
resolv-retry infinite
nobind
persist-key
cipher aes-128-cbc
auth sha1
tls-client
remote-cert-tls server

auth-user-pass credentials.conf
compress
verb 1
<crl-verify>
-----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----
</crl-verify>

<ca>
-----BEGIN CERTIFICATE-----
MIIFqzCCBJOgAwIBAgIJAKZ7D5Yv87qDMA0GCSqGSIb3DQEBDQUAMIHoMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCQ0ExEzARBgNVBAcTCkxvc0FuZ2VsZXMxIDAeBgNV
BAoTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAwHgYDVQQLExdQcml2YXRlIElu
dGVybmV0IEFjY2VzczEgMB4GA1UEAxMXUHJpdmF0ZSBJbnRlcm5ldCBBY2Nlc3Mx
IDAeBgNVBCkTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMS8wLQYJKoZIhvcNAQkB
FiBzZWN1cmVAcHJpdmF0ZWludGVybmV0YWNjZXNzLmNvbTAeFw0xNDA0MTcxNzM1
MThaFw0zNDA0MTIxNzM1MThaMIHoMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex
EzARBgNVBAcTCkxvc0FuZ2VsZXMxIDAeBgNVBAoTF1ByaXZhdGUgSW50ZXJuZXQg
QWNjZXNzMSAwHgYDVQQLExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UE
AxMXUHJpdmF0ZSBJbnRlcm5ldCBBY2Nlc3MxIDAeBgNVBCkTF1ByaXZhdGUgSW50
ZXJuZXQgQWNjZXNzMS8wLQYJKoZIhvcNAQkBFiBzZWN1cmVAcHJpdmF0ZWludGVy
bmV0YWNjZXNzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAPXD
L1L9tX6DGf36liA7UBTy5I869z0UVo3lImfOs/GSiFKPtInlesP65577nd7UNzzX
lH/P/CnFPdBWlLp5ze3HRBCc/Avgr5CdMRkEsySL5GHBZsx6w2cayQ2EcRhVTwWp
cdldeNO+pPr9rIgPrtXqT4SWViTQRBeGM8CDxAyTopTsobjSiYZCF9Ta1gunl0G/
8Vfp+SXfYCC+ZzWvP+L1pFhPRqzQQ8k+wMZIovObK1s+nlwPaLyayzw9a8sUnvWB
/5rGPdIYnQWPgoNlLN9HpSmsAcw2z8DXI9pIxbr74cb3/HSfuYGOLkRqrOk6h4RC
OfuWoTrZup1uEOn+fw8CAwEAAaOCAVQwggFQMB0GA1UdDgQWBBQv63nQ/pJAt5tL
y8VJcbHe22ZOsjCCAR8GA1UdIwSCARYwggESgBQv63nQ/pJAt5tLy8VJcbHe22ZO
sqGB7qSB6zCB6DELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRMwEQYDVQQHEwpM
b3NBbmdlbGVzMSAwHgYDVQQKExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4G
A1UECxMXUHJpdmF0ZSBJbnRlcm5ldCBBY2Nlc3MxIDAeBgNVBAMTF1ByaXZhdGUg
SW50ZXJuZXQgQWNjZXNzMSAwHgYDVQQpExdQcml2YXRlIEludGVybmV0IEFjY2Vz
czEvMC0GCSqGSIb3DQEJARYgc2VjdXJlQHByaXZhdGVpbnRlcm5ldGFjY2Vzcy5j
b22CCQCmew+WL/O6gzAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBDQUAA4IBAQAn
a5PgrtxfwTumD4+3/SYvwoD66cB8IcK//h1mCzAduU8KgUXocLx7QgJWo9lnZ8xU
ryXvWab2usg4fqk7FPi00bED4f4qVQFVfGfPZIH9QQ7/48bPM9RyfzImZWUCenK3
7pdw4Bvgoys2rHLHbGen7f28knT2j/cbMxd78tQc20TIObGjo8+ISTRclSTRBtyC
GohseKYpTS9himFERpUgNtefvYHbn70mIOzfOJFTVqfrptf9jXa9N8Mpy3ayfodz
1wiqdteqFXkTYoSDctgKMiZ6GdocK9nMroQipIQtpnwd4yBDWIyC6Bvlkrq5TQUt
YDQ8z9v+DMO6iwyIDRiU
-----END CERTIFICATE-----
</ca>

disable-occ

2019-02-09 02:19:55,279 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-02-09 02:19:55,282 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-02-09 02:19:55,285 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2019-02-09 02:19:55,288 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2019-02-09 02:19:55,291 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-02-09 02:19:55,294 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-02-09 02:19:55,296 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2019-02-09 02:19:55,299 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2019-02-09 02:19:55,302 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-02-09 02:19:55,512 DEBG 'start-script' stdout output:
[info] Remote VPN endpoint resolves to the following A record(s)...
195.206.105.212 185.156.175.87 185.230.125.53 91.132.136.43 195.206.105.210 185.230.125.40 185.230.125.83 185.230.125.38 91.132.136.51 185.156.175.92 185.156.175.85 185.230.125.41 185.156.175.94

2019-02-09 02:19:55,522 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2019-02-09 02:19:55,523 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.18.20-unRAID

2019-02-09 02:19:55,523 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2019-02-09 02:19:55,523 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-02-09 02:19:55,524 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'
[debug] Show name servers defined for container

2019-02-09 02:19:55,524 DEBG 'start-script' stdout output:
nameserver 209.222.18.222
nameserver 37.235.1.174
nameserver 1.1.1.1
nameserver 8.8.8.8
nameserver 209.222.18.218
nameserver 37.235.1.177
nameserver 1.0.0.1
nameserver 8.8.4.4

2019-02-09 02:19:55,524 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint swiss.privateinternetaccess.com

2019-02-09 02:19:55,563 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 6382
;; flags: qr rd ra ; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; swiss.privateinternetaccess.com.    IN    A

;; ANSWER SECTION:
swiss.privateinternetaccess.com.    187    IN    A    185.230.125.34
swiss.privateinternetaccess.com.    187    IN    A    185.230.125.48
swiss.privateinternetaccess.com.    187    IN    A    195.206.105.213
swiss.privateinternetaccess.com.    187    IN    A    185.230.125.41
swiss.privateinternetaccess.com.    187    IN    A    91.132.136.43
swiss.privateinternetaccess.com.    187    IN    A    185.212.170.189
swiss.privateinternetaccess.com.    187    IN    A    91.132.136.54
swiss.privateinternetaccess.com.    187    IN    A    185.230.125.82
swiss.privateinternetaccess.com.    187    IN    A    185.230.125.50
swiss.privateinternetaccess.com.    187    IN    A    185.212.170.180
swiss.privateinternetaccess.com.    187    IN    A    185.230.125.49
swiss.privateinternetaccess.com.    187    IN    A    195.206.105.215
swiss.privateinternetaccess.com.    187    IN    A    185.156.175.94

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 37 msec
;; SERVER: 8.8.4.4
;; WHEN: Sat Feb  9 02:19:55 2019
;; MSG SIZE  rcvd: 257

2019-02-09 02:19:55,564 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2019-02-09 02:19:55,564 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.3    bde1bca90b56
195.206.105.212    swiss.privateinternetaccess.com

2019-02-09 02:19:55,568 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2019-02-09 02:19:55,571 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.3

2019-02-09 02:19:55,574 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2019-02-09 02:19:55,581 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2019-02-09 02:19:55,584 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2019-02-09 02:19:55,585 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

2019-02-09 02:19:55,585 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-02-09 02:19:55,586 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.3 

2019-02-09 02:19:55,586 DEBG 'start-script' stdout output:
--------------------
[debug] Modules currently loaded for kernel

2019-02-09 02:19:55,588 DEBG 'start-script' stdout output:
Module                  Size  Used by
tun                    36864  0
xt_nat                 16384  6
veth                   16384  0
ipt_MASQUERADE         16384  7
iptable_nat            16384  1
nf_conntrack_ipv4      16384  15
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
nf_nat_ipv4            16384  2 ipt_MASQUERADE,iptable_nat
iptable_filter         16384  1
ip_tables              24576  2 iptable_filter,iptable_nat
nf_nat                 24576  2 nf_nat_ipv4,xt_nat
reiserfs              212992  0
xfs                   663552  9
md_mod                 49152  9
nct6775                53248  0
hwmon_vid              16384  1 nct6775
bonding               110592  0
mlx4_en               102400  0
mlx4_core             274432  1 mlx4_en
e1000e                180224  0
sb_edac                24576  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             196608  0
kvm                   364544  1 kvm_intel
ipmi_ssif              24576  0
isci                  102400  4
libsas                 69632  1 isci
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
scsi_transport_sas     32768  2 isci,libsas
glue_helper            16384  1 aesni_intel
i2c_i801               24576  0
i2c_core               40960  2 i2c_i801,ipmi_ssif
intel_cstate           16384  0
intel_uncore          102400  0
ahci                   40960  11
intel_rapl_perf        16384  0
libahci                28672  1 ahci
wmi                    20480  0
pcc_cpufreq            16384  0
ipmi_si                53248  0
button                 16384  0

2019-02-09 02:19:55,625 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-02-09 02:19:55,626 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.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.0.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 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.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.0.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-02-09 02:19:55,626 DEBG 'start-script' stdout output:
--------------------

2019-02-09 02:19:55,627 DEBG 'start-script' stdout output:
[debug] OpenVPN command line:- /usr/bin/openvpn --daemon --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'pia' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_REMOTE 'swiss.privateinternetaccess.com' --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' --remote 195.206.105.212 1198 udp --remote 185.156.175.87 1198 udp --remote 185.230.125.53 1198 udp --remote 91.132.136.43 1198 udp --remote 195.206.105.210 1198 udp --remote 185.230.125.40 1198 udp --remote 185.230.125.83 1198 udp --remote 185.230.125.38 1198 udp --remote 91.132.136.51 1198 udp --remote 185.156.175.92 1198 udp --remote 185.156.175.85 1198 udp --remote 185.230.125.41 1198 udp --remote 185.156.175.94 1198 udp --remote-random --keepalive 10 60 --setenv STRICT_PORT_FORWARD 'yes' --disable-occ --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/Switzerland.ovpn'
[info] Starting OpenVPN...

2019-02-09 02:19:55,650 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:55 2019 WARNING: file 'credentials.conf' is group or others accessible
Sat Feb  9 02:19:55 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Sat Feb  9 02:19:55 2019 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10

2019-02-09 02:19:55,651 DEBG 'start-script' stdout output:
[info] OpenVPN started

2019-02-09 02:19:55,651 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:55 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:19:55,652 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:55 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.230.125.53:1198

2019-02-09 02:19:55,652 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:55 2019 UDP link local: (not bound)
Sat Feb  9 02:19:55 2019 UDP link remote: [AF_INET]185.230.125.53:1198

2019-02-09 02:19:56,329 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:56 2019 [a1d5e8bd7db4f0ca33c71f0d870fc0d8] Peer Connection Initiated with [AF_INET]185.230.125.53:1198

2019-02-09 02:19:57,508 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:57 2019 auth-token received, disabling auth-nocache for the authentication token

2019-02-09 02:19:57,509 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:57 2019 TUN/TAP device tun0 opened
Sat Feb  9 02:19:57 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sat Feb  9 02:19:57 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-02-09 02:19:57,510 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:57 2019 /usr/bin/ip addr add dev tun0 local 10.39.10.6 peer 10.39.10.5

2019-02-09 02:19:57,511 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:57 2019 /root/openvpnup.sh tun0 1500 1558 10.39.10.6 10.39.10.5 init

2019-02-09 02:19:57,515 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:19:57,518 DEBG 'start-script' stdout output:
Sat Feb  9 02:19:57 2019 Initialization Sequence Completed

2019-02-09 02:19:57,522 DEBG 'privoxy-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'
[info] Configuring Privoxy...

2019-02-09 02:19:57,527 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:19:57,527 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.39.10.6 different, marking for reconfigure

2019-02-09 02:19:57,530 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-02-09 02:19:57,533 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-02-09 02:19:57,547 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2019-02-09 02:19:57,548 DEBG 'privoxy-script' stderr output:
2019-02-09 02:19:57.548 14af1af8a100 Info: Privoxy version 3.0.26
2019-02-09 02:19:57.548 14af1af8a100 Info: Program name: /usr/bin/privoxy

2019-02-09 02:19:57,617 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:19:57,626 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:19:57,627 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'
[info] Strict port forwarding enabled, attempting to assign an incoming port...

2019-02-09 02:19:57,627 DEBG 'start-script' stdout output:
[debug] Attempting to get external IP using Name Server 'ns1.google.com'...

2019-02-09 02:19:57,632 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=650b56e5013e656539d459e6d0f3717995f45c292c90b46e15aadb491464cab7...

2019-02-09 02:19:58,149 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 185.230.125.53

2019-02-09 02:19:58,239 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:19:58,240 DEBG 'watchdog-script' stdout output:
[debug] Waiting for file '/home/nobody/vpn_incoming_port.txt' to be generated (contains PIA API generated incoming port number)...

2019-02-09 02:19:58,893 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=650b56e5013e656539d459e6d0f3717995f45c292c90b46e15aadb491464cab7, response code 200

2019-02-09 02:19:58,929 DEBG 'start-script' stdout output:
[debug] Successfully assigned incoming port 21820

2019-02-09 02:19:59,240 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:19:59,241 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 21820 different, marking for reconfigure
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-02-09 02:19:59,406 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-02-09 02:19:59,596 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-02-09 02:20:00,410 DEBG 'watchdog-script' stdout output:
Setting random_port to False..
Configuration value successfully updated.

2019-02-09 02:20:00,812 DEBG 'watchdog-script' stdout output:
Setting listen_ports to (21820, 21820)..
Configuration value successfully updated.

2019-02-09 02:20:01,256 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-02-09 02:20:01,257 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:20:31,258 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:20:31,375 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:20:31,381 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:20:31,382 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:20:31,387 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820

2019-02-09 02:20:31,387 DEBG 'watchdog-script' stdout output:
[debug] Deluge incoming port is 21820
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:21:01,388 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:21:01,505 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:21:01,512 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:21:01,512 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:21:01,516 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820

2019-02-09 02:21:01,516 DEBG 'watchdog-script' stdout output:
[debug] Deluge incoming port is 21820
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:21:31,517 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:21:31,636 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:21:31,643 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:21:31,644 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:21:31,648 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:22:01,649 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:22:01,768 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:22:01,774 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:22:01,775 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:22:01,778 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820

2019-02-09 02:22:01,778 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:22:31,779 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:22:31,897 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:22:31,903 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:22:31,904 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:22:31,908 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820

2019-02-09 02:22:31,908 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:23:01,909 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:23:02,025 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:23:02,032 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:23:02,032 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:23:02,036 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:23:32,037 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:23:32,154 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:23:32,161 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:23:32,161 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:23:32,165 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:24:02,166 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:24:02,283 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:24:02,289 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:24:02,290 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:24:02,294 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820

2019-02-09 02:24:02,294 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:24:32,295 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:24:32,412 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:24:32,418 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:24:32,419 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:24:32,423 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820

2019-02-09 02:24:32,423 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:25:02,424 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:25:02,542 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:25:02,549 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:25:02,549 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:25:02,553 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820
[debug] VPN IP is 10.39.10.6

2019-02-09 02:25:02,554 DEBG 'watchdog-script' stdout output:
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:25:32,555 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:25:32,672 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:25:32,678 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:25:32,679 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:25:32,683 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820

2019-02-09 02:25:32,683 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:26:02,684 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-02-09 02:26:02,802 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.39.10.6'

2019-02-09 02:26:02,809 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '185.230.125.53'

2019-02-09 02:26:02,809 DEBG 'watchdog-script' stdout output:
[debug] Incoming port for tunnel is '21820'

2019-02-09 02:26:02,813 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 21820
[debug] Deluge incoming port is 21820

2019-02-09 02:26:02,813 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.39.10.6
[debug] Deluge IP is 10.39.10.6

2019-02-09 02:26:06,953 WARN received SIGTERM indicating exit request
2019-02-09 02:26:06,954 DEBG killing privoxy-script (pid 151) with signal SIGTERM
2019-02-09 02:26:06,954 INFO waiting for start-script, watchdog-script, privoxy-script to die
2019-02-09 02:26:07,955 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22679269636576 for <Subprocess at 22679269653752 with name privoxy-script in state STOPPING> (stdout)>
2019-02-09 02:26:07,956 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22679271398000 for <Subprocess at 22679269653752 with name privoxy-script in state STOPPING> (stderr)>
2019-02-09 02:26:07,956 INFO stopped: privoxy-script (terminated by SIGTERM)
2019-02-09 02:26:07,956 DEBG received SIGCLD indicating a child quit
2019-02-09 02:26:07,957 DEBG killing watchdog-script (pid 150) with signal SIGTERM
2019-02-09 02:26:07,957 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22679269636360 for <Subprocess at 22679269651160 with name watchdog-script in state STOPPING> (stderr)>
2019-02-09 02:26:07,958 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22679269634272 for <Subprocess at 22679269651160 with name watchdog-script in state STOPPING> (stdout)>
2019-02-09 02:26:07,958 INFO stopped: watchdog-script (terminated by SIGTERM)
2019-02-09 02:26:07,958 DEBG received SIGCLD indicating a child quit
2019-02-09 02:26:07,958 DEBG killing start-script (pid 149) with signal SIGTERM
2019-02-09 02:26:07,959 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22679269652384 for <Subprocess at 22679269652888 with name start-script in state STOPPING> (stdout)>
2019-02-09 02:26:07,959 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22679287588120 for <Subprocess at 22679269652888 with name start-script in state STOPPING> (stderr)>
2019-02-09 02:26:07,959 INFO stopped: start-script (terminated by SIGTERM)
2019-02-09 02:26:07,959 DEBG received SIGCLD indicating a child quit

mtornero_supervisord.log

Share this post


Link to post

Ok after you pointed me in the direction that it was my LAN_NETWORK as the culprit. I looked at the network setting to see if there was something I was missing. I ended up noticing the routing table in the network settings that showed me where I needed to make my changes. When I applied the changes I was able to get the webUI up and functioning. Thanks for pointing me in the right direction. Here are the settings that worked in the end. rt.JPG.236440460ff09eccbd1100bfb0f4f31f.JPG 

Share this post


Link to post
7 minutes ago, mtornero said:

The ip address of the server is 198.162.0.20 so wouldnt that make 192.168.0.1/24

192.168.0.1 is your gateway. If your IP is 198.162.0.20 and your netmask is 255.255.255.0 then your network is 192.168.0.0/24 as per the example that @strike linked.

Share this post


Link to post
40 minutes ago, wgstarks said:

192.168.0.1 is your gateway. If your IP is 198.162.0.20 and your netmask is 255.255.255.0 then your network is 192.168.0.0/24 as per the example that @strike linked.

Thanks for the pro tip, that was all I was looking for. It might be quicker to have people go to the settings and plug in the values already displayed instead of sending them to that older post. Finding that info was more direct help. Maybe add it to install/setup steps ive seen people sent to. 

Share this post


Link to post

Hi All

 

So if I already have all the openvpn files from my host vendors VPN (They use OpenVPN)

Can I set it up, using the Container Variable: VPN_PROV: custom?

And then following the great video on how to set this up ;-)

 

Update I get the following files from my provider:

ca.crt

credentials.conf

openvpn.ovpn

username.crt

username.key

 

Edited by casperse

Share this post


Link to post

Hi all, I just tried to access the webui on my unraid box.  I get "the site cannot be reached" error.  I'm using 8112 as the web gui and I haven't changed anything.  I just switched to PIA and setup a new account.  username and password are correct and I am still getting page cannot be reached.  I followed the SIO video and set everything up in alignment with that, including using the netherlands vpn profile.  Any suggestions?

Share this post


Link to post

Hey everyone,

 

Just started using this container yesterday, and I have made some progress, but I must be missing something along the way. I'm using Mullvad VPN, and I saw back in 2017 someone had issues getting this container started with Mullvad as their VPN provider. By looking through the logs, I can see that the container is filtering out the ipv6 options (which was the original issue back in 2017) but I'm still running into issues. It seems as though OpenVPN keeps stopping and restarting for one reason or another.

 

The easiest way for me to describe the issue is...

1. Spin up the delugevpn

2. Wait for web ui to initialize, then add a torrent file.

3. Look at tracker status for torrent file, get errors such as " Error: Cannot assign requested address" or "Error: Host not found (non-authoritative), try again later".

 

There are brief glimmers where the VPN is functioning properly and it'll begin to download the file(s), but then I'll see a drop in peers, and I assume it's because OpenVPN is restarting. Attached is my log file with the DEBUG variable set to "true".  Any help is much appreciated!

supervisord.log

Share this post


Link to post
9 hours ago, PureCurry said:

There are brief glimmers where the VPN is functioning properly and it'll begin to download the file(s), but then I'll see a drop in peers, and I assume it's because OpenVPN is restarting.

im going to guess you are a qnap user, if so see Q13 in the following link:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613

 

Share this post


Link to post
4 hours ago, binhex said:

im going to guess you are a qnap user, if so see Q13 in the following link:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613

 

QNAP makes the strangest configuration choices, I should've known that just from using Container Station for a few hours! I gave up on their GUI and went straight CLI, and I'm definitely not looking back. Editing out that line from daemon_mgr.conf and spinning up a fresh container immediately solved my issue. Downloads are working at full speed with a healthy list of seeders and peers 😁 Thanks a bunch for your help Binhex!! I'll be sure to take a closer look at the FAQ next time.

Share this post


Link to post

Hi everyone

 

I dont normally post for help until i've run up against a wall... and i have.

 

I cant seem to seed any torrents.

 

The only time i see any uploading rate is when i'm downloading - afterwards theres no traffic.

 

This is running behind another linux box firewall and ive done my best to unsure the ports are forwarded to the unraid box.

This isnt new to me, i have many ports forwarded to other points in my network and they all work fine

download speeds are ok, just no upload...

 

Anything i can check? What config files would you like to see?

Not much for errors in the logfile.

 

Help! (please)

Share this post


Link to post
44 minutes ago, lukesaber said:

ive done my best to unsure the ports are forwarded to the unraid box.

a common misconception, port forwarding on your router/firewall will get you nowhere, the port forwarding has to be done by your vpn provider, so my guess is that you are using a vpn provider that does not allow port forwarding or you havent configured deluge to make use of the port assigned to you by your vpn provider, this will result in low or non existent seeding.

 

edit - see Q16 from the link below for more details:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&amp;comment=433612

 

Edited by binhex

Share this post


Link to post
On 2/11/2019 at 6:13 PM, jonathanm said:

Thanks for that.  I checked and everything appears to be in order.  After some further digging, I was able to get to the webui by turning off VPN_Enabled.  So I guess it's something i'm doing wrong there.  I have PIA, I loaded the netherlands openvpn profile into appdata\... Are there any instructions on how to setup the VPN piece?  I followed SIO to the t including signing up for PIA.  

 

Any suggestions or instructions to help?

Share this post


Link to post
1 minute ago, ledfortr said:

Any suggestions or instructions to help?

Review the list of PIA endpoints that support port forwarding. netherlands isn't on the list.

Share this post


Link to post

So a bunch of binhex containers are showing as "update ready". I updated deluge but the update said it was deleting the container instead. now its gone. what gives?

Share this post


Link to post

First Image Unable to access the Webgui see

2nd Image i have files in openvpn

3rd image i've changed it from customer all way to bridge and no luck

4th image the configurations

Capture.PNG

Capture1.PNG

Capture3.PNG

Capture4.PNG

Share this post


Link to post
2 hours ago, darrenyorston said:

So a bunch of binhex containers are showing as "update ready". I updated deluge but the update said it was deleting the container instead. now its gone. what gives?

not sure why its showing updates as i havent pushed anything for at least a couple of weeks+ (delugevpn 29 days), that aside deletion of the container is perfectly normal for an update, when you click on update in the unraid web ui what actually is happening is pull down of the new image, then deletion of the existing container, then re-creation of the new container, keep in mind no configuration should be contained within the container, its all volume mounted to the host via /config, so deletion of the container will mean no loss of config.

 

so without a screenshot of the commands executed during the update its hard to say why it couldnt re-create the container, im assuming its still in this stuck state right?, can you post a screenshot.

Share this post


Link to post
1 hour ago, binhex said:

not sure why its showing updates as i havent pushed anything for at least a couple of weeks+ (delugevpn 29 days), that aside deletion of the container is perfectly normal for an update, when you click on update in the unraid web ui what actually is happening is pull down of the new image, then deletion of the existing container, then re-creation of the new container, keep in mind no configuration should be contained within the container, its all volume mounted to the host via /config, so deletion of the container will mean no loss of config.

 

so without a screenshot of the commands executed during the update its hard to say why it couldnt re-create the container, im assuming its still in this stuck state right?, can you post a screenshot.

Yeah man. When I checked my containers every container I have said there was un update available. I started with deluge as its first on the list. The container started updating. It processed, deleted the container then stopped. The container was then gone. I had to reinstall it.

Share this post


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.