PIA now supports wireguard. This should allow faster downloads than OpenVPN. I created an issue on Github requesting support to be added for wireguard. Not sure if you had seen it so asking here. 

 

https://github.com/binhex/arch-delugevpn/issues/166

Hey all, I apologize as I can only assume my question has been answered somewhere in the previous 241 pages! But I am looking to see if I can use the Deluge docker as a thin client (GTK UI) to attach to my remote FeralHosting (seedbox) deluge daemon.

 

Basically I would like my Radarr/Sonarr dockers to drop their .torrent files directly to the thinclient folder and then have that upload via the ssh tunnel to the seedbox.

 

I have done some extensive GoogleFu and searched through the forums and haven't seen a solution.

 

I've also looked at: https://dev.deluge-torrent.org/wiki/UserGuide/ThinClient and I'm not seeing where the switch from Classic mode is. Was this feature disabled or rolled into a different option?

 

Appreciate it.

 

**EDIT**

 

So my Seedbox is on Deluge v1 and obviously the dockers are v2, assuming this is the issue and why it won't even highlight connect via the connection manager?

 

Anyone have any issues upgrading from v1 to v2? I'll have to see if it's supported on my Seedbox if this is the issue.

 

Edited May 10, 20206 yr by Skrumpy

I tried downgrad my deluge docker from 2.0.4 to 2.0.3. I followed the faq, used the tag arch-delugevpn:2.0.3_23_g5f1eada3e-1-03. 

Seemed to work, but sadly doesn´t because my webui still shows 2.0.4 dev20.

 

What have I done wrong?

I read through the posts in this thread here but couldn´t find a working solution for my problem.

30 minutes ago, antagon said:

I tried downgrad my deluge docker from 2.0.4 to 2.0.3. I followed the faq, used the tag arch-delugevpn:2.0.3_23_g5f1eada3e-1-03. 

Seemed to work, but sadly doesn´t because my webui still shows 2.0.4 dev20.

 

What have I done wrong?

I read through the posts in this thread here but couldn´t find a working solution for my problem.

I may be wrong but I don't think that tag is correct. I don't see that build in the list.

acorrding to the faq it should be stated under "tags", or I made a mistake. Gonna check it

11 minutes ago, antagon said:

acorrding to the faq it should be stated under "tags", or I made a mistake. Gonna check it

My mistake. It’s on both, I just missed it.

Hi

 

I've set up DelugeVPN with the SurfShark VPN. It works, but my download speeds are quite low (2 MB/s). I'm using the belgian server with the TCP protocol.

If I connect my Win10 laptop with the same server and protocol, I'm able to reach speeds of up to 6 MB/s (using BitTorrent). Without VPN, I reach speeds of 20+ MB/s, using the same torrent. I understand that using a VPN will cut down my speeds, but I do not understand why deluge gives me much lower speeds than my Win10 client connected in the same way.

 

I've looked around for possible solutions, including disabling enable_outgoing_utp and enable_incoming_utp in the ItConfig plugin, but nothing appears to be working. Can anyone help me?

EDIT: solved by updating os to 6.8.3 (which has separate issues). see below.

 

This is probably not an issue wiht delugevpn as that container on it's own seems to work, but I's connected...

 

I had this set up a few weeks ago and it was working, but I needed to change up a few things so I opted to tear it all down and start from scratch. (learning experience, right?)

 

I'm following spaceinvaderone's excellent video on routing container networks through another container running VPN: https://www.youtube.com/watch?v=znSu_FuKFW0

 

Using binhex-delugevpn as my vpn container. that seems to be set up and working properly. I can check it's external IP and it looks like it's in Switzerland. WebUI is accessible from internal network and seems to be working. able to download a linux iso without problems.

 

Trying to create a binhex-jackett container (have tried some others and get the same result). I can get the container to run without changing network settings, but if I change the normal network to "none" and add an extra parameters "--net=container:binhex-delugevpn" I get this:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-jackett' --net='none' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-jackett':'/config':'rw' --net=container:binhex-delugevpn 'binhex/arch-jackett' /usr/bin/docker: Error response from daemon: Container cannot be connected to network endpoints: container:binhex-delugevpn, none. See '/usr/bin/docker run --help'. The command failed.

 

