[Support] binhex - DelugeVPN

[humble-relocation2501]

9 hours ago, humble-relocation2501 said:

still showing the private ip on the web ui, but run the command that you suggested inside the container and it shows the vpn ip.

Also checked https://iknowwhatyoudownload.com with vpn ip shows stuff I downloaded and it doesn't show anything with my ip.

So I'm 100% confident that there has not been an ip leak.

Thanks for your help!

I will post in deluge forum and will let you know about what they say.

so here is the answer from deluge dev team

https://forum.deluge-torrent.org/viewtopic.php?t=56613

[binhex]

40 minutes ago, humble-relocation2501 said:

so here is the answer from deluge dev team

https://forum.deluge-torrent.org/viewtopic.php?t=56613

A quote from the reply:-
 

Quote

Anyway, hope helps with binding to interface name instead.

Already done, it is bound to the vpn interface, and we also specify the vpn adapters ip for incoming, so yeah not much else i can do here unless im missing a setting in the ui.

 

from my previous post:-
 

Quote

detail that you have the vpn provider adapter bound in deluge for 'outgoing interface' and the ip address of the vpn adapter defined for 'incoming address' yet the external ip address shown is your isp ip address and see what they say.

i see you included this in your post, ok he does go on about setting the incoming adapter but there is no way to do that, you can only set the incoming address, and if you try and force this by editing the core.conf it simply errors, so i dont know how to achieve this, it must be some hackery of libtorrent probably via itconfig i assume.

[Corneloues]

On 10/31/2023 at 2:13 PM, binhex said:

 I think what you are trying to achieve is covered in Q24:-https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Yes, and this is what I have configured. But one of my containers needs a port open to the outside world.

 

So I'm trying to use a PIA port to do that.

 

Can that be done?

[binhex]

13 minutes ago, Corneloues said:

 

Yes, and this is what I have configured. But one of my containers needs a port open to the outside world.

 

So I'm trying to use a PIA port to do that.

 

Can that be done?

The PIA incoming port is dynamic so every time you restart the container or the vpn drops and re-establishes you may have a new port number, what is it you are trying to achieve?, access a web ui of a container externally?

[Corneloues]

9 hours ago, binhex said:

what is it you are trying to achieve?, access a web ui of a container externally?

 

Run a Soulseek client over the VPN

[binhex]

10 hours ago, Corneloues said:

 

Run a Soulseek client over the VPN

I see, so you do need a working incoming port, that is going to be tricky, as i mentioned the port is dynamic for pia (other vpn providers permit static incoming port), so even if you find out what the port is you would then need a programmatic way of configuring soulseek to use it, otherwise you would need to manually reconfigure soulseek each time the port changes.

so is it possible?, yes but its going to require some work on your part to configure soulseek.

[Corneloues]

8 hours ago, binhex said:

so is it possible?, yes but its going to require some work on your part to configure soulseek.

 

Ah bugger...

 

My skills don't stretch that far yet...

 

Maybe easier to use a different VPN client.

[MarianKoniuszko]

Hello, after last update my deluge-vpn keep loosing Labels plugin. Every restart container I don't have that plugin and my Radarr/Sonarr cannot import.
Regards.

[binhex]

35 minutes ago, MarianKoniuszko said:

Hello, after last update my deluge-vpn keep loosing Labels plugin. Every restart container I don't have that plugin and my Radarr/Sonarr cannot import.
Regards.

try Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/delugevpn.md

[MarianKoniuszko]

1 hour ago, binhex said:

try Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/delugevpn.md

Why that issue is only on Deluge-vpn? Not on regular Deluge container.

[binhex]

Why that issue is only on Deluge-vpn? Not on regular Deluge container.

It's for both

Sent from my 22021211RG using Tapatalk

[MarianKoniuszko]

2 minutes ago, binhex said:

It's for both

Sent from my 22021211RG using Tapatalk
 

But Deluge works ok after rebuild container.

Only deluge-vpn failed to load labels plugin.

[dReDone]

I've had DelugeVPN with NordVPN on Unraid running fine for quite some time but since I changed residence (and internet provider) it hasn't been working. When on VPN I cannot connect to Deluge and the browser request times out. Without VPN on it works fine. Looking through this thread I've seen quite a few solutions.

The main issue I've seen which is pinned to the top of this thread is people are using e-mail/password in credentials.conf but I've never used these and always used the user name/password credentials from the suggested solution from my NordVPN Manual setup page.

 

