[Support] binhex - DelugeVPN


Recommended Posts

I’m having trouble with download and completed folders. 
 

in the configs on unraid I have it set to /mnt/user/media/downloads/

 

in deluge I have downloads set to /incomplete and move completed to /completed

 

when deluge downloads it just downloads to /downloads not /incomplete and then it won’t move the files when completed. 
 

thanks. 

Link to comment
9 hours ago, binhex said:

It is free for pushes and pulls (limited) I'm assuming what you are referring to is automated builds on docker hub infrastructure, this is no longer free, check out GitHub workflows instead.

Sent from my CLT-L09 using Tapatalk
 

Thanks will check that out.  I used to manually go into DockerHub and manually trigger a build. 

 

I think I will make a stand alone Flexget and use the Network of none and extra params --net=container:DelugeVPN.   Too hard to maintain my DelugeVPN-flexget. 

Edited by Paul_Ber
Link to comment
3 minutes ago, Tenno said:

That didn’t work. It created a new folder in my app data/binhex delugevpn/ called downloads and completed in that…

 

So in the config you have "Host Path 2" set to /mnt/user/media/downloads/ and in deluge you have set like this image.

 

506398462_Screenshot2021-10-09142905.png.085033892cb95d3944c72f5c57a9d5f8.png

Link to comment

Was using normal deluge and got a DMCA from ISP so now I'm here using a VPN like I should have always done.

 

I'm having trouble where randomly the download/upload speeds are limited to under 50kbs. The only way to fix this is to restart the container and then my speeds are fine until it happens again randomly.

 

VPN is PIA and using wireguard option. I have changed the endpoint to a location closer to me.

 

Here is a system log. Not sure if this has any info to help.

 

Oct 8 12:07:11 and Oct 8 16:47:54 are the times when I had to restart the container.

Quote