help pls

Edited May 11, 20206 yr by hopsonhops

56 minutes ago, hopsonhops said:

help pls

I’m not sure why you are changing the network but if you want Jackett to use the DelugeVPN you would point it to the privoxy service the DelugeVPN docker provides. This is configured in the Jackett settings.

7 minutes ago, wgstarks said:

I’m not sure why you are changing the network but if you want Jackett to use the DelugeVPN you would point it to the privoxy service the DelugeVPN docker provides. This is configured in the Jackett settings.

this doesn't address what I'm trying to do here.

 

as I noted above I'm following the process in spaceinvader's video to route container traffic through a container with vpn. Jackett is just one container I would like to have set up this way. This was working previously, but now I've gone to re-do my setup and it's no longer working.

 

One problem might be that the container thinks it has two networks, but I can't find a way to truly delete the default network, just set the drop-down to "none". 

Success! solution ended up being upgrade from OS 6.8.1 to 6.8.3. Theres a bug in 6.8.3 that causes all containers to constantly think they need to be updated, so I had rolled back to the previous version. Apparently 6.8.1 has this issue with routing container networks. Looks like I'm stuck with one issue or the other so I guess I'll just live with the false update notification issue.

4 minutes ago, hopsonhops said:

Success! solution ended up being upgrade from OS 6.8.1 to 6.8.3. Theres a bug in 6.8.3 that causes all containers to constantly think they need to be updated, so I had rolled back to the previous version. Apparently 6.8.1 has this issue with routing container networks. Looks like I'm stuck with one issue or the other so I guess I'll just live with the false update notification issue.

Actually I think that bug was in 6.8.2 and fixed in 6.8.3.

23 minutes ago, wgstarks said:

Actually I think that bug was in 6.8.2 and fixed in 6.8.3.

definitely still a bug in 6.8.3. All of my containers have an update option. even fresh installs or ones I just updated. 

Mine don’t.

2 hours ago, hopsonhops said:

All of my containers have an update option. even fresh installs or ones I just updated. 

Just to be clear this is on the Docker tab in the GUI in the version column?

8 hours ago, hopsonhops said:

definitely still a bug in 6.8.3. All of my containers have an update option. even fresh installs or ones I just updated. 

Known issue on 6.8.3 when on the dashboard.  Docker Tab is correct.  Already fixed on the next release

Hi Binhex,

I haven't been on my server for a while, but just went on to use Deluge, however it wont launch for me, was wondering if you could help?

 

My logs I see the below when I go to start the programme:

 

020-05-12 08:19:18,163 DEBG 'start-script' stdout output:
Tue May 12 08:19:18 2020 SIGHUP[soft,tls-error] received, process restarting

When a go to start deluge it just doesn't load for me.

Hi,

 

Having and issue (not sure if it even is an issue) with looking at the IP address when bashing into the deluge container. When I run the command "curl ifconifg.io" though the deluge terminal I get back a public IPv6 address rather then the IPv4 address from PIA that the container is connected. In the web UI on the bottom right I can see PIA's IP address just not using terminal.

 

The really strange part is that I don't have IPv6 enabled on my router and also have Unraid set to IPv4 only in network settings. Also when I run the same command in for example Radarr's terminal window I get my WAN IPv4 address even though in the Radarr seeings I have proxy enabled though Deluge. If I shut down Deluge anything that I have configured to proxy though it can no longer connect. When I proxy my browser though Deluge and do a IP leak test I get the IP address of the PIA server and no leaks.

 

Again not sure if this is even a problem, just want to make sure I don't have any leak with Deluge or any other docker that is using it as a proxy.

For some reason I can no longer reach the deluge webgui.  I noticed my torrents seemed to not be active so just stopped and started the docker.  It starts fine, however when I go to the webgui it tells me the site can't be reached.

For the webgui in the docker I have http://[IP]:[PORT:8112]/

my airvpn login is fine.Log for_ binhex-delugevpn.html

 

Not sure what happened....

ok I disabled the vpn part and restarted and can now get to the webgui...I'm guessing that means I have a problem with my vpn...but have no idea where to start...

 

THink I got it.  It seems the vpn I was connected to was down.

 

