[Support] binhex - DelugeVPN


Recommended Posts

Good day, I'm not sure if this has been covered elsewhere in this thread.

 

My delugevpn logs consistently say: "/config/wireguard/wg0.conf' is world accessible"

 

I've checked the internet and the FAQ for this docker, but I'm not sure how this translates to managing it in unRaid.  I'm a PIA user, what changes do I need to make to the wg0.conf file?  I've seen a solution for "chmod 600" to this file, but how do I do that for this docker running in unraid?

 

I appreciate your time.

Link to comment

Been running DelugeVPN on my unraid server for 4 years without issue, and today downloads have started saving to and filling up the docker image. I had to delete the docker image and re-install apps, but no matter what I do, new downloads will not save to the specified download folder and continue to fill up the docker image. I haven't changed anything and cannot figure out how to correct this - any clues?

Link to comment
26 minutes ago, phneutral said:

Been running DelugeVPN on my unraid server for 4 years without issue, and today downloads have started saving to and filling up the docker image. I had to delete the docker image and re-install apps, but no matter what I do, new downloads will not save to the specified download folder and continue to fill up the docker image. I haven't changed anything and cannot figure out how to correct this - any clues?

Post your docker run command or a screenshot of your container template settings. Also post a screenshot of the downloads settings in deluge

 

Edit: Be sure to redact your username/password

Edited by strike
Link to comment
2 hours ago, Salted11 said:

Good day, I'm not sure if this has been covered elsewhere in this thread.

 

My delugevpn logs consistently say: "/config/wireguard/wg0.conf' is world accessible"

 

I've checked the internet and the FAQ for this docker, but I'm not sure how this translates to managing it in unRaid.  I'm a PIA user, what changes do I need to make to the wg0.conf file?  I've seen a solution for "chmod 600" to this file, but how do I do that for this docker running in unraid?

 

I appreciate your time.

 

On 4/14/2021 at 8:38 AM, binhex said:

 

 

it a warning about security permissions on the file, not to be concerned about.

 

I’m sure you could do it from the command line. Don’t think it’s necessary or even a good idea.

Edited by wgstarks
Link to comment
14 hours ago, strike said:

Post your docker run command or a screenshot of your container template settings. Also post a screenshot of the downloads settings in deluge

 

Edit: Be sure to redact your username/password

 

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='DelugeVPN' --net='bridge' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXX.com' -e 'VPN_PASS'='XXXX' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn'
4fa52ea739407aca6f115f18b43d7c2954d3278554e369d230327475934063b4



The command finished successfully!

 

 

 

image.png.bcae8745af35f82e626939b27bdd26a4.png

 

Thank you for replying - here it is 

Edited by phneutral
Link to comment

Hey @binhex

First of all thanks for this docker image.

 

I was wondering if it's possible to have a startup script?

Let's say if I wan't to install 7zip (pacman -S p7zip), so I don't have to manually do it every time the container gets updated?

I'm using a plugin for deluge that extracts archived files, but it's disabling support for .7z files.

Link to comment
7 hours ago, mikl said:

Hey @binhex

First of all thanks for this docker image.

 

I was wondering if it's possible to have a startup script?

Let's say if I wan't to install 7zip (pacman -S p7zip), so I don't have to manually do it every time the container gets updated?

I'm using a plugin for deluge that extracts archived files, but it's disabling support for .7z files.

simpler for me to include it, which im happy to do as its a small package, look for it in the next image release.

  • Like 1
Link to comment

Hi every body and happy new year. One of my new years resolution last year was to have my media server fully functional as I want it to work. Long story short that didn't happen so nows the plan to finish that.

Regarding Delauge it DL files at full speed, but UL is really slow, and moste of the time there is no UL going on.

 

My router is Ubiquiti USG and I have enabled UPnP on it.
I am not running any VPN at the moment  while I am figuring this out.

I have been trying a lot of things, but nothing seems to be in the right direction

 

If any one can assist it would be much apprichiated.

Screenshot 2022-01-03 at 01-21-25 Valholl UpdateContainer.png

Screenshot 2022-01-03 at 01-27-38 Deluge WebUI 2 0 5.png

Screenshot 2022-01-03 at 01-27-08 Deluge WebUI 2 0 5.png

Screenshot 2022-01-03 at 01-27-00 Deluge WebUI 2 0 5.png

Screenshot 2022-01-03 at 01-26-44 Deluge WebUI 2 0 5.png

Link to comment
18 hours ago, Geiri said:

Regarding Delauge it DL files at full speed, but UL is really slow, and moste of the time there is no UL going on.

classic signs of no incoming port, which from your scrrenshot is confirmed, you basically need to do the following:-

 

router - set up port forward from 58846 tcp and udp to the ip of your unraid server

deluge - untick random incoming port and specify the port as 58846.

 

note - this is ONLY required when NOT using a vpn connection, when using a VPN no port forward is required on your router.

Link to comment
On 1/3/2022 at 8:42 PM, binhex said:

classic signs of no incoming port, which from your scrrenshot is confirmed, you basically need to do the following:-

 

router - set up port forward from 58846 tcp and udp to the ip of your unraid server

deluge - untick random incoming port and specify the port as 58846.

 

note - this is ONLY required when NOT using a vpn connection, when using a VPN no port forward is required on your router.

Thanx binhex for all your contribution to the Unraid community,
I tried your advise, but as soon as I change the port to 58846 and restart deluge I am not able to open it any more. I have tried 3 times from scratch and always same result. After some playing around I noticed that port 58846 is by default the demon port.

 

Why opening an incoming port when I am having trouble with outgoing traffic?

 

I also did try VPN with PIA out (but with another router) and I got simulare result that good DL speed but almost no upload.

Link to comment

Hi Binhex and forum

 

I've just setup delugeVPN running in docker on synology NAS DSM7..

 

If I set VPN_ENABLED = no then I can access webUI at NASip:8112.

 

If I set VPN_ENABLED = yes then I can see the Deluge UI at NASip:8112 but connection says my daemon is "offline".

 

BUT I also access deluge via an android app called Deluge. I can use this app to access deluge with VPN_ENABLED yes or no and it work fine. I can add torrents, download, deluge move completed files. I can even confirm that the VPN is enabled using checkmyiptorrent. 

 