I saw another person who had some weird IP/Subnet settings but that didn't seem to fix anything either. My old subnet was 10.0.0.0/24 and the new router has a subnet of 192.168.4.0/22. My internal IP is 192.168.4.5 for my deluge and 192.168.4.21. I don't think there is any problem there but I'm not the greatest at understanding subnet issues.

 

Hopefully someone can help because I keep seeing super similar issues but it ends up not being the issue! Attached the log that is usually requested.

supervisord.log

[binhex]

25 minutes ago, dReDone said:

I've had DelugeVPN with NordVPN on Unraid running fine for quite some time but since I changed residence (and internet provider) it hasn't been working. When on VPN I cannot connect to Deluge and the browser request times out. Without VPN on it works fine. Looking through this thread I've seen quite a few solutions.

The main issue I've seen which is pinned to the top of this thread is people are using e-mail/password in credentials.conf but I've never used these and always used the user name/password credentials from the suggested solution from my NordVPN Manual setup page.

 

I saw another person who had some weird IP/Subnet settings but that didn't seem to fix anything either. My old subnet was 10.0.0.0/24 and the new router has a subnet of 192.168.4.0/22. My internal IP is 192.168.4.5 for my deluge and 192.168.4.21. I don't think there is any problem there but I'm not the greatest at understanding subnet issues.

 

Hopefully someone can help because I keep seeing super similar issues but it ends up not being the issue! Attached the log that is usually requested.

supervisord.log 40.75 kB · 0 downloads

that's a successful start but i see you have overlapping networks defined, from your log:-
 

LAN_NETWORK defined as '192.168.4.0/22, 192.168.4.0/24'

change this to be:-
 

LAN_NETWORK defined as '192.168.4.0/22'

 

[dReDone]

1 minute ago, binhex said:

that's a successful start but i see you have overlapping networks defined, from your log:-
 

LAN_NETWORK defined as '192.168.4.0/22, 192.168.4.0/24'

change this to be:-
 

LAN_NETWORK defined as '192.168.4.0/22'

 

 

Sorry didn't realize I hadn't changed it back. Originally it was set to 192.168.4.0/22.

I reset LAN_NETWORK and here's a fresh supervisord.log

supervisord.log

[binhex]

19 minutes ago, dReDone said:

 

Sorry didn't realize I hadn't changed it back. Originally it was set to 192.168.4.0/22.

I reset LAN_NETWORK and here's a fresh supervisord.log

supervisord.log 45.62 kB · 0 downloads

OK i see your issue, you have given the container a set ip address, this then causes a clash as the docker network and the lan are then the same, from your log:-
 

2023-11-08 06:32:02,593 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 192.168.4.5

2023-11-08 06:32:02,599 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.252.0

2023-11-08 06:32:02,935 DEBG 'start-script' stdout output:
[info] Docker network defined as    192.168.4.0/22

the fix is either to setup another docker network separate to your lan and use that, or simply switch it back to 'bridge'.

[dReDone]

57 minutes ago, binhex said:

OK i see your issue, you have given the container a set ip address, this then causes a clash as the docker network and the lan are then the same, from your log:-
 

2023-11-08 06:32:02,593 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 192.168.4.5

2023-11-08 06:32:02,599 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.252.0

2023-11-08 06:32:02,935 DEBG 'start-script' stdout output:
[info] Docker network defined as    192.168.4.0/22

the fix is either to setup another docker network separate to your lan and use that, or simply switch it back to 'bridge'.

This worked! Thanks so much for your help, you do fantastic work! I had it set up with a Static IP on my last network, curious why it was okay then. Either way it's going now! Thanks again.

[MarianKoniuszko]

Hello @binhex I one more time need Your help
I've got problems with my drive and all docker apps and plugins were gone. Now I reinstall all of them from Previous apps but only deluge-vpn refuse to pull:
 

Pulling image: binhex/arch-delugevpn:latest
IMAGE ID [2091926825]: Pulling from binhex/arch-delugevpn.

TOTAL DATA PULLED: 0 B

Error: Get "https://registry-1.docker.io/v2/binhex/arch-delugevpn/manifests/sha256:d23477a27d878cfaa2572ff771b45921bf0786ba4eefff5f3aab340948535a85": EOF

EDIT. 
OK, It pull now and everything is working.
Regards.