Oct 8 03:00:23 Impulse avahi-daemon[8662]: New relevant interface veth024c338.IPv6 for mDNS.
Oct 8 03:00:23 Impulse avahi-daemon[8662]: Registering new address record for fe80::481a:3aff:fe9b:a806 on veth024c338.*.
Oct 8 03:21:37 Impulse kernel: TCP: request_sock_TCP: Possible SYN flooding on port 33967. Sending cookies. Check SNMP counters.
Oct 8 03:40:16 Impulse crond[2081]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Oct 8 08:12:59 Impulse kernel: TCP: request_sock_TCP: Possible SYN flooding on port 24919. Sending cookies. Check SNMP counters.
Oct 8 11:08:55 Impulse kernel: mlx4_en: eth1: Link Up
Oct 8 11:08:55 Impulse kernel: br1: port 1(eth1) entered blocking state
Oct 8 11:08:55 Impulse kernel: br1: port 1(eth1) entered forwarding state
Oct 8 12:07:11 Impulse kernel: veth516a8b9: renamed from eth0
Oct 8 12:07:11 Impulse kernel: docker0: port 1(veth024c338) entered disabled state
Oct 8 12:07:12 Impulse avahi-daemon[8662]: Interface veth024c338.IPv6 no longer relevant for mDNS.
Oct 8 12:07:12 Impulse avahi-daemon[8662]: Leaving mDNS multicast group on interface veth024c338.IPv6 with address fe80::***.
Oct 8 12:07:12 Impulse kernel: docker0: port 1(veth024c338) entered disabled state
Oct 8 12:07:12 Impulse kernel: device veth024c338 left promiscuous mode
Oct 8 12:07:12 Impulse kernel: docker0: port 1(veth024c338) entered disabled state
Oct 8 12:07:12 Impulse avahi-daemon[8662]: Withdrawing address record for fe80::*** on veth024c338.
Oct 8 12:07:13 Impulse kernel: docker0: port 1(vethdc23ddc) entered blocking state
Oct 8 12:07:13 Impulse kernel: docker0: port 1(vethdc23ddc) entered disabled state
Oct 8 12:07:13 Impulse kernel: device vethdc23ddc entered promiscuous mode
Oct 8 12:07:13 Impulse kernel: docker0: port 1(vethdc23ddc) entered blocking state
Oct 8 12:07:13 Impulse kernel: docker0: port 1(vethdc23ddc) entered forwarding state
Oct 8 12:07:13 Impulse kernel: docker0: port 1(vethdc23ddc) entered disabled state
Oct 8 12:07:14 Impulse kernel: eth0: renamed from veth75c5376
Oct 8 12:07:14 Impulse kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethdc23ddc: link becomes ready
Oct 8 12:07:14 Impulse kernel: docker0: port 1(vethdc23ddc) entered blocking state
Oct 8 12:07:14 Impulse kernel: docker0: port 1(vethdc23ddc) entered forwarding state
Oct 8 12:07:16 Impulse avahi-daemon[8662]: Joining mDNS multicast group on interface vethdc23ddc.IPv6 with address fe80::***.
Oct 8 12:07:16 Impulse avahi-daemon[8662]: New relevant interface vethdc23ddc.IPv6 for mDNS.
Oct 8 12:07:16 Impulse avahi-daemon[8662]: Registering new address record for fe80::*** on vethdc23ddc.*.
Oct 8 12:32:13 Impulse kernel: mlx4_en: eth1: Link Down
Oct 8 12:32:14 Impulse kernel: br1: port 1(eth1) entered disabled state
Oct 8 12:35:05 Impulse kernel: TCP: request_sock_TCP: Possible SYN flooding on port 33948. Sending cookies. Check SNMP counters.
Oct 8 13:44:23 Impulse kernel: TCP: request_sock_TCP: Possible SYN flooding on port 33948. Sending cookies. Check SNMP counters.
Oct 8 15:29:55 Impulse kernel: TCP: request_sock_TCP: Possible SYN flooding on port 45751. Sending cookies. Check SNMP counters.
Oct 8 15:40:02 Impulse kernel: mlx4_en: eth1: Link Up
Oct 8 15:40:02 Impulse kernel: br1: port 1(eth1) entered blocking state
Oct 8 15:40:02 Impulse kernel: br1: port 1(eth1) entered forwarding state
Oct 8 16:47:54 Impulse kernel: veth75c5376: renamed from eth0
Oct 8 16:47:54 Impulse kernel: docker0: port 1(vethdc23ddc) entered disabled state
Oct 8 16:47:55 Impulse avahi-daemon[8662]: Interface vethdc23ddc.IPv6 no longer relevant for mDNS.
Oct 8 16:47:55 Impulse avahi-daemon[8662]: Leaving mDNS multicast group on interface vethdc23ddc.IPv6 with address fe80::***.
Oct 8 16:47:55 Impulse kernel: docker0: port 1(vethdc23ddc) entered disabled state
Oct 8 16:47:55 Impulse kernel: device vethdc23ddc left promiscuous mode
Oct 8 16:47:55 Impulse kernel: docker0: port 1(vethdc23ddc) entered disabled state
Oct 8 16:47:55 Impulse avahi-daemon[8662]: Withdrawing address record for fe80::*** on vethdc23ddc.
Oct 8 16:47:56 Impulse kernel: docker0: port 1(veth88cc443) entered blocking state
Oct 8 16:47:56 Impulse kernel: docker0: port 1(veth88cc443) entered disabled state
Oct 8 16:47:56 Impulse kernel: device veth88cc443 entered promiscuous mode
Oct 8 16:47:56 Impulse kernel: docker0: port 1(veth88cc443) entered blocking state
Oct 8 16:47:56 Impulse kernel: docker0: port 1(veth88cc443) entered forwarding state
Oct 8 16:47:56 Impulse kernel: docker0: port 1(veth88cc443) entered disabled state
Oct 8 16:47:57 Impulse kernel: eth0: renamed from veth866eccd
Oct 8 16:47:57 Impulse kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth88cc443: link becomes ready
Oct 8 16:47:57 Impulse kernel: docker0: port 1(veth88cc443) entered blocking state
Oct 8 16:47:57 Impulse kernel: docker0: port 1(veth88cc443) entered forwarding state
Oct 8 16:47:59 Impulse avahi-daemon[8662]: Joining mDNS multicast group on interface veth88cc443.IPv6 with address fe80::***.
Oct 8 16:47:59 Impulse avahi-daemon[8662]: New relevant interface veth88cc443.IPv6 for mDNS.
Oct 8 16:47:59 Impulse avahi-daemon[8662]: Registering new address record for fe80::*** on veth88cc443.*.

 

Any ideas as why this is happening?

Edited by ShadyDeth
Link to comment
6 minutes ago, ShadyDeth said:

 