Any idea why I can't access the daemon via webUI with the VPN enabled despite it definitely working? 

Capture.thumb.JPG.fae6290ef55f6c70e4a71e4aa0808963.JPG

Link to comment
11 hours ago, Geiri said:

I tried your advise, but as soon as I change the port to 58846 and restart deluge I am not able to open it any more. I have tried 3 times from scratch and always same result. After some playing around I noticed that port 58846 is by default the demon port.

sorry i am telling you duff info there!, that's what you get for not using this image for a while :-), ok the RIGHT port to port forward is 58946 as you are right that port 58846 is used by the daemon.

Link to comment

I've attached my log below (sorry it's upside down with latest first).

 

I feel like my issue is something simple as

-Deluge is working,

-I can send torrents using a Android Deluge app and they work normally,

-I can call up the web UI at mylanIP:8112

 

but I can't log in as the connection manager says the daemon is offline (which it isn't according to the android app).

 

Any help appreciated!

 

2022-01-07 09:08:13stdout

2022-01-07 09:08:13stdout[info] Deluge Web UI started

2022-01-07 09:08:13stdout2022-01-07 19:38:13,208 DEBG 'watchdog-script' stdout output:

2022-01-07 09:08:13stdout

2022-01-07 09:08:13stdout[info] Starting Deluge Web UI...

2022-01-07 09:08:13stdout2022-01-07 19:38:13,207 DEBG 'watchdog-script' stdout output:

2022-01-07 09:08:13stdout

2022-01-07 09:08:13stdout[info] No torrents with state 'Error' found

2022-01-07 09:08:13stdout2022-01-07 19:38:13,205 DEBG 'watchdog-script' stdout output:

2022-01-07 09:08:03stdout

2022-01-07 09:08:03stdoutConfiguration value successfully updated.

2022-01-07 09:08:03stdoutSetting "listen_ports" to: (44332, 44332)

2022-01-07 09:08:03stdout2022-01-07 19:38:03,650 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:54stdout

2022-01-07 09:07:54stdoutConfiguration value successfully updated.

2022-01-07 09:07:54stdoutSetting "random_port" to: False

2022-01-07 09:07:54stdout2022-01-07 19:37:54,348 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:43stdout

2022-01-07 09:07:43stdout[info] Deluge process listening on port 58846

2022-01-07 09:07:43stdout2022-01-07 19:37:43,221 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:41stdout

2022-01-07 09:07:41stdout[info] Waiting for Deluge process to start listening on port 58846...

2022-01-07 09:07:41stdout[info] Deluge process started

2022-01-07 09:07:41stdout2022-01-07 19:37:41,162 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:39stdout

2022-01-07 09:07:39stdout[info] Writing changes to Deluge config file '/config/web.conf'...

2022-01-07 09:07:39stdout[info] Deluge key 'default_daemon' will have a new value '20855efaeabf4074a60993f9b7415de2'

2022-01-07 09:07:39stdout[info] Deluge key 'default_daemon' currently has a value of '20855efaeabf4074a60993f9b7415de2'

2022-01-07 09:07:39stdout2022-01-07 19:37:39,366 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:38stdout

2022-01-07 09:07:38stdout[info] Writing changes to Deluge config file '/config/core.conf'...

2022-01-07 09:07:38stdout[info] Deluge key 'outgoing_interface' will have a new value 'tun0'