[Sinister]

Good Afternoon

I am trying to route my Jackett through delugevpn whith sonarr and radarr im aware you need to change the ip address from 192 to instead localhost. I am a bit confused as to what you would enter to in the URL to get jackett to communicate with sonarr and radarr.

 

 

 

Edited November 19, 2023 by Sinister
Solved most of my own issues

[expo]

You all are my last hope in getting UNRAID to work. I am simply trying to route my containers through my binhex-delugevpn, I have followed every single tutorial. And they all basically say to do these steps:

• Install binhex-delugevpn
• I curl ipconfig.io and i get the VPN IP
• Install next app, for this example binhex-sonarr
• everything works fine
• setup, curl ipconfig.io get my local ip
• change network to none, in Extra Parameters add --net=contianer:binhex-delugevpn
• launched sonarr
• curl ipconfig get VPN
• add port 8989 to deluge
• Can't get the port to resolve, can't get to the UI

Folks say that you don't need to run it behind a VPN, I do. Either way, I will want to do the same with other apps such as a web browser. I have done this dozens of time with every VPN app I could find. I am using PIA in wireguard mode.

What am I missing? What do i need to post to get some help? Someone has said my docker config file but I don't know what that is.

 

Run Command:

docker run
  -d
  --name='binhex-sonarr'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="UNRAID"
  -e HOST_CONTAINERNAME="binhex-sonarr"
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8989]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sonarr-icon.png'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user':'/media':'rw'
  -v '/mnt/user/appdata/binhex-sonarr':'/config':'rw'
  --net=container:binhex-delugevpn 'binhex/arch-sonarr'

b02f8de0affc8531d17b7c8da1272543ea24bbf1b200cafe3f20085dc012206b

The command finished successfully!

 

 

deluge vpn run command

docker run
  -d
  --name='binhex-delugevpn'
  --net='bridge'
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="UNRAID"
  -e HOST_CONTAINERNAME="binhex-delugevpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='redacted'
  -e 'VPN_PASS'='redacted'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='yes'
  -e 'LAN_NETWORK'='192.168.15.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'DELUGE_DAEMON_LOG_LEVEL'='info'
  -e 'DELUGE_WEB_LOG_LEVEL'='info'
  -e 'DELUGE_ENABLE_WEBUI_PASSWORD'='yes'
  -e 'VPN_INPUT_PORTS'='7878, 8989'
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://192.168.15.187:8112'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/deluge-icon.png'
  -p '8112:8112/tcp'
  -p '58846:58846/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -p '8118:8118/tcp'
  -p '3000:3000/tcp'
  -p '8989:8989/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn'

d19d66fb12244273d2c318ed59e0dc319df9be509552f5a0b0b612945d767883

The command finished successfully!

added my diagnostic file

 

unraid-diagnostics-20231124-1730.zip

Edited November 24, 2023 by expo

[Sinister]

1 hour ago, expo said:

You all are my last hope in getting UNRAID to work. I am simply trying to route my containers through my binhex-delugevpn, I have followed every single tutorial. And they all basically say to do these steps:

• Install binhex-delugevpn
• I curl ipconfig.io and i get the VPN IP
• Install next app, for this example binhex-sonarr
• everything works fine
• setup, curl ipconfig.io get my local ip
• change network to none, in Extra Parameters add --net=contianer:binhex-delugevpn
• launched sonarr
• curl ipconfig get VPN
• add port 8989 to deluge
• Can't get the port to resolve, can't get to the UI

Folks say that you don't need to run it behind a VPN, I do. Either way, I will want to do the same with other apps such as a web browser. I have done this dozens of time with every VPN app I could find. I am using PIA in wireguard mode.

What am I missing? What do i need to post to get some help? Someone has said my docker config file but I don't know what that is.

 

Run Command:

docker run
  -d
  --name='binhex-sonarr'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="UNRAID"
  -e HOST_CONTAINERNAME="binhex-sonarr"
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8989]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sonarr-icon.png'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user':'/media':'rw'
  -v '/mnt/user/appdata/binhex-sonarr':'/config':'rw'
  --net=container:binhex-delugevpn 'binhex/arch-sonarr'

b02f8de0affc8531d17b7c8da1272543ea24bbf1b200cafe3f20085dc012206b

The command finished successfully!

 

 

deluge vpn run command