So in the config you have "Host Path 2" set to /mnt/user/media/downloads/ and in deluge you have set like this image.

 

506398462_Screenshot2021-10-09142905.png.085033892cb95d3944c72f5c57a9d5f8.png

Yes exactly like that. It’s still downloading to mnt/user/media/downloads not an /incomplete folder in downloads and then it moves them to the app data folder for deluge…

Link to comment
35 minutes ago, Tenno said:

Yes exactly like that. It’s still downloading to mnt/user/media/downloads not an /incomplete folder in downloads and then it moves them to the app data folder for deluge…

Make a Screenshot from your Host Path set in the docker container settings.

Link to comment
1 hour ago, boris said:

remove the last "/" so it is /mnt/user/media/downloads


didit fix it and also /data/incomplete/completed makes it so the files don’t download at all I found. Only reason they did before is because they were added under /incomplete which still downloads to the …/media/downloads folder. Should I have it set to /downloads/incomplete?

Link to comment

Can't seem to access the Web UI after switching to Wireguard. Using Mullvad as my VPN, and I can't see any errors or anything in my logs. I can connect with VPN disabled. I am accessing the network from a tunneled Wireguard connection into unraid if that matters, and I added the /sbin/modules iptable_mangle from my unraid console to my gofile.  supervisord.log

 

 

Edited by cooltot
Link to comment

Now that DockerHub on the free plan doesn't you build anymore I am just going to use Binhex-DelugeVPN.

 

I did find a Docker on DockerHub for Flexget so I made a template for Unraid.

 

I have the template use extra params to use the network of binhex-delugevpn.   Seems to work fine.   Haven figured out how to connect to the Flexget webui, although the webui isn't really needed and if you want to manually run Flexget then use console.

 

https://github.com/paulpoco/docker-templates/blob/master/paulpoco/flexget.xml

 

@binhex how do I access the webui of a Docker that is using the network of -net=container:binhex-delugevpn ?    

 

Edit: I solved with question Q24 from VPN FAQ, all working as needed   https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Edited by Paul_Ber
I solved my question
Link to comment
22 hours ago, ShadyDeth said:

Was using normal deluge and got a DMCA from ISP so now I'm here using a VPN like I should have always done.

 

I'm having trouble where randomly the download/upload speeds are limited to under 50kbs. The only way to fix this is to restart the container and then my speeds are fine until it happens again randomly.

 

VPN is PIA and using wireguard option. I have changed the endpoint to a location closer to me.

 

Here is a system log. Not sure if this has any info to help.

 

Oct 8 12:07:11 and Oct 8 16:47:54 are the times when I had to restart the container.

 

Any ideas as why this is happening?

You need to be using an endpoint that supports port forwarding or your speeds will be limited. Open up the Deluge log at startup, it lists all the endpoints that support port forwarding.

Link to comment

Hi, I am having trouble accessing Deluge webUI (through firefox giving "problem loading page") whether VPN_ENABLED is on or off.

I do not have a proxy and the IP address of the device that I'm trying to access Web UI is 192.168.1.2, an internal IP.

 

Any help is greatly appreciated.

 

supervisord.txt

Edited by InerrantEye
Link to comment
2 hours ago, InerrantEye said:

Hi, I am having trouble accessing Deluge webUI (through firefox giving "problem loading page") whether VPN_ENABLED is on or off.

I do not have a proxy and the IP address of the device that I'm trying to access Web UI is 192.168.1.2, an internal IP.

 

Any help is greatly appreciated.

 

supervisord.txt 16.5 kB · 0 downloads

no obvious issues there, so i suspect you have misconfigured the LAN_NETWORK, from your log:-

LAN_NETWORK defined as '192.168.1.0/24'

see Q4 :- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

edit - if your lan is correct (sounds like it maybe ok from the ip you listed above) then attempt access from another device on your network, also try a different browser to ensure your issue isnt browser related.

Link to comment
2 hours ago, binhex said:

no obvious issues there, so i suspect you have misconfigured the LAN_NETWORK, from your log:-

LAN_NETWORK defined as '192.168.1.0/24'

see Q4 :- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

edit - if your lan is correct (sounds like it maybe ok from the ip you listed above) then attempt access from another device on your network, also try a different browser to ensure your issue isnt browser related.

 

Hi, I've recalculated the LAN_NETWORK and still got the same result. I've port forwarded port 8112 and DMZ'd to no luck. I've tried a different device and used 2 other browsers.

 