Just a quick question.  When using airvpn, I seem to be able to create an ovpn file for a country or I can select an individual location.  Just wondering if one is preferable to the other.  Right now I selected country and I am now able to connect to the webgui but wondering if using country rather than a single location causes issues?

 

On 5/12/2020 at 5:57 AM, hopsonhops said:

Theres a bug in 6.8.3 that causes all containers to constantly think they need to be updated, so I had rolled back to the previous version. Apparently 6.8.1 has this issue with routing container networks. Looks like I'm stuck with one issue or the other so I guess I'll just live with the false update notification issue.

Strange - I have the problem that I no longer have 'update' options showing on the Dashboard - I have to go to the Docker page in order to invoke the update.

Getting a VPN connection error on PIA so can't acess WebUI. I  Updated  Deluge Doccker and installed new Cert from PIA.  Tried several .ovpn configs from PIA for different servers but still same message.  What does this error mean?  Suggestions to fix welcomed.

 

2020-05-13 19:34:23,375 DEBG 'watchdog-script' stderr output:
terminate called after throwing an instance of 'std::bad_weak_ptr'
what(): bad_weak_ptr

 

Edited May 13, 20206 yr by PhiPhi
Insert Code tags

@binhex Setting -1 for upload slots in Global Network Bandwidth seems to kill the daemon instantly (without saving the setting) and completely corrupt the list of torrents I have added. I went from having over 500 torrents added to less than 3. Files are still on my drive but they are no longer in Deluge. Restarted the docker container twice too, doesn't make any difference.

 

I did this a second time after adding 100 torrents. Exact same thing.

 

Interestingly setting -1 works if there are no torrents active in Deluge.

 

-1 seemed to have been a valid setting before without throwing this error... no idea why it is for some settings but not this one. Is this a bug?

 

EDIT: Seem to also be having a problem. No matter what I specify as the download location, it won't make the folder.

 

Eg. if my "/data/" location is mapped to something like /tank/Downloads/Torrents where I have a subfolder for each tracker.

 

It seems Deluge will just dump everything there, even if I specify /data/Tracker1

 