docker run
  -d
  --name='binhex-delugevpn'
  --net='bridge'
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="UNRAID"
  -e HOST_CONTAINERNAME="binhex-delugevpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='redacted'
  -e 'VPN_PASS'='redacted'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='yes'
  -e 'LAN_NETWORK'='192.168.15.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'DELUGE_DAEMON_LOG_LEVEL'='info'
  -e 'DELUGE_WEB_LOG_LEVEL'='info'
  -e 'DELUGE_ENABLE_WEBUI_PASSWORD'='yes'
  -e 'VPN_INPUT_PORTS'='7878, 8989'
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://192.168.15.187:8112'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/deluge-icon.png'
  -p '8112:8112/tcp'
  -p '58846:58846/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -p '8118:8118/tcp'
  -p '3000:3000/tcp'
  -p '8989:8989/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn'

d19d66fb12244273d2c318ed59e0dc319df9be509552f5a0b0b612945d767883

The command finished successfully!

added my diagnostic file

 

unraid-diagnostics-20231124-1730.zip 86.49 kB · 0 downloads

Lets see if i can help you from going crazy like i did, does your deluge container have a slot for vpn input ports and output ports ? if not those are pretty important, i ended up uninstalling and re-downloading the template pointing it at my existing deluge appdata folder and all was well. in the input and output ports you need to put in the ports of the containers you want to passthrough 8989.7878 seperated by comma for more than one containers.

 

When adding the port to deluge if you add 8989 as a container port like the guide says you need to make the host port something like 9000, also you wont be able to launch the UI by clicking on the container you weill need to go to the containers ip address and enter the host port you entered into deluge.

 

So for sonar instead of 192,168.1.114:8989 it would be 192.168.1.114:9000

[expo]

 

edit: I started fresh again, used the tutorial with Gluetun and got it to work. No idea what I was doing wrong other than maybe selecting openvpn vs wireguard. but I got it working. thanks for your help.

 

16 hours ago, Sinister said:

Lets see if i can help you from going crazy like i did, does your deluge container have a slot for vpn input ports and output ports ? if not those are pretty important, i ended up uninstalling and re-downloading the template pointing it at my existing deluge appdata folder and all was well. in the input and output ports you need to put in the ports of the containers you want to passthrough 8989.7878 seperated by comma for more than one containers.

 

 

 

Edited November 25, 2023 by expo
got it working

[arlovelo]

I've come across an issue after moving my media server to a new host along with all my docker images. My deluge download speed is a lot slower than it should be on the new host and I can't figure out why. As an example, I downloaded the same file on both hosts at same time and averaged 7.5-8MiB/s on old host and 1.5-2MiB/s on new. (My internet connection is 500Mbps fibre and I usually max out at 30MiB/s on downloads on old host).

 

I've used the same docker-compose file in portainer so I know I have the same set up. The wg0.conf file is set with the same PIA endpoint and the file permissions are all similar. I'm a bit stumped as to what the issue could be.

 

Differences are:

Old vs New

Ubuntu 20.04 vs 22.04

Docker-Compose 1.25.0 vs 1.29.2

Docker 24.0.7 vs 24.0.5

 

Any ideas what could be causing this issue?

[ChatNoir]

8 hours ago, arlovelo said:

Differences are:

Old vs New

Ubuntu 20.04 vs 22.04

Docker-Compose 1.25.0 vs 1.29.2

Docker 24.0.7 vs 24.0.5

It is unclear for me if you are using Unraid. Seems not.

Not sure anyone can help you if you are on Ubuntu with different tools.

[realdiel]

Greetings! For some reason, Binhex - DelugeVPN won't run on my UNRAID server anymore. Its run fine for years prior so not sure what occurred to prevent it from running now. I've recently successfully replaced some capacity drives, but that's it. I've attempted to restart the app, reinstall it and now reboot my server. I can't get the web UI to load and my torrents don't appear to be seeding. My other dockers run fine. Is there a document that explains how to interpret a log file as there appears to be some line items there that could be of concern. The docker shows as started, but the log shows "Deluge Web UI not running".

 

Tinkering with Deluge further, I was able to install just the vanilla Deluge docker and pull up the web UI no problem.

 