Not sure what else to try.

Link to comment
6 hours ago, InerrantEye said:

 

Hi, I've recalculated the LAN_NETWORK and still got the same result. I've port forwarded port 8112 and DMZ'd to no luck. I've tried a different device and used 2 other browsers.

 

Not sure what else to try.

It is a local network, so you don't need port forwarding. Do you maybe have VLAN enabled and your unraid machine is in a different VLAN? Maybe install and try firefox inside unraid from the Apps tab. 

Edited by boris
Link to comment

Hi

 

I have been having trouble getting the DelugeVPN docker to function properly for the last two days. All of a sudden I couldn't connect to the webserver anymore, and after checking the logs I see this;

 

2021-10-11 00:25:20,842 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

2021-10-11 00:25:20,843 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 1423, in run
    self.mainLoop()
  File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 1433, in mainLoop
    reactorBaseSelf.runUntilCurrent()
  File "/usr/lib/python3.9/site-packages/twisted/internet/base.py", line 999, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "/usr/lib/python3.9/site-packages/twisted/internet/task.py", line 232, in __call__
    d = defer.maybeDeferred(self.f, *self.a, **self.kw)
--- <exception caught here> ---
  File "/usr/lib/python3.9/site-packages/twisted/internet/defer.py", line 167, in maybeDeferred
    result = f(*args, **kw)
  File "/usr/lib/python3.9/site-packages/deluge/core/alertmanager.py", line 70, in update
    self.handle_alerts()
  File "/usr/lib/python3.9/site-packages/deluge/core/alertmanager.py", line 138, in handle_alerts
    **{
  File "/usr/lib/python3.9/site-packages/deluge/core/alertmanager.py", line 139, in <dictcomp>
    attr: getattr(alert, attr)
builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe5 in position 34: invalid continuation byte

 

I had some trouble a few months ago with DelugeVPN which was solved by reinstalling the docker, so I tried doing the same again. It seemed to work fine for a few hours, I re-added a lot of torrents, and after DelugeVPN had rechecked most of the files I again got an error saying "The connection to the web server has been lost". After this I haven't been able to access the web server for more than a moment.

 

After checking logs another time I again tried reinstalling the docker, but now I can barely open the web UI before it locks down with "the connection to the web server has been lost".

In addition and possibly unrelated - earlier today I also had trouble accessing the docker because it seemed Private Internet Access was having problems. When I disabled the VPN part of the docker it started, but I still couldn't access the Web UI due to the error message above. A few hours later PIA seemed to have fixed their problems, but still no Web UI access.

 

Does anyone have any idea what the problem could be? I have attached the log file from before I reinstalled and a log file from the latest reinstall. 

 

Unraid version: 6.9.1
CPU: Intel i3 8350K

Motherboard: Asus Rog Strix Z370-F Gaming. BIOS from 01.12.2017

Controller card: LSI SAS-9211-8i

Disks: Eight Seagate ranging from 8 to 16 TB, mainly Ironwolf-disks.

PSU: EVGA Supernova G3 750W

 

supervisord (new install).log supervisord (old install).log

Link to comment

Hi all. Having trouble connecting to the DelugeVPN Web UI. I have gone through the FAQ docs as it has helped me get things going in the past, but I was unable to find a fix for this current iteration of the problem. Would really appreciate it if someone could point me in the right direction based off of these logs! Also attaching a screenshot of my .ovpn file config, which I have edited slightly to comply with the problem listed in Q22 of the FAQ.2043843539_ScreenShot2021-10-12at1_03_01PM.thumb.png.7ad1bda3c96f52385fcfd0bbb1a366e1.pngdelugevpn_log_091221.rtf

Link to comment

AutoAdd Issue in Deluge

 

First, let me say that I've benefited greatly from this container and the help in this thread, so thank you all. And although I'm running the container on a Synology unit, I thought I'd finally give something back here for anyone who may be having a similar issue.

 

Background

Container was running great for me up to binhex/arch-delugevpn:2.0.3-2-01, but any time I upgraded past that I had problems with Deluge's AutoAdd functionality (basically its "watch" directory capability that was formerly an external plugin that is now baked into Deluge itself). Certain elements worked like Radarr/Sonnar integration, but other elements broke, like when I used manual search inside Jackett, which relies on a blackhole watch folder. I ended up just rolling back the container, it worked fine again, and I stopped worrying about it for a while. However, with the new (rare) potential for IP leakage, it's been nagging at me to move to the new container versions. Initially, I wasn't sure if it was the container, the VPN, or Deluge itself, but it always kind of felt like Deluge given the VPN was up, I could download torrents, and Radarr/Sonarr integration worked -- it was only the AutoAdd turning itself off and not behaving itself when using Jackett manual searches that wasn't working. I'm actually surprised I haven't seen more comments about this here because of how AWESOME using Jackett this way is! (Y'all are missing out, LOL).

 

The Fix

I finally put my mind to figuring this out once and for all yesterday, and I believe I tracked it down. Turns out the baked-into-Deluge AutoAdd is currently broken for certain applications (like watching for Magnets), and that version is in the current BinHex containers. Even though the fix hasn't been promoted into Deluge yet (so of course not in the container yet either), there is a manual fix available, and it's easy (just drop an updated AutoAdd egg into the Deluge PlugIns folder and it will take precedence over the baked-in version). I will say that I literally just implemented and tested, so it's possible I'll still run into problems, but it's looking promising at the moment.

 

Thanks again for this container and this thread, enjoy!

 

The temporary fix can be found here

Edited by SomeDudeUsingDockers
  • Like 2
  • Thanks 2
Link to comment

I've been trying to get this setup all day, and followed several guides. Can't seem to find a problem, even the log to me looks good and doesnt show any errors, but when I try to launch the webUI it just cant be reached. Could anyone take a look at my settings and see if anything stands out? or point out an error i am missing, or misunderstanding.


Im using Unraid 6.8.2 with the binhex-delugevpn container.
My deluge settings screen can be seen here, and my docker settings here
No matter what I try to do opening the WebUI results in :  "This site can’t be reached, 192.168.2.200 refused to connect."

Can anyone offer any guidance at all? Doesnt seem to work even if I turn off the VPN option either...

Ive added the montreal server, and certs from : https://www.privateinternetaccess.com/openvpn/openvpn.zip

root@Tower:/mnt/user/appdata/binhex-delugevpn/openvpn# ls -la
total 17
drwxrwxr-x 1 nobody users  176 Oct 14 15:17 ./
drwxrwxr-x 1 nobody users  832 Oct 14 15:17 ../
-rwxrwxr-x 1 nobody users 2025 Nov 19  2020 ca.rsa.2048.crt*
-rwxrwxr-x 1 nobody users 3164 Oct 14 15:17 ca_montreal.ovpn*
-rwxrwxr-x 1 nobody users   18 Oct 14 15:17 credentials.conf*
-rwxrwxr-x 1 nobody users  869 Nov 19  2020 crl.rsa.2048.pem*


My ifconfig looks like so:

root@Tower:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500 ether 1c:6f:65:d9:67:17  txqueuelen 1000  (Ethernet) RX packets 7752025  bytes 10844401490 (10.0 GiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 4039805  bytes 1478951027 (1.3 GiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500 inet 192.168.2.200  netmask 255.255.255.0  broadcast 0.0.0.0 ether 1c:6f:65:d9:67:17  txqueuelen 1000  (Ethernet) RX packets 7447379  bytes 10720011315 (9.9 GiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 4039836  bytes 1478392689 (1.3 GiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500 inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255 inet6 fe80::42:6ff:fe57:3a44  prefixlen 64  scopeid 0x20<link> ether 02:42:06:57:3a:44  txqueuelen 0  (Ethernet) RX packets 2967268  bytes 199171145 (189.9 MiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 6608997  bytes 10234027166 (9.5 GiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500 ether 1c:6f:65:d9:67:17  txqueuelen 1000  (Ethernet) RX packets 7752025  bytes 10844401490 (10.0 GiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 4039805  bytes 1478951027 (1.3 GiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536 inet 127.0.0.1  netmask 255.0.0.0 inet6 ::1  prefixlen 128  scopeid 0x10<host> loop  txqueuelen 1000  (Local Loopback) RX packets 1125049  bytes 180185356 (171.8 MiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 1125049  bytes 180185356 (171.8 MiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
veth3ad0513: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500 inet6 fe80::2495:3dff:fe80:eddd  prefixlen 64  scopeid 0x20<link> ether 26:95:3d:80:ed:dd  txqueuelen 0  (Ethernet) RX packets 297  bytes 41532 (40.5 KiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 314  bytes 161691 (157.9 KiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vethadc693e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500 inet6 fe80::a480:80ff:feff:3433  prefixlen 64  scopeid 0x20<link> ether a6:80:80:ff:34:33  txqueuelen 0  (Ethernet) RX packets 37363  bytes 6223584 (5.9 MiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 39591  bytes 35893743 (34.2 MiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vethbe5c793: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500 inet6 fe80::e803:46ff:feb8:d61e  prefixlen 64  scopeid 0x20<link> ether ea:03:46:b8:d6:1e  txqueuelen 0  (Ethernet) RX packets 2914105  bytes 232320924 (221.5 MiB) RX errors 0  dropped 0  overruns 0  frame 0 TX packets 6555141  bytes 10193301441 (9.4 GiB) TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


and my deluge log looks like this:

https://hub.docker.com/u/binhex/

2021-10-14 15:17:02.222153 [info] Host is running unRAID
2021-10-14 15:17:02.247578 [info] System information Linux 039d91cca154 4.19.98-Unraid #1 SMP Sun Jan 26 09:15:03 PST 2020 x86_64 GNU/Linux
2021-10-14 15:17:02.276036 [info] OS_ARCH defined as 'x86-64'
2021-10-14 15:17:02.303416 [info] PUID defined as '99'
2021-10-14 15:17:02.396788 [info] PGID defined as '100'
2021-10-14 15:17:02.576331 [info] UMASK defined as '000'
2021-10-14 15:17:02.603182 [info] Permissions already set for volume mappings
2021-10-14 15:17:02.633232 [info] Deleting files in /tmp (non recursive)...
2021-10-14 15:17:02.664097 [info] VPN_ENABLED defined as 'yes'
2021-10-14 15:17:02.691026 [info] VPN_CLIENT defined as 'openvpn'
2021-10-14 15:17:02.718088 [info] VPN_PROV defined as 'pia'
2021-10-14 15:17:03.145137 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca_montreal.ovpn
2021-10-14 15:17:03.195860 [info] VPN remote server(s) defined as 'ca-montreal.privacy.network,'
2021-10-14 15:17:03.220580 [info] VPN remote port(s) defined as '1198,'
2021-10-14 15:17:03.246743 [info] VPN remote protcol(s) defined as 'udp,'
2021-10-14 15:17:03.282958 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-10-14 15:17:03.311370 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-10-14 15:17:03.340731 [info] LAN_NETWORK defined as '192.168.2.0/24'
2021-10-14 15:17:03.367157 [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'
2021-10-14 15:17:03.394004 [info] VPN_USER defined as '----'
2021-10-14 15:17:03.420245 [info] VPN_PASS defined as '----'
2021-10-14 15:17:03.446688 [info] STRICT_PORT_FORWARD defined as 'yes'
2021-10-14 15:17:03.473126 [info] ENABLE_PRIVOXY defined as 'yes'
2021-10-14 15:17:03.501868 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2021-10-14 15:17:03.528426 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2021-10-14 15:17:03.555550 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2021-10-14 15:17:03.582054 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2021-10-14 15:17:03.612661 [info] Starting Supervisor...
2021-10-14 15:17:03,823 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2021-10-14 15:17:03,823 INFO Set uid to user 0 succeeded
2021-10-14 15:17:03,825 INFO supervisord started with pid 6
2021-10-14 15:17:04,827 INFO spawned: 'shutdown-script' with pid 188
2021-10-14 15:17:04,829 INFO spawned: 'start-script' with pid 189
2021-10-14 15:17:04,830 INFO spawned: 'watchdog-script' with pid 190
2021-10-14 15:17:04,830 INFO reaped unknown pid 7 (exit status 0)
2021-10-14 15:17:04,835 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2021-10-14 15:17:04,835 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-10-14 15:17:04,835 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-10-14 15:17:04,835 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-10-14 15:17:04,872 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2021-10-14 15:17:04,875 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2021-10-14 15:17:04,877 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2021-10-14 15:17:04,880 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2021-10-14 15:17:04,882 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2021-10-14 15:17:04,885 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2021-10-14 15:17:04,888 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2021-10-14 15:17:04,890 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2021-10-14 15:17:05,084 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2021-10-14 15:17:05,095 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2021-10-14 15:17:05,098 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.0/24 as route via docker eth0

2021-10-14 15:17:05,099 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2021-10-14 15:17:05,100 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.2.0/24 via 172.17.0.1 dev eth0
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.4
local 172.17.0.4 dev eth0 table local proto kernel scope host src 172.17.0.4
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.4

2021-10-14 15:17:05,100 DEBG 'start-script' stdout output:
--------------------

2021-10-14 15:17:05,102 DEBG 'start-script' stdout output:
iptable_mangle 16384 0
ip_tables 24576 4 iptable_filter,iptable_raw,iptable_nat,iptable_mangle

2021-10-14 15:17:05,103 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2021-10-14 15:17:05,171 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2021-10-14 15:17:05,172 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 -s 172.98.71.21/32 -i eth0 -j ACCEPT
-A INPUT -s 172.98.71.41/32 -i eth0 -j ACCEPT
-A INPUT -s 172.98.71.51/32 -i eth0 -j ACCEPT
-A INPUT -s 172.98.71.12/32 -i eth0 -j ACCEPT
-A INPUT -s 172.98.71.31/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.2.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.2.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -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 -d 172.98.71.21/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.98.71.41/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.98.71.51/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.98.71.12/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.98.71.31/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.2.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.2.0/24 -o eth0 -p tcp -m tcp --sport 8118 -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

2021-10-14 15:17:05,173 DEBG 'start-script' stdout output:
--------------------

2021-10-14 15:17:05,174 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2021-10-14 15:17:05,187 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.


2021-10-14 15:17:05,187 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 WARNING: file 'credentials.conf' is group or others accessible

2021-10-14 15:17:05 OpenVPN 2.5.1 [git:makepkg/f186691b32e68362+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 24 2021
2021-10-14 15:17:05 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10
2021-10-14 15:17:05 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2021-10-14 15:17:05,188 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 CRL: loaded 1 CRLs from file -----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-----


2021-10-14 15:17:05,188 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.71.12:1198
2021-10-14 15:17:05 UDP link local: (not bound)
2021-10-14 15:17:05 UDP link remote: [AF_INET]172.98.71.12:1198

2021-10-14 15:17:05,338 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 [montreal403] Peer Connection Initiated with [AF_INET]172.98.71.12:1198

2021-10-14 15:17:05,379 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 TUN/TAP device tun0 opened
2021-10-14 15:17:05 net_iface_mtu_set: mtu 1500 for tun0
2021-10-14 15:17:05 net_iface_up: set tun0 up

2021-10-14 15:17:05,379 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 net_addr_v4_add: 10.10.112.237/24 dev tun0
2021-10-14 15:17:05 /root/openvpnup.sh tun0 1500 1553 10.10.112.237 255.255.255.0 init

2021-10-14 15:17:05,380 DEBG 'start-script' stdout output:
2021-10-14 15:17:05 Initialization Sequence Completed

2021-10-14 15:17:07,549 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2021-10-14 15:17:07,711 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 172.98.71.12

2021-10-14 15:17:07,712 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2021-10-14 15:17:07,712 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-montreal.privacy.network' is port forward enabled...

2021-10-14 15:17:08,147 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-montreal.privacy.network' is in the list of endpoints that support port forwarding

2021-10-14 15:17:08,148 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2021-10-14 15:17:08,148 DEBG 'start-script' stdout output:
[info] al.privacy.network
[info] ad.privacy.network
[info] austria.privacy.network
[info] brussels.privacy.network
[info] ba.privacy.network
[info] sofia.privacy.network
[info] zagreb.privacy.network
[info] czech.privacy.network
[info] denmark.privacy.network
[info] ee.privacy.network
[info] fi.privacy.network
[info] fi-2.privacy.network
[info] france.privacy.network
[info] de-berlin.privacy.network

2021-10-14 15:17:08,148 DEBG 'start-script' stdout output:
[info] de-frankfurt.privacy.network
[info] gr.privacy.network
[info] hungary.privacy.network
[info] is.privacy.network
[info] ireland.privacy.network
[info] man.privacy.network
[info] italy.privacy.network
[info] italy-2.privacy.network
[info] lv.privacy.network
[info] liechtenstein.privacy.network
[info] lt.privacy.network
[info] lu.privacy.network
[info] mk.privacy.network
[info] malta.privacy.network
[info] md.privacy.network
[info] monaco.privacy.network
[info] nl-amsterdam.privacy.network
[info] no.privacy.network
[info] poland.privacy.network

2021-10-14 15:17:08,148 DEBG 'start-script' stdout output:
[info] pt.privacy.network
[info] ro.privacy.network
[info] rs.privacy.network
[info] sk.privacy.network
[info] spain.privacy.network
[info] sweden.privacy.network
[info] sweden-2.privacy.network
[info] swiss.privacy.network
[info] ua.privacy.network
[info] uk-london.privacy.network
[info] uk-southampton.privacy.network
[info] uk-manchester.privacy.network
[info] uk-2.privacy.network
[info] bahamas.privacy.network
[info] ca-toronto.privacy.network
[info] ca-montreal.privacy.network
[info] ca-vancouver.privacy.network
[info] ca-ontario.privacy.network

2021-10-14 15:17:08,148 DEBG 'start-script' stdout output:
[info] greenland.privacy.network
[info] mexico.privacy.network
[info] panama.privacy.network
[info] ar.privacy.network
[info] br.privacy.network
[info] venezuela.privacy.network
[info] yerevan.privacy.network
[info] bangladesh.privacy.network
[info] cambodia.privacy.network
[info] china.privacy.network
[info] cyprus.privacy.network
[info] georgia.privacy.network
[info] hk.privacy.network
[info] in.privacy.network
[info] israel.privacy.network
[info] japan.privacy.network
[info] japan-2.privacy.network

2021-10-14 15:17:08,149 DEBG 'start-script' stdout output:
[info] kazakhstan.privacy.network
[info] mongolia.privacy.network
[info] philippines.privacy.network
[info] qatar.privacy.network
[info] saudiarabia.privacy.network
[info] sg.privacy.network
[info] srilanka.privacy.network
[info] taiwan.privacy.network
[info] tr.privacy.network
[info] ae.privacy.network
[info] vietnam.privacy.network
[info] au-sydney.privacy.network
[info] aus-melbourne.privacy.network
[info] aus-perth.privacy.network
[info] nz.privacy.network
[info] dz.privacy.network

2021-10-14 15:17:08,149 DEBG 'start-script' stdout output:
[info] egypt.privacy.network
[info] morocco.privacy.network
[info] nigeria.privacy.network
[info] za.privacy.network

2021-10-14 15:17:09,990 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '56070'

2021-10-14 15:17:10,607 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.10.112.237 different, marking for reconfigure

2021-10-14 15:17:10,611 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2021-10-14 15:17:10,614 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2021-10-14 15:17:10,617 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2021-10-14 15:17:10,617 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 56070 different, marking for reconfigure

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

2021-10-14 15:17:10,991 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.10.112.237'
[info] Writing changes to Deluge config file '/config/core.conf'...

2021-10-14 15:17:11,341 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'...

2021-10-14 15:17:11,532 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'b55a2f26ff31a033cbe2e203fc67eb05ef5bbc21'
[info] Deluge key 'default_daemon' will have a new value 'b55a2f26ff31a033cbe2e203fc67eb05ef5bbc21'
[info] Writing changes to Deluge config file '/config/web.conf'...

2021-10-14 15:17:11,341 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'...

2021-10-14 15:17:11,532 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'b55a2f26ff31a033cbe2e203fc67eb05ef5bbc21'
[info] Deluge key 'default_daemon' will have a new value 'b55a2f26ff31a033cbe2e203fc67eb05ef5bbc21'
[info] Writing changes to Deluge config file '/config/web.conf'...

2021-10-14 15:17:11,872 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2021-10-14 15:17:12,084 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2021-10-14 15:17:14,429 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2021-10-14 15:17:16,829 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (56070, 56070)
Configuration value successfully updated.

2021-10-14 15:17:19,296 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2021-10-14 15:17:19,296 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2021-10-14 15:17:19,297 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2021-10-14 15:17:19,297 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2021-10-14 15:17:20,302 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2021-10-14 15:17:20,306 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

Any help would be greatly appreciated!

Link to comment
6 hours ago, xceph said:

No matter what I try to do opening the WebUI results in :  "This site can’t be reached, 192.168.2.200 refused to connect."

what is the network for the host running the web browser?, is it also 192.168.2.x?

Link to comment

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.