2022-01-07 09:07:38stdout[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'

2022-01-07 09:07:38stdout2022-01-07 19:37:38,866 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:38stdout

2022-01-07 09:07:38stdout[info] Writing changes to Deluge config file '/config/core.conf'...

2022-01-07 09:07:38stdout[info] Deluge key 'listen_interface' will have a new value '10.14.112.5'

2022-01-07 09:07:38stdout[info] Deluge key 'listen_interface' currently has a value of '10.23.112.13'

2022-01-07 09:07:38stdout2022-01-07 19:37:38,019 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:32stdout

2022-01-07 09:07:32stdout[info] Successfully assigned and bound incoming port '44332'

2022-01-07 09:07:32stdout2022-01-07 19:37:32,660 DEBG 'start-script' stdout output:

2022-01-07 09:07:29stdout

2022-01-07 09:07:29stdout[info] Removing deluge pid file (if it exists)...

2022-01-07 09:07:29stdout[info] Attempting to start Deluge...

2022-01-07 09:07:29stdout2022-01-07 19:37:29,783 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:29stdout

2022-01-07 09:07:29stdout[info] Deluge incoming port 6890 and VPN incoming port 44332 different, marking for reconfigure

2022-01-07 09:07:29stdout2022-01-07 19:37:29,765 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:29stdout

2022-01-07 09:07:29stdout[info] Deluge Web UI not running

2022-01-07 09:07:29stdout2022-01-07 19:37:29,765 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:29stdout

2022-01-07 09:07:29stdout[info] Deluge not running

2022-01-07 09:07:29stdout2022-01-07 19:37:29,756 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:29stdout

2022-01-07 09:07:29stdout[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.14.112.5 different, marking for reconfigure

2022-01-07 09:07:29stdout2022-01-07 19:37:29,746 DEBG 'watchdog-script' stdout output:

2022-01-07 09:07:27stdout

2022-01-07 09:07:27stdout[info] bangladesh.privacy.network

2022-01-07 09:07:27stdout[info] israel.privacy.network

2022-01-07 09:07:27stdout[info] taiwan.privacy.network

2022-01-07 09:07:27stdout[info] swiss.privacy.network

2022-01-07 09:07:27stdout[info] mexico.privacy.network

2022-01-07 09:07:27stdout[info] ae.privacy.network

2022-01-07 09:07:27stdout[info] georgia.privacy.network

2022-01-07 09:07:27stdout[info] greenland.privacy.network

2022-01-07 09:07:27stdout[info] aus-perth.privacy.network

2022-01-07 09:07:27stdout[info] uk-london.privacy.network

2022-01-07 09:07:27stdout[info] aus-melbourne.privacy.network

2022-01-07 09:07:27stdout[info] mk.privacy.network

2022-01-07 09:07:27stdout[info] cambodia.privacy.network

2022-01-07 09:07:27stdout[info] panama.privacy.network

2022-01-07 09:07:27stdout[info] ro.privacy.network

2022-01-07 09:07:27stdout[info] sweden.privacy.network

2022-01-07 09:07:27stdout[info] egypt.privacy.network

2022-01-07 09:07:27stdout[info] saudiarabia.privacy.network

2022-01-07 09:07:27stdout[info] nz.privacy.network

2022-01-07 09:07:27stdout[info] ca-toronto.privacy.network

2022-01-07 09:07:27stdout[info] uk-southampton.privacy.network

2022-01-07 09:07:27stdout[info] denmark-2.privacy.network

2022-01-07 09:07:27stdout[info] morocco.privacy.network

2022-01-07 09:07:27stdout[info] czech.privacy.network

2022-01-07 09:07:27stdout[info] mongolia.privacy.network

2022-01-07 09:07:27stdout[info] in.privacy.network

2022-01-07 09:07:27stdout[info] ee.privacy.network

2022-01-07 09:07:27stdout[info] japan.privacy.network

2022-01-07 09:07:27stdout[info] denmark.privacy.network

2022-01-07 09:07:27stdout[info] rs.privacy.network

2022-01-07 09:07:27stdout[info] ba.privacy.network

2022-01-07 09:07:27stdout[info] de-frankfurt.privacy.network

2022-01-07 09:07:27stdout[info] italy-2.privacy.network

2022-01-07 09:07:27stdout[info] au-sydney.privacy.network

2022-01-07 09:07:27stdout[info] nl-amsterdam.privacy.network

2022-01-07 09:07:27stdout[info] philippines.privacy.network

2022-01-07 09:07:27stdout[info] yerevan.privacy.network

2022-01-07 09:07:27stdout[info] poland.privacy.network

2022-01-07 09:07:27stdout[info] ca-vancouver.privacy.network

2022-01-07 09:07:27stdout[info] spain.privacy.network

2022-01-07 09:07:27stdout[info] gr.privacy.network

2022-01-07 09:07:27stdout[info] sk.privacy.network

2022-01-07 09:07:27stdout[info] sg.privacy.network

2022-01-07 09:07:27stdout[info] vietnam.privacy.network

2022-01-07 09:07:27stdout[info] fi-2.privacy.network

2022-01-07 09:07:27stdout[info] no.privacy.network

2022-01-07 09:07:27stdout[info] tr.privacy.network

2022-01-07 09:07:27stdout[info] lu.privacy.network

2022-01-07 09:07:27stdout[info] china.privacy.network

2022-01-07 09:07:27stdout[info] kazakhstan.privacy.network

2022-01-07 09:07:27stdout[info] srilanka.privacy.network

2022-01-07 09:07:27stdout[info] uk-manchester.privacy.network

2022-01-07 09:07:27stdout[info] man.privacy.network

2022-01-07 09:07:27stdout[info] hungary.privacy.network

2022-01-07 09:07:27stdout[info] sofia.privacy.network

2022-01-07 09:07:27stdout[info] de-berlin.privacy.network

2022-01-07 09:07:27stdout[info] italy.privacy.network

2022-01-07 09:07:27stdout2022-01-07 19:37:27,362 DEBG 'start-script' stdout output:

2022-01-07 09:07:27stdout

2022-01-07 09:07:27stdout[info] uk-2.privacy.network

2022-01-07 09:07:27stdout[info] bahamas.privacy.network

2022-01-07 09:07:27stdout[info] brussels.privacy.network

2022-01-07 09:07:27stdout[info] hk.privacy.network

2022-01-07 09:07:27stdout[info] fi.privacy.network

2022-01-07 09:07:27stdout[info] montenegro.privacy.network

2022-01-07 09:07:27stdout[info] ca-montreal.privacy.network

2022-01-07 09:07:27stdout[info] malta.privacy.network

2022-01-07 09:07:27stdout[info] venezuela.privacy.network

2022-01-07 09:07:27stdout[info] ireland.privacy.network

2022-01-07 09:07:27stdout[info] md.privacy.network

2022-01-07 09:07:27stdout[info] monaco.privacy.network

2022-01-07 09:07:27stdout[info] liechtenstein.privacy.network

2022-01-07 09:07:27stdout[info] cyprus.privacy.network

2022-01-07 09:07:27stdout[info] macau.privacy.network

2022-01-07 09:07:27stdout[info] pt.privacy.network

2022-01-07 09:07:27stdout[info] is.privacy.network

2022-01-07 09:07:27stdout[info] lt.privacy.network

2022-01-07 09:07:27stdout[info] dz.privacy.network

2022-01-07 09:07:27stdout[info] qatar.privacy.network

2022-01-07 09:07:27stdout[info] zagreb.privacy.network

2022-01-07 09:07:27stdout[info] nigeria.privacy.network

2022-01-07 09:07:27stdout[info] za.privacy.network

2022-01-07 09:07:27stdout[info] ca-ontario.privacy.network

2022-01-07 09:07:27stdout[info] sweden-2.privacy.network

2022-01-07 09:07:27stdout[info] ad.privacy.network

2022-01-07 09:07:27stdout[info] ua.privacy.network

2022-01-07 09:07:27stdout[info] al.privacy.network

2022-01-07 09:07:27stdout[info] austria.privacy.network

2022-01-07 09:07:27stdout[info] france.privacy.network

2022-01-07 09:07:27stdout[info] ar.privacy.network

2022-01-07 09:07:27stdout[info] lv.privacy.network

2022-01-07 09:07:27stdout[info] br.privacy.network

2022-01-07 09:07:27stdout[info] japan-2.privacy.network

2022-01-07 09:07:27stdout2022-01-07 19:37:27,360 DEBG 'start-script' stdout output:

2022-01-07 09:07:27stdout

2022-01-07 09:07:27stdout[info] List of PIA endpoints that support port forwarding:-

2022-01-07 09:07:27stdout2022-01-07 19:37:27,359 DEBG 'start-script' stdout output:

2022-01-07 09:07:27stdout

2022-01-07 09:07:27stdout[info] PIA endpoint 'aus-melbourne.privacy.network' is in the list of endpoints that support port forwarding

2022-01-07 09:07:27stdout2022-01-07 19:37:27,358 DEBG 'start-script' stdout output:

2022-01-07 09:07:26stdout

2022-01-07 09:07:26stdout[info] Checking endpoint 'aus-melbourne.privacy.network' is port forward enabled...

2022-01-07 09:07:26stdout[info] Port forwarding is enabled

2022-01-07 09:07:26stdout2022-01-07 19:37:26,235 DEBG 'start-script' stdout output:

2022-01-07 09:07:26stdout

2022-01-07 09:07:26stdout[info] Script started to assign incoming port

2022-01-07 09:07:26stdout2022-01-07 19:37:26,234 DEBG 'start-script' stdout output:

2022-01-07 09:07:26stdout

2022-01-07 09:07:26stdout[info] Successfully retrieved external IP address 181.214.199.112

2022-01-07 09:07:26stdout2022-01-07 19:37:26,211 DEBG 'start-script' stdout output:

2022-01-07 09:07:25stdout

2022-01-07 09:07:25stdout[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2022-01-07 09:07:25stdout2022-01-07 19:37:25,685 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 Initialization Sequence Completed

2022-01-07 09:07:23stdout2022-01-07 19:37:23,513 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 /root/openvpnup.sh tun0 1500 1553 10.14.112.5 255.255.255.0 init

2022-01-07 09:07:23stdout2022-01-07 19:37:23 net_addr_v4_add: 10.14.112.5/24 dev tun0

2022-01-07 09:07:23stdout2022-01-07 19:37:23,509 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 net_iface_up: set tun0 up

2022-01-07 09:07:23stdout2022-01-07 19:37:23 net_iface_mtu_set: mtu 1500 for tun0

2022-01-07 09:07:23stdout2022-01-07 19:37:23 TUN/TAP device tun0 opened

2022-01-07 09:07:23stdout2022-01-07 19:37:23,509 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 [melbourne414] Peer Connection Initiated with [AF_INET]181.214.199.112:1198

2022-01-07 09:07:23stdout2022-01-07 19:37:23,486 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 UDP link remote: [AF_INET]181.214.199.112:1198

2022-01-07 09:07:23stdout2022-01-07 19:37:23 UDP link local: (not bound)

2022-01-07 09:07:23stdout2022-01-07 19:37:23 TCP/UDP: Preserving recently used remote address: [AF_INET]181.214.199.112:1198

2022-01-07 09:07:23stdout2022-01-07 19:37:23,187 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout-----END X509 CRL-----

2022-01-07 09:07:23stdoutMR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==

2022-01-07 09:07:23stdout5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy

2022-01-07 09:07:23stdoutze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA

2022-01-07 09:07:23stdoutB4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re

2022-01-07 09:07:23stdoutjI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW

2022-01-07 09:07:23stdout9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5

2022-01-07 09:07:23stdoutMCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG

2022-01-07 09:07:23stdoutaW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa

2022-01-07 09:07:23stdoutZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl

2022-01-07 09:07:23stdoutHgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0

2022-01-07 09:07:23stdoutcm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw

2022-01-07 09:07:23stdoutEwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl

2022-01-07 09:07:23stdoutMIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI

2022-01-07 09:07:23stdout2022-01-07 19:37:23 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----

2022-01-07 09:07:23stdout2022-01-07 19:37:23,186 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2022-01-07 09:07:23stdout2022-01-07 19:37:23,185 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 library versions: OpenSSL 1.1.1m  14 Dec 2021, LZO 2.10

2022-01-07 09:07:23stdout2022-01-07 19:37:23 OpenVPN 2.5.5 [git:makepkg/869f194c23ae93c4+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Dec 15 2021

2022-01-07 09:07:23stdout2022-01-07 19:37:23 WARNING: file 'credentials.conf' is group or others accessible

2022-01-07 09:07:23stdout2022-01-07 19:37:23,184 DEBG 'start-script' stdout output:

2022-01-07 09:07:23stdout

2022-01-07 09:07:23stdout2022-01-07 19:37:23 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.

2022-01-07 09:07:23stdout2022-01-07 19:37:23,184 DEBG 'start-script' stdout output:

2022-01-07 09:07:22stdout

2022-01-07 09:07:22stdout[info] Starting OpenVPN (non daemonised)...

2022-01-07 09:07:22stdout2022-01-07 19:37:22,540 DEBG 'start-script' stdout output:

2022-01-07 09:07:22stdout

2022-01-07 09:07:22stdout--------------------

2022-01-07 09:07:22stdout2022-01-07 19:37:22,538 DEBG 'start-script' stdout output:

2022-01-07 09:07:22stdout

2022-01-07 09:07:22stdout-A OUTPUT -o tun0 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -o lo -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -s 172.17.0.0/16 -d 10.0.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -d 181.214.199.122/32 -o eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -d 181.214.199.121/32 -o eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -d 181.214.199.111/32 -o eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -d 181.214.199.101/32 -o eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -d 181.214.199.112/32 -o eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -i tun0 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -i lo -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -s 10.0.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -s 181.214.199.122/32 -i eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -s 181.214.199.121/32 -i eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -s 181.214.199.111/32 -i eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -s 181.214.199.101/32 -i eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -s 181.214.199.112/32 -i eth0 -j ACCEPT

2022-01-07 09:07:22stdout-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

2022-01-07 09:07:22stdout-P OUTPUT DROP

2022-01-07 09:07:22stdout-P FORWARD DROP

2022-01-07 09:07:22stdout-P INPUT DROP

2022-01-07 09:07:22stdout2022-01-07 19:37:22,536 DEBG 'start-script' stdout output:

2022-01-07 09:07:22stdout

2022-01-07 09:07:22stdout--------------------

2022-01-07 09:07:22stdout[info] iptables defined as follows...

2022-01-07 09:07:22stdout2022-01-07 19:37:22,524 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout[info] iptable_mangle support detected, adding fwmark for tables

2022-01-07 09:07:21stdoutx_tables               17138  19 ip6table_filter,xt_ipvs,xt_iprange,xt_mark,xt_recent,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_nat,xt_multiport,iptable_filter,xt_REDIRECT,iptable_mangle,ip6_tables,xt_addrtype

2022-01-07 09:07:21stdoutip_tables              14011  7 iptable_filter,iptable_mangle,iptable_nat

2022-01-07 09:07:21stdoutiptable_mangle          1656  1

2022-01-07 09:07:21stdout2022-01-07 19:37:21,845 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout--------------------

2022-01-07 09:07:21stdoutunreachable default dev lo proto kernel metric 4294967295 error 4294967195 pref medium

2022-01-07 09:07:21stdout2022-01-07 19:37:21,822 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdoutunreachable default dev lo proto kernel metric 4294967295 error 4294967195 pref medium

2022-01-07 09:07:21stdoutbroadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2 

2022-01-07 09:07:21stdoutlocal 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2 

2022-01-07 09:07:21stdoutbroadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.2 

2022-01-07 09:07:21stdoutbroadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 

2022-01-07 09:07:21stdoutlocal 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 

2022-01-07 09:07:21stdoutlocal 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 

2022-01-07 09:07:21stdoutbroadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 

2022-01-07 09:07:21stdout2022-01-07 19:37:21,821 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 

2022-01-07 09:07:21stdout2022-01-07 19:37:21,821 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout10.0.0.0/24 via 172.17.0.1 dev eth0 

2022-01-07 09:07:21stdout2022-01-07 19:37:21,820 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdoutdefault via 172.17.0.1 dev eth0 

2022-01-07 09:07:21stdout2022-01-07 19:37:21,820 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout--------------------

2022-01-07 09:07:21stdout[info] ip route defined as follows...

2022-01-07 09:07:21stdout2022-01-07 19:37:21,809 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout[info] Adding 10.0.0.0/24 as route via docker eth0

2022-01-07 09:07:21stdout2022-01-07 19:37:21,806 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout[info] Docker network defined as    172.17.0.0/16

2022-01-07 09:07:21stdout2022-01-07 19:37:21,797 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout[info] Default route for container is 172.17.0.1

2022-01-07 09:07:21stdout2022-01-07 19:37:21,706 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout[info] Adding 8.8.8.8 to /etc/resolv.conf

2022-01-07 09:07:21stdout2022-01-07 19:37:21,315 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2022-01-07 09:07:21stdout2022-01-07 19:37:21,226 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout2022-01-07 19:37:21,207 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2022-01-07 09:07:21stdout2022-01-07 19:37:21,207 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2022-01-07 09:07:21stdout2022-01-07 19:37:21,207 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2022-01-07 09:07:21stdout

2022-01-07 09:07:21stdout[info] VPN is enabled, beginning configuration of VPN

2022-01-07 09:07:21stdout2022-01-07 19:37:21,207 DEBG 'start-script' stdout output:

2022-01-07 09:07:21stdout2022-01-07 19:37:21,088 INFO reaped unknown pid 9 (exit status 0)

2022-01-07 09:07:21stdout2022-01-07 19:37:21,087 INFO spawned: 'watchdog-script' with pid 184

2022-01-07 09:07:21stdout2022-01-07 19:37:21,084 INFO spawned: 'start-script' with pid 183

2022-01-07 09:07:21stdout2022-01-07 19:37:21,081 INFO spawned: 'shutdown-script' with pid 182

2022-01-07 09:07:20stdout2022-01-07 19:37:20,078 INFO supervisord started with pid 8

2022-01-07 09:07:19stdout2022-01-07 19:37:19,993 INFO Set uid to user 0 succeeded

2022-01-07 09:07:19stdout2022-01-07 19:37:19,992 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2022-01-07 09:07:12stdout2022-01-07 19:37:12.786625 [info] Starting Supervisor...

2022-01-07 09:07:12stdout2022-01-07 19:37:12.712096 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'

2022-01-07 09:07:12stdout2022-01-07 19:37:12.640856 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'

2022-01-07 09:07:12stdout2022-01-07 19:37:12.568546 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports

2022-01-07 09:07:12stdout2022-01-07 19:37:12.497964 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports

2022-01-07 09:07:12stdout2022-01-07 19:37:12.420729 [info] ENABLE_PRIVOXY defined as 'no'

2022-01-07 09:07:12stdout2022-01-07 19:37:12.343575 [info] STRICT_PORT_FORWARD defined as 'yes'

2022-01-07 09:07:12stdout2022-01-07 19:37:12.270404 [info] VPN_PASS defined as '**************************'

2022-01-07 09:07:12stdout2022-01-07 19:37:12.199321 [info] VPN_USER defined as '************'

2022-01-07 09:07:12stdout2022-01-07 19:37:12.129842 [info] NAME_SERVERS defined as '8.8.8.8'

2022-01-07 09:07:12stdout2022-01-07 19:37:12.061810 [info] LAN_NETWORK defined as '10.0.0.0/24'

2022-01-07 09:07:11stdout2022-01-07 19:37:11.990958 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)

2022-01-07 09:07:11stdout2022-01-07 19:37:11.920997 [info] VPN_DEVICE_TYPE defined as 'tun0'

2022-01-07 09:07:11stdout2022-01-07 19:37:11.849612 [info] VPN remote protcol(s) defined as 'udp,'

2022-01-07 09:07:11stdout2022-01-07 19:37:11.783209 [info] VPN remote port(s) defined as '1198,'

2022-01-07 09:07:11stdout2022-01-07 19:37:11.721821 [info] VPN remote server(s) defined as 'aus-melbourne.privacy.network,'

2022-01-07 09:07:11stdout2022-01-07 19:37:11.501854 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/au_melbourne.ovpn

2022-01-07 09:07:07stdout2022-01-07 19:37:07.663800 [info] VPN_PROV defined as 'pia'

2022-01-07 09:07:07stdout2022-01-07 19:37:07.597353 [info] VPN_CLIENT defined as 'openvpn'

2022-01-07 09:07:07stdout2022-01-07 19:37:07.523843 [info] VPN_ENABLED defined as 'yes'

2022-01-07 09:07:07stdout2022-01-07 19:37:07.286779 [info] Deleting files in /tmp (non recursive)...

2022-01-07 09:07:06stdout2022-01-07 19:37:06.981193 [info] Permissions already set for '/config'

2022-01-07 09:07:06stdout2022-01-07 19:37:06.901860 [info] UMASK defined as '000'

2022-01-07 09:07:06stdout2022-01-07 19:37:06.483703 [info] PGID defined as '100'

2022-01-07 09:07:06stdout2022-01-07 19:37:06.151680 [info] PUID defined as '1026'

2022-01-07 09:07:05stdout2022-01-07 19:37:05.996605 [info] OS_ARCH defined as 'x86-64'

2022-01-07 09:07:05stdout2022-01-07 19:37:05.923509 [info] System information Linux Deluge-with-VPN 4.4.180+ #42218 SMP Mon Oct 18 19:17:56 CST 2021 x86_64 GNU/Linux

2022-01-07 09:07:05stdout

2022-01-07 09:07:05stdout   https://hub.docker.com/u/binhex/

2022-01-07 09:07:05stdout     \/        \/     \/     \/      \/

2022-01-07 09:07:05stdout |___  /__|___|  /___|  /\___  >__/\_ \

2022-01-07 09:07:05stdout | \_\ \  |   |  \   Y  \  ___/ >    <

2022-01-07 09:07:05stdout | __ \|  |/    \|  |  \_/ __ \\  \/  /

2022-01-07 09:07:05stdout\_ |__ |__| ____ |  |__   ____ ___  ___

2022-01-07 09:07:05stdout___.   .__       .__

2022-01-07 09:07:05stdoutCreated by...

Link to comment

I can't seem to access WebUI while using wireguard. Any help would be appreciated

It is fully active and can see network traffic on eth0.

 

2022-01-08 23:30:19.761351 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2022-01-08 23:30:19.778837 [info] Starting Supervisor...
2022-01-08 23:30:21,036 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2022-01-08 23:30:21,036 INFO Set uid to user 0 succeeded
2022-01-08 23:30:21,038 INFO supervisord started with pid 7
2022-01-08 23:30:22,040 INFO spawned: 'shutdown-script' with pid 168
2022-01-08 23:30:22,041 INFO spawned: 'start-script' with pid 169
2022-01-08 23:30:22,041 INFO spawned: 'watchdog-script' with pid 170
2022-01-08 23:30:22,041 INFO reaped unknown pid 8 (exit status 0)
2022-01-08 23:30:22,055 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2022-01-08 23:30:22,055 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-08 23:30:22,055 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-08 23:30:22,055 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-01-08 23:30:22,057 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2022-01-08 23:30:22,059 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2022-01-08 23:30:22,060 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2022-01-08 23:30:22,062 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2022-01-08 23:30:22,064 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2022-01-08 23:30:22,066 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2022-01-08 23:30:22,883 DEBG 'start-script' stdout output:
[info] Token generated for PIA wireguard authentication

2022-01-08 23:30:22,903 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'...

2022-01-08 23:30:23,132 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2022-01-08 23:30:23,145 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2022-01-08 23:30:23,147 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2022-01-08 23:30:23,148 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

2022-01-08 23:30:23,148 DEBG 'start-script' stdout output:
[info] ip route defined as follows...

2022-01-08 23:30:23,148 DEBG 'start-script' stdout output:
--------------------

2022-01-08 23:30:23,148 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
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.2
local 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2

2022-01-08 23:30:23,148 DEBG 'start-script' stdout output:
--------------------

2022-01-08 23:30:23,150 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 28672 6 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables 28672 17 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2022-01-08 23:30:23,150 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2022-01-08 23:30:23,242 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2022-01-08 23:30:23,243 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 181.214.206.122/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.92/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.111/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.112/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.101/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.0.0/24 -d 172.17.0.0/16 -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 -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 wg0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 181.214.206.122/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.92/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.111/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.112/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.101/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.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 -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 wg0 -j ACCEPT

2022-01-08 23:30:23,243 DEBG 'start-script' stdout output:
--------------------

2022-01-08 23:30:23,245 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2022-01-08 23:30:23,289 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-01-08 23:30:23,292 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-01-08 23:30:23,293 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-01-08 23:30:23,301 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.34.182.158 dev wg0

2022-01-08 23:30:23,304 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2022-01-08 23:30:23,329 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2022-01-08 23:30:23,329 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2022-01-08 23:30:23,330 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2022-01-08 23:30:23,330 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2022-01-08 23:30:23,332 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2022-01-08 23:30:23,343 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2022-01-08 23:30:23,345 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2022-01-08 23:30:24,452 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2022-01-08 23:30:24,579 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 181.214.206.122

2022-01-08 23:30:24,580 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2022-01-08 23:30:24,583 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2022-01-08 23:30:24,583 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'nl-amsterdam.privacy.network' is port forward enabled...

2022-01-08 23:30:25,360 DEBG 'start-script' stdout output:
[info] PIA endpoint 'nl-amsterdam.privacy.network' is in the list of endpoints that support port forwarding

2022-01-08 23:30:25,360 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2022-01-08 23:30:25,360 DEBG 'start-script' stdout output:
[info] ad.privacy.network
[info] qatar.privacy.network
[info] tr.privacy.network

2022-01-08 23:30:25,360 DEBG 'start-script' stdout output:
[info] lv.privacy.network
[info] dz.privacy.network
[info] uk-manchester.privacy.network
[info] sweden.privacy.network
[info] taiwan.privacy.network
[info] swiss.privacy.network
[info] philippines.privacy.network
[info] nigeria.privacy.network
[info] hungary.privacy.network
[info] man.privacy.network
[info] fi.privacy.network
[info] greenland.privacy.network
[info] ca-montreal.privacy.network
[info] denmark.privacy.network
[info] lt.privacy.network
[info] monaco.privacy.network
[info] italy.privacy.network
[info] china.privacy.network
[info] nl-amsterdam.privacy.network
[info] japan-2.privacy.network
[info] spain.privacy.network
[info] sweden-2.privacy.network
[info] aus-melbourne.privacy.network
[info] france.privacy.network
[info] ca-ontario.privacy.network

2022-01-08 23:30:25,360 DEBG 'start-script' stdout output:
[info] saudiarabia.privacy.network
[info] malta.privacy.network
[info] mk.privacy.network
[info] br.privacy.network
[info] kazakhstan.privacy.network
[info] aus-perth.privacy.network
[info] in.privacy.network
[info] bahamas.privacy.network
[info] md.privacy.network
[info] austria.privacy.network
[info] ba.privacy.network
[info] hk.privacy.network
[info] liechtenstein.privacy.network
[info] zagreb.privacy.network
[info] japan.privacy.network
[info] de-frankfurt.privacy.network
[info] lu.privacy.network
[info] sk.privacy.network
[info] sofia.privacy.network
[info] israel.privacy.network
[info] yerevan.privacy.network
[info] de-berlin.privacy.network
[info] nz.privacy.network
[info] panama.privacy.network
[info] fi-2.privacy.network
[info] ar.privacy.network
[info] egypt.privacy.network
[info] vietnam.privacy.network
[info] cambodia.privacy.network
[info] au-sydney.privacy.network

2022-01-08 23:30:25,360 DEBG 'start-script' stdout output:
[info] cyprus.privacy.network
[info] gr.privacy.network
[info] mexico.privacy.network
[info] brussels.privacy.network
[info] denmark-2.privacy.network
[info] venezuela.privacy.network
[info] ae.privacy.network
[info] ca-vancouver.privacy.network
[info] srilanka.privacy.network
[info] montenegro.privacy.network
[info] uk-london.privacy.network
[info] uk-2.privacy.network
[info] sg.privacy.network
[info] czech.privacy.network
[info] rs.privacy.network
[info] pt.privacy.network
[info] macau.privacy.network
[info] ca-toronto.privacy.network
[info] georgia.privacy.network
[info] uk-southampton.privacy.network
[info] poland.privacy.network
[info] morocco.privacy.network
[info] ro.privacy.network
[info] is.privacy.network

2022-01-08 23:30:25,360 DEBG 'start-script' stdout output:
[info] italy-2.privacy.network
[info] mongolia.privacy.network
[info] no.privacy.network
[info] ireland.privacy.network
[info] ua.privacy.network
[info] za.privacy.network
[info] al.privacy.network
[info] ee.privacy.network
[info] bangladesh.privacy.network

2022-01-08 23:30:27,732 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34448'

2022-01-08 23:30:28,450 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.34.182.158 different, marking for reconfigure

2022-01-08 23:30:28,519 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-01-08 23:30:28,521 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2022-01-08 23:30:28,523 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2022-01-08 23:30:28,524 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 34448 different, marking for reconfigure

2022-01-08 23:30:28,530 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-01-08 23:30:29,176 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.3.112.8'
[info] Deluge key 'listen_interface' will have a new value '10.34.182.158'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-01-08 23:30:29,459 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 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-01-08 23:30:29,576 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '2839844df5404444b8d5678f6834c5dc'
[info] Deluge key 'default_daemon' will have a new value '2839844df5404444b8d5678f6834c5dc'
[info] Writing changes to Deluge config file '/config/web.conf'...

2022-01-08 23:30:29,923 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-01-08 23:30:30,139 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-01-08 23:30:31,904 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2022-01-08 23:30:33,704 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (34448, 34448)
Configuration value successfully updated.

2022-01-08 23:30:35,540 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-01-08 23:30:35,541 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-01-08 23:30:35,541 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2022-01-08 23:30:35,541 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2022-01-08 23:30:36,599 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-01-08 23:30:36,601 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

Link to comment

Since yesterday my deluge stopped working. im running version 1.3.15_18.

i also tried deleting docker and reinstalling, same issue.

 

i also downloaded a current version of delugevpn and still gave me the same error. i made zero changes to unraid or dockers. 
 

 

 

the following error from logs:

022-01-08 15:24:27,329 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...

2022-01-08 15:24:27,332 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/5.10.21-Unraid

2022-01-08 15:24:27,332 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2022-01-08 15:24:27,334 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

 

* i followed the steps from the docker vpn faq:

 

SSH into the unRAID host and issue the following commands:-

echo "# force iptable mangle module to load (required for *vpn dockers)" >> /boot/config/go

echo "/sbin/modprobe iptable_mangle" >> /boot/config/go

 

Reboot the host for the change to take effect

 

Note - If you want to apply the fix straight away issue the following:-

/sbin/modprobe iptable_mangle

 

 

any ideas?

Link to comment
On 9/1/2021 at 10:02 PM, xgroleau said:

  

Hi,

I am getting some issue with deluge lately, it seems there is some recursive routing, but I am only using the VPN for deluge and a torrent indexer. I am using CyberGhost VPN with OpenVPN. I can still download torrent, though it spams the log file and the VPN seem to drop and restart every couple minutes and also torrent goes sometime in error. Has anyone encountered a similar issue?

Here are the logs when it seems to restart:
 

2021-09-01 15:41:20,270 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2021-09-01 15:41:20,741 DEBG 'start-script' stdout output:
2021-09-01 15:41:20 us=739881 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:20,093 DEBG 'start-script' stdout output:
2021-09-01 15:41:20 us=93338 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443
2021-09-01 15:41:20 us=93371 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443
2021-09-01 15:41:20 us=93386 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443
2021-09-01 15:41:20 us=93459 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:20,094 DEBG 'start-script' stdout output:
2021-09-01 15:41:20 us=94796 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:20,095 DEBG 'start-script' stdout output:
2021-09-01 15:41:20 us=94945 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443
2021-09-01 15:41:20 us=94956 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443
2021-09-01 15:41:20 us=94965 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443
2021-09-01 15:41:20 us=94974 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443
2021-09-01 15:41:20 us=95128 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:20,270 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2021-09-01 15:41:20,741 DEBG 'start-script' stdout output:
2021-09-01 15:41:20 us=739881 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:24,403 DEBG 'start-script' stdout output:
2021-09-01 15:41:24 us=403033 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:25,404 DEBG 'start-script' stdout output:
2021-09-01 15:41:25 us=403897 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:25,419 DEBG 'start-script' stdout output:
2021-09-01 15:41:25 us=418975 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

2021-09-01 15:41:25,404 DEBG 'start-script' stdout output:
2021-09-01 15:41:25 us=403897 Recursive routing detected, drop tun packet to [AF_INET]193.176.85.96:443

 

Did you ever figure this out? Having the same problem, and have had it for a while now - tried changing my OVPN file to a different endpoint, didn't change anything - figure it's the torrent client trying to contact itself through the VPN, which OpenVPN doesn't like (for obvious reasons). 

Link to comment

My VPN is failing to connect within 60 seconds and I receive the following error:

TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

When I test the VPN connection on my Windows laptop using the VPN provider's OpenVPN client - it takes nearly 90 seconds to create the connection

OpenVPN.Control - INFO - Connection built in 80.815 sec.

 

Is there any way I can extend the timeout to say 120 seconds?

Link to comment
49 minutes ago, Mokad said:

QBittorrentVPN was working a month or so ago. Came back a couple days ago and i can't access the WebUI anymore while VPN enabled is set to yes. Also switched to DelugeVPN now. Using this with NordVPN. Attatched supervisord below. Thanks for anyhelp you can give.

supervisord.log 15.62 kB · 1 download

You have posted your user name and password. You should contact NordVPN and change them.

 

Also, I don’t think you have your LAN Network set correctly.

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

Scroll down to Q4.

Edited by wgstarks
Link to comment

First: @binhex, thanks for all the work you put into your dockers and the support you offer on this forum.

 

Forum users, looking for help with a VPN issue I'm having. 

 

I had delugevpn setup and working for months with my VPN provider (Mullvad) using openvpn.  It's been working great up until now.  But since a recent server shutdown, I can't get the VPN tunnel to work in the docker + I can't access the deluge gui.   I'm at a loss to what the issue is.  What I've done so far (with no success):

  1. When I set the Container Variable: VPN_ENABLED to NO, I can then access the GUI on port 8112. 
  2. Downloaded and implemented a new config file for openvpn from Mullvad
  3. I've confirmed the openvpn config file by using the exact same config file in my openvpn client on my PC.  So I know the file is structured correctly.  As well, my PC and Unraid server are on the same network segment, and have the same firewall rules applied to both.
  4. Tried using Mullvad VPN servers in another region
  5. Pulled an older version of the docker to see if openvpn 2.5.5 client was the issue.  (binhex/arch-delugevpn:2.0.4-2-01)
  6. Running ifconfig from inside the docker, I don't see tun0 up (which I think is the correct interface for the VPN tunnel)
  7. I've completely wiped the docker, cleaned up the files in appdata and pulled the full delugevpn again. 
  8. I've stopped and restarted docker services on my unraid server. 
  9. I've looked over the supervisord.log so many times, I don't see any errors or anything that could explain why the tunnel isn't coming up (See the attached supervisord.log file)

What am I missing / what else can I look at to see why this isn't working? 

 

supervisord.log

Link to comment
1 hour ago, Xoron said:

First: @binhex, thanks for all the work you put into your dockers and the support you offer on this forum.

 

Forum users, looking for help with a VPN issue I'm having. 

 

I had delugevpn setup and working for months with my VPN provider (Mullvad) using openvpn.  It's been working great up until now.  But since a recent server shutdown, I can't get the VPN tunnel to work in the docker + I can't access the deluge gui.   I'm at a loss to what the issue is.  What I've done so far (with no success):

  1. When I set the Container Variable: VPN_ENABLED to NO, I can then access the GUI on port 8112. 
  2. Downloaded and implemented a new config file for openvpn from Mullvad
  3. I've confirmed the openvpn config file by using the exact same config file in my openvpn client on my PC.  So I know the file is structured correctly.  As well, my PC and Unraid server are on the same network segment, and have the same firewall rules applied to both.
  4. Tried using Mullvad VPN servers in another region
  5. Pulled an older version of the docker to see if openvpn 2.5.5 client was the issue.  (binhex/arch-delugevpn:2.0.4-2-01)
  6. Running ifconfig from inside the docker, I don't see tun0 up (which I think is the correct interface for the VPN tunnel)
  7. I've completely wiped the docker, cleaned up the files in appdata and pulled the full delugevpn again. 
  8. I've stopped and restarted docker services on my unraid server. 
  9. I've looked over the supervisord.log so many times, I don't see any errors or anything that could explain why the tunnel isn't coming up (See the attached supervisord.log file)

What am I missing / what else can I look at to see why this isn't working? 

 

supervisord.log 11.57 kB · 1 download

Same for me. Hoping for a solution to this awesome solution!

Link to comment
7 hours ago, Xoron said:

First: @binhex, thanks for all the work you put into your dockers and the support you offer on this forum.

 

Forum users, looking for help with a VPN issue I'm having. 

 

I had delugevpn setup and working for months with my VPN provider (Mullvad) using openvpn.  It's been working great up until now.  But since a recent server shutdown, I can't get the VPN tunnel to work in the docker + I can't access the deluge gui.   I'm at a loss to what the issue is.  What I've done so far (with no success):

  1. When I set the Container Variable: VPN_ENABLED to NO, I can then access the GUI on port 8112. 
  2. Downloaded and implemented a new config file for openvpn from Mullvad
  3. I've confirmed the openvpn config file by using the exact same config file in my openvpn client on my PC.  So I know the file is structured correctly.  As well, my PC and Unraid server are on the same network segment, and have the same firewall rules applied to both.
  4. Tried using Mullvad VPN servers in another region
  5. Pulled an older version of the docker to see if openvpn 2.5.5 client was the issue.  (binhex/arch-delugevpn:2.0.4-2-01)
  6. Running ifconfig from inside the docker, I don't see tun0 up (which I think is the correct interface for the VPN tunnel)
  7. I've completely wiped the docker, cleaned up the files in appdata and pulled the full delugevpn again. 
  8. I've stopped and restarted docker services on my unraid server. 
  9. I've looked over the supervisord.log so many times, I don't see any errors or anything that could explain why the tunnel isn't coming up (See the attached supervisord.log file)

What am I missing / what else can I look at to see why this isn't working? 

 

supervisord.log 11.57 kB · 2 downloads

that ovpn file from mullvad looks wrong, its using a whacky port for a start (port 1300 - standard is 1194) which leads me to think this config is not correct, can you please reverify that you are downloading the correct openvpn configuration file from mullvad, looking at your logs it is unable to contact any of the endpoints specified in the ovpn file, from your log:-

 

2022-01-11 21:22:57,804 DEBG 'start-script' stdout output:
2022-01-11 21:22:57 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
2022-01-11 21:22:57 UDP link local: (not bound)
2022-01-11 21:22:57 UDP link remote: [AF_INET]89.36.78.34:1300

2022-01-11 21:23:57,039 DEBG 'start-script' stdout output:
2022-01-11 21:23:57 [UNDEF] Inactivity timeout (--ping-restart), restarting

this is simply stating it cannot connect to remote 89.36.78.34 on port 1300, so as stated above its either an incorrect ovpn file or your firewall is blocking outbound port 1300 (check this!).

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.