Edit: Any suggestions on how to get DelugeVPN back up? I still have quite a few HnRs now despite it showing as running on the Docker page for UNRAID (can't pull up the web UI). I pulled up the console and checked for the host and it showed as offline and "Connection was refused by other side: 111: Connection refused. ". Not sure how to proceed here other than try another torrent client.

2Edit: 

You can close this one. I did an app restore for deluge and am up and running again.

 

3Edit: Can't pull up the web UI for Deluge and it appears to not be seeding. I've attempted to restore it as before, but still can't get this docker to work. Here's the log below. Any suggestions?

 

[info] Deluge process listening on port 58846

2023-12-18 22:44:53,993 WARN received SIGTERM indicating exit request
2023-12-18 22:44:53,994 DEBG killing watchdog-script (pid 72) with signal SIGTERM
2023-12-18 22:44:53,994 INFO waiting for watchdog-script to die
2023-12-18 22:44:53,994 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1531d72b5b10 current result: <twisted.python.failure.Failure builtins.AttributeError: 'ConnectionRefusedError' object has no attribute 'message'>>

2023-12-18 22:44:53,994 DEBG 'watchdog-script' stdout output:
[info] Waiting for child processes to exit...

2023-12-18 22:44:53,995 DEBG 'watchdog-script' stdout output:
[info] All child processes exited, exiting while loop...

2023-12-18 22:44:53,995 DEBG 'watchdog-script' stdout output:
[info] All child processes exited, exiting 'watchdog.sh' script...

2023-12-18 22:44:53,995 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22453359396560 for <Subprocess at 22453362367120 with name watchdog-script in state STOPPING> (stdout)>
2023-12-18 22:44:53,995 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22453377238224 for <Subprocess at 22453362367120 with name watchdog-script in state STOPPING> (stderr)>
2023-12-18 22:44:53,995 INFO stopped: watchdog-script (exit status 0)
2023-12-18 22:44:53,995 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
  https://hub.docker.com/u/binhex/

2023-12-18 22:48:03.566571 [info] Host is running unRAID
2023-12-18 22:48:03.586372 [info] System information Linux 00cbefe71d84 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 GNU/Linux
2023-12-18 22:48:03.608965 [info] PUID defined as '0'
2023-12-18 22:48:03.633366 [info] PGID defined as '0'
2023-12-18 22:48:03.691838 [info] UMASK defined as '000'
2023-12-18 22:48:03.714275 [info] Permissions already set for '/config'
2023-12-18 22:48:03.738033 [info] Deleting files in /tmp (non recursive)...
2023-12-18 22:48:03.765418 [info] VPN_ENABLED defined as 'no'
2023-12-18 22:48:03.786464 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2023-12-18 22:48:03.810486 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2023-12-18 22:48:03.835168 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2023-12-18 22:48:03.857653 [info] DELUGE_ENABLE_WEBUI_PASSWORD not defined,(via -e DELUGE_ENABLE_WEBUI_PASSWORD), defaulting to 'yes'
2023-12-18 22:48:03.882736 [info] Starting Supervisor...
2023-12-18 22:48:04,022 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2023-12-18 22:48:04,023 INFO Set uid to user 0 succeeded
2023-12-18 22:48:04,024 INFO supervisord started with pid 7
2023-12-18 22:48:05,026 INFO spawned: 'start-script' with pid 71
2023-12-18 22:48:05,028 INFO spawned: 'watchdog-script' with pid 72
2023-12-18 22:48:05,028 INFO reaped unknown pid 8 (exit status 0)
2023-12-18 22:48:05,031 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2023-12-18 22:48:05,031 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-12-18 22:48:05,031 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-12-18 22:48:05,031 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22652256504848 for <Subprocess at 22652256503888 with name start-script in state RUNNING> (stdout)>
2023-12-18 22:48:05,032 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22652269960464 for <Subprocess at 22652256503888 with name start-script in state RUNNING> (stderr)>
2023-12-18 22:48:05,032 INFO exited: start-script (exit status 0; expected)
2023-12-18 22:48:05,032 DEBG received SIGCHLD indicating a child quit
2023-12-18 22:48:05,046 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-12-18 22:48:05,049 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2023-12-18 22:48:05,050 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-12-18 22:48:05,246 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 ''
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-12-18 22:48:05,437 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 ''
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-12-18 22:48:05,635 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'ed245fa046284bd999b98097404968b9'
[info] Deluge key 'default_daemon' will have a new value 'ed245fa046284bd999b98097404968b9'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-12-18 22:48:05,670 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2023-12-18 22:48:06,104 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846
 

Edited December 19, 2023 by realdiel