for example as the download location when adding a torrent. I thought it was a permissions issue but when adding the torrent, having it start in "/tank/Downloads/Torrents" instead of e.g. "/tank/Downloads/Torrents/Tracker1" because the former is "/data/" I can still right click, "Move Download" to /tank/Downloads/Torrents/Tracker1 and it will work... It just won't start from there, and more annoyingly it won't cross-seed properly. I need to start the torrent in "/data/" add it in a paused state (which doesn't seem to work either) and then stop it immediately, change the download location via right click and move the already downloaded files back and then manually force recheck.

 

Is there any way to get this working normally?

Edited May 13, 20206 yr by plantsandbinary

Hello All, i am not able to access deluge Webui. I am using PIA VPN. I can able to access webui after turning of VPN. Can any one help me on this? . I tried different PIA VPN config but same issue

 

2020-05-13 20:51:41,935 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has an undefined value
[info] Deluge key 'listen_interface' will have a new value '10.82.10.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-05-13 20:51:42,280 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has an undefined value
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-05-13 20:51:42,468 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '2764f3fde14944b381d5a620d1a3dc7f'
[info] Deluge key 'default_daemon' will have a new value '2764f3fde14944b381d5a620d1a3dc7f'
[info] Writing changes to Deluge config file '/config/web.conf'...

2020-05-13 20:51:42,767 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-05-13 20:51:42,979 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-05-13 20:51:45,024 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-05-13 20:51:47,125 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (21213, 21213)
Configuration value successfully updated.

2020-05-13 20:51:49,279 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2020-05-13 20:51:49,280 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

2020-05-13 20:51:49,286 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2020-05-13 20:51:50,298 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2020-05-13 20:51:50,305 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2020-05-13 21:03:11,034 WARN received SIGTERM indicating exit request
2020-05-13 21:03:11,035 DEBG killing watchdog-script (pid 174) with signal SIGTERM
2020-05-13 21:03:11,035 INFO waiting for start-script, watchdog-script to die
2020-05-13 21:03:12,037 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 140687154367600 for <Subprocess at 140687154366928 with name watchdog-script in state STOPPING> (stdout)>
2020-05-13 21:03:12,037 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 140687153836960 for <Subprocess at 140687154366928 with name watchdog-script in state STOPPING> (stderr)>
2020-05-13 21:03:12,037 INFO stopped: watchdog-script (terminated by SIGTERM)
2020-05-13 21:03:12,038 DEBG received SIGCHLD indicating a child quit
2020-05-13 21:03:12,038 DEBG killing start-script (pid 173) with signal SIGTERM
2020-05-13 21:03:13,039 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140687154229504 for <Subprocess at 140687154232144 with name start-script in state STOPPING> (stdout)>
2020-05-13 21:03:13,039 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140687154366832 for <Subprocess at 140687154232144 with name start-script in state STOPPING> (stderr)>
2020-05-13 21:03:13,040 INFO stopped: start-script (terminated by SIGTERM)
2020-05-13 21:03:13,040 DEBG received SIGCHLD indicating a child quit
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2020-05-13 21:03:15.753546 [info] System information Linux 47add084911d 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-05-13 21:03:15.822867 [info] PUID defined as '99'
2020-05-13 21:03:15.855091 [info] PGID defined as '100'
2020-05-13 21:03:16.011914 [info] UMASK defined as '000'
2020-05-13 21:03:16.041761 [info] Permissions already set for volume mappings
2020-05-13 21:03:16.073119 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-05-13 21:03:16.103154 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-05-13 21:03:16.133524 [info] VPN_ENABLED defined as 'yes'
2020-05-13 21:03:16.171208 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Montreal.ovpn
2020-05-13 21:03:16.228504 [info] VPN remote line defined as 'remote ca-montreal.privateinternetaccess.com 1198'
2020-05-13 21:03:16.259283 [info] VPN_REMOTE defined as 'ca-montreal.privateinternetaccess.com'
2020-05-13 21:03:16.288013 [info] VPN_PORT defined as '1198'
2020-05-13 21:03:16.323263 [info] VPN_PROTOCOL defined as 'udp'
2020-05-13 21:03:16.351491 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-05-13 21:03:16.381102 [info] VPN_PROV defined as 'pia'
2020-05-13 21:03:16.406479 [info] LAN_NETWORK defined as '192.168.1.0/24'
2020-05-13 21:03:16.432079 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2020-05-13 21:03:16.457634 [info] VPN_USER defined as ''
2020-05-13 21:03:16.483202 [info] VPN_PASS defined as ''
2020-05-13 21:03:16.509302 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-05-13 21:03:16.534900 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-05-13 21:03:16.561437 [info] ENABLE_PRIVOXY defined as 'yes'
2020-05-13 21:03:16.594030 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-05-13 21:03:16.628286 [info] Deleting files in /tmp (non recursive)...
2020-05-13 21:03:16.654112 [info] Starting Supervisor...
2020-05-13 21:03:16,818 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-05-13 21:03:16,818 INFO Set uid to user 0 succeeded
2020-05-13 21:03:16,820 INFO supervisord started with pid 7
2020-05-13 21:03:17,823 INFO spawned: 'start-script' with pid 167
2020-05-13 21:03:17,826 INFO spawned: 'watchdog-script' with pid 168
2020-05-13 21:03:17,826 INFO reaped unknown pid 8
2020-05-13 21:03:17,834 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-05-13 21:03:17,835 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-05-13 21:03:17,835 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-05-13 21:03:17,847 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2020-05-13 21:03:17,898 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-05-13 21:03:17,903 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-05-13 21:03:17,905 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-05-13 21:03:17,910 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-05-13 21:03:17,913 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-05-13 21:03:17,916 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-05-13 21:03:17,921 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-05-13 21:03:17,924 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-05-13 21:03:17,928 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-05-13 21:03:17,980 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2020-05-13 21:03:17,981 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.107-Unraid

2020-05-13 21:03:17,981 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2020-05-13 21:03:17,982 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2020-05-13 21:03:17,982 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'

2020-05-13 21:03:18,003 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-05-13 21:03:18,007 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2020-05-13 21:03:18,008 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-05-13 21:03:18,009 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.4
192.168.1.0/24 via 172.17.0.1 dev eth0

2020-05-13 21:03:18,009 DEBG 'start-script' stdout output:
--------------------

2020-05-13 21:03:18,063 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-05-13 21:03:18,065 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-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 -s 192.168.1.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 INPUT -i 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 -s 172.17.0.0/16 -d 192.168.1.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
-A OUTPUT -o tun0 -j ACCEPT

2020-05-13 21:03:18,066 DEBG 'start-script' stdout output:
--------------------

2020-05-13 21:03:18,068 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2020-05-13 21:03:18,075 DEBG 'start-script' stdout output:
Wed May 13 21:03:18 2020 WARNING: file 'credentials.conf' is group or others accessible
Wed May 13 21:03:18 2020 OpenVPN 2.4.8 [git:makepkg/3976acda9bf10b5e+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan 3 2020
Wed May 13 21:03:18 2020 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10

2020-05-13 21:03:18,076 DEBG 'start-script' stdout output:
[info] OpenVPN started

2020-05-13 21:03:18,077 DEBG 'start-script' stdout output:
Wed May 13 21:03:18 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-05-13 21:03:18,078 DEBG 'start-script' stdout output:
Wed May 13 21:03:18 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]
Wed May 13 21:03:18 2020 UDP link local: (not bound)
Wed May 13 21:03:18 2020 UDP link remote: [AF_INET]

2020-05-13 21:03:18,250 DEBG 'start-script' stdout output:
Wed May 13 21:03:18 2020 [c3288ea57944d8030ec4fc9939569fb7] Peer Connection Initiated with [AF_INET]

2020-05-13 21:03:19,373 DEBG 'start-script' stdout output:
Wed May 13 21:03:19 2020 TUN/TAP device tun0 opened
Wed May 13 21:03:19 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-05-13 21:03:19,375 DEBG 'start-script' stdout output:
Wed May 13 21:03:19 2020 /usr/bin/ip addr add dev tun0 local 10.48.10.10 peer 10.48.10.9

2020-05-13 21:03:19,377 DEBG 'start-script' stdout output:
Wed May 13 21:03:19 2020 /root/openvpnup.sh tun0 1500 1558 10.48.10.10 10.48.10.9 init

2020-05-13 21:03:19,386 DEBG 'start-script' stdout output:
Wed May 13 21:03:19 2020 Initialization Sequence Completed

2020-05-13 21:03:19,508 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-montreal.privateinternetaccess.com' is port forward enabled...

2020-05-13 21:03:19,513 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2020-05-13 21:03:19,920 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2020-05-13 21:03:19,987 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-05-13 21:03:19,988 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-05-13 21:03:19,995 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=7d24f8ae5b6dd5a5f8f8380f005bc3333099c58a3ef84c010aadc6cdb3eb87d7...

2020-05-13 21:03:20,479 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=7d24f8ae5b6dd5a5f8f8380f005bc3333099c58a3ef84c010aadc6cdb3eb87d7, response code 200

2020-05-13 21:03:20,515 DEBG 'start-script' stdout output:
[info] Successfully assigned incoming port 24433

2020-05-13 21:03:20,515 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-05-13 21:03:20,698 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address ''

2020-05-13 21:03:20,700 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-05-13 21:03:20,927 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 

2020-05-13 21:03:20,994 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.48.10.10 different, marking for reconfigure

2020-05-13 21:03:21,004 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2020-05-13 21:03:21,012 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2020-05-13 21:03:21,022 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2020-05-13 21:03:21,022 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 24433 different, marking for reconfigure
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2020-05-13 21:03:21,345 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.82.10.6'
[info] Deluge key 'listen_interface' will have a new value '10.48.10.10'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-05-13 21:03:21,528 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-05-13 21:03:21,691 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '2764f3fde14944b381d5a620d1a3dc7f'
[info] Deluge key 'default_daemon' will have a new value '2764f3fde14944b381d5a620d1a3dc7f'
[info] Writing changes to Deluge config file '/config/web.conf'...

2020-05-13 21:03:21,976 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-05-13 21:03:22,191 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-05-13 21:03:24,219 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-05-13 21:03:26,320 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (24433, 24433)
Configuration value successfully updated.

2020-05-13 21:03:28,472 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2020-05-13 21:03:28,473 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2020-05-13 21:03:28,473 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2020-05-13 21:03:28,480 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2020-05-13 21:03:29,492 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2020-05-13 21:03:29,497 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118