11 hours ago, strike said:

Simply put: wireguard

And I'm not sure, but I believe you have to rename it to wg0.conf

Awesome! Thanks for the response. Took a couple of shots at it, but I got all the changes made and I've got it up and running on WireGuard now!

Now...

How do I delete the password?

I went to look at it so I could plug the pwd into one of my arrs to use it as a download client. Of course, the pwd isn't displayed there, but I did look in the browser pwd manager, used that, and now I can't log in to either the Web GUI of the Deluge client or get a connection from the arr... 😢

2 hours ago, Free Man said:

How do I delete the password?

From the Deluge docs:

How can I reset forgotten password?

    Stop the Web UI before modifying the web.conf file.
    Edit web.conf in config and delete the entire pwd_sha1 line or use quick method via command-line e.g.:

sed -i.bak "/pwd_sha1/d" ~/.config/deluge/web.conf

    Start the Web UI and the password will have been reset to default password deluge.

However, even after deleting the pwd_sha1 line and restarting the container, it's still telling me the password is invalid!
I've typed the default password in plain text in notepad++ (to be sure I have it correct) and copy/pasted into the password prompt and it's not working.

Anyone have any suggestions?

Has this stopped working for anyone randomly?
It's been working fine for 6-12 months and after a server reboot today I can't conneted to the web interface with the VPN enabled.

If I disable the VPN then deluge will start without issue.

I've double-checked the password, tried using different servers, generated new config files from the PIA website but I can't get deluge to work with PIA VPN anymore.

I've attached the supervisor.log here: Deluge

18 hours ago, opticon said:

Has this stopped working for anyone randomly?
It's been working fine for 6-12 months and after a server reboot today I can't conneted to the web interface with the VPN enabled.

If I disable the VPN then deluge will start without issue.

I've double-checked the password, tried using different servers, generated new config files from the PIA website but I can't get deluge to work with PIA VPN anymore.

I've attached the supervisor.log here: Deluge

Yes, ran into same issue with PIA today.

It looks like the zipped ovpn files aren't working.

I logged into the PIA VPN site, and went to downloads

From there I scrolled to the bottom and went to the OpenVPN Configuration Generator

https://www.privateinternetaccess.com/account/ovpn-config-generator

I left it as OpenVPN 2.4 or newer

I left it as Windows (I hadn't paid attention, and since it worked I am typing it up with that)

For the location I chose the CA Ontario (because it was in the port forward list, I had tried Ireland before, which is also in the port forward list, but that failed)

Under Select Port I picked UDP/1197 - RSA-4096 - AES-256-GCM (top row, far right)

and then generated the file.

I then removed all other ovpn files from the OpenVPN config directory and restarted the container.

It finally got me back into Deluge.

I'm sure someone will be able to say what actually went wrong and also a better (more reasoned) solution. But for now this has me reconnected and hopefully it works for you as well!

1 hour ago, elbobo said:

Yes, ran into same issue with PIA today.

It looks like the zipped ovpn files aren't working.

I logged into the PIA VPN site, and went to downloads

From there I scrolled to the bottom and went to the OpenVPN Configuration Generator

https://www.privateinternetaccess.com/account/ovpn-config-generator

I left it as OpenVPN 2.4 or newer

I left it as Windows (I hadn't paid attention, and since it worked I am typing it up with that)

For the location I chose the CA Ontario (because it was in the port forward list, I had tried Ireland before, which is also in the port forward list, but that failed)

Under Select Port I picked UDP/1197 - RSA-4096 - AES-256-GCM (top row, far right)

and then generated the file.

I then removed all other ovpn files from the OpenVPN config directory and restarted the container.

It finally got me back into Deluge.

I'm sure someone will be able to say what actually went wrong and also a better (more reasoned) solution. But for now this has me reconnected and hopefully it works for you as well!

I've tried your exact settings but still no luck for me

39 minutes ago, opticon said:

I've tried your exact settings but still no luck for me

20 hours ago, opticon said:

Has this stopped working for anyone randomly?
It's been working fine for 6-12 months and after a server reboot today I can't conneted to the web interface with the VPN enabled.

If I disable the VPN then deluge will start without issue.

I've double-checked the password, tried using different servers, generated new config files from the PIA website but I can't get deluge to work with PIA VPN anymore.

I've attached the supervisor.log here: Deluge

I figured it out, I changed my DNS servers on my router to OpenDNS to test some parental controls a week ago. I changed it back to Cloudflare and I'm able to get back into Deluge

Yes stopped working for me. My server is set to cloudflare 1.1.1.1 as DNS and I have tried re-generating the PIA config, still no luck. No errors in the logs.

Working now I chose a VPN config hich support port mapping like person above. Initially the logs were saying the config I provided wasn't in the list of ones supporting it. So I chose one of the ones in that list in the logs.

DelugeVPN has Zero Bandwidth

New to the group, sorry if this is in the wrong spot. My delugeVPN stopped working today. I blew away the old config, downloaded a new / latest docker. It work, I select a torrent, it says downloading but then speed quickly goes to 0.00% and never changes. Below is a past of my logs and config. Any ideas? I even tried an old torrent that worked last week no problem. Any help is appreciated.

PIA username and password is verified.

Made sure preferences are correct to allow for downloads...

Tried Netherlands and Canada for VPN connections, same result

Config:

docker run

  -d

  --name='binhex-delugevpn'

  --net='bridge'

  --pids-limit 2048

  --privileged=true

  -e TZ="America/Phoenix"

  -e HOST_OS="Unraid"

  -e HOST_HOSTNAME="Tower"

  -e HOST_CONTAINERNAME="binhex-delugevpn"

  -e 'VPN_ENABLED'='yes'

  -e 'VPN_USER'='pxxx

  -e 'VPN_PASS’=‘xxx’

  -e 'VPN_PROV'='pia'

  -e 'VPN_CLIENT'='openvpn'

  -e 'STRICT_PORT_FORWARD'='yes'

  -e 'ENABLE_PRIVOXY'='yes'

  -e 'ENABLE_SOCKS'='no'

  -e 'SOCKS_USER'='admin'

  -e 'SOCKS_PASS'='socks'

  -e 'LAN_NETWORK'='192.168.1.0/24'

  -e 'VPN_INPUT_PORTS'=''

  -e 'VPN_OUTPUT_PORTS'=''

  -e 'DEBUG'='false'

  -e 'VPN_OPTIONS'=''

  -e 'ENABLE_STARTUP_SCRIPTS'='no'

  -e 'USERSPACE_WIREGUARD'='no'

  -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1'

  -e 'DELUGE_DAEMON_LOG_LEVEL'='info'

  -e 'DELUGE_WEB_LOG_LEVEL'='info'

  -e 'DELUGE_ENABLE_WEBUI_PASSWORD'='yes'

  -e 'ENABLE_HEALTHCHECK'='yes'

  -e 'HEALTHCHECK_COMMAND'=''

  -e 'HEALTHCHECK_ACTION'=''

  -e 'HEALTHCHECK_HOSTNAME'='google.com'

  -e 'PUID'='99'

  -e 'PGID'='100'

  -e 'UMASK'='000'

  -l net.unraid.docker.managed=dockerman

  -l net.unraid.docker.webui='http://[IP]:[PORT:8112]'

  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/deluge-icon.png'

  -p '8112:8112/tcp'

  -p '8118:8118/tcp'

  -p '9118:9118/tcp'

  -p '58846:58846/tcp'

  -p '58946:58946/tcp'

  -p '58946:58946/udp'

  -v '/mnt/cache/appdata/binhex-delugevpn':'/config':'rw'

  -v '/mnt/user/downloads/':'/mnt/user/downloads/':'rw'

  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-delugevpn'

a56af11f1c0e0438e4a1168b1664367c4870cad3ce5c316e90432f55dc4916c2

The command finished successfully!

Loggs:

[info] Successfully assigned and bound incoming port

2026-03-01 21:00:43,093 DEBG 'watchdog-script' stdout output:

[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.11.112.145 different, marking for reconfigure

2026-03-01 21:00:43,099 DEBG 'watchdog-script' stdout output:

[info] Deluge not running

2026-03-01 21:00:43,105 DEBG 'watchdog-script' stdout output:

[info] Deluge Web UI not running

2026-03-01 21:00:43,112 DEBG 'watchdog-script' stdout output:

[info] Privoxy not running

2026-03-01 21:00:43,112 DEBG 'watchdog-script' stdout output:

[info] Deluge incoming port 6890 and VPN incoming port 28001 different, marking for reconfigure

2026-03-01 21:00:43,115 DEBG 'watchdog-script' stdout output:

[info] Attempting to start Deluge...

[info] Removing deluge pid file (if it exists)...

2026-03-01 21:00:43,647 DEBG 'watchdog-script' stdout output:

[info] Deluge key 'listen_interface' currently has a value of '10.10.112.88'

[info] Deluge key 'listen_interface' will have a new value '10.11.112.145'

[info] Writing changes to Deluge config file '/config/core.conf'...

2026-03-01 21:00:43,972 DEBG 'watchdog-script' stdout output:

[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'

[info] Deluge key 'outgoing_interface' will have a new value 'tun0'

[info] Writing changes to Deluge config file '/config/core.conf'...

2026-03-01 21:00:44,273 DEBG 'watchdog-script' stdout output:

[info] Deluge key 'default_daemon' currently has a value of '9edaaf75fbe249ac9b19cacd9901ec63'

[info] Deluge key 'default_daemon' will have a new value '9edaaf75fbe249ac9b19cacd9901ec63'

[info] Writing changes to Deluge config file '/config/web.conf'...

2026-03-01 21:00:44,329 DEBG 'watchdog-script' stdout output:

[info] Deluge process started

[info] Waiting for Deluge process to start listening on port 58846...

2026-03-01 21:00:44,903 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/pluginmanagerbase.py:16: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

import pkg_resources

2026-03-01 21:00:45,019 DEBG 'watchdog-script' stdout output:

[info] Deluge process listening on port 58846

2026-03-01 21:00:45,521 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/ui/ui_entry.py:20: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

import pkg_resources

2026-03-01 21:00:48,228 DEBG 'watchdog-script' stdout output:

Setting "random_port" to: False

Configuration value successfully updated.

2026-03-01 21:00:48,800 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/ui/ui_entry.py:20: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

import pkg_resources

2026-03-01 21:00:51,378 DEBG 'watchdog-script' stdout output:

Setting "listen_ports" to: (28001, 28001)

Configuration value successfully updated.

2026-03-01 21:00:51,959 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/ui/ui_entry.py:20: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

import pkg_resources

2026-03-01 21:00:54,727 DEBG 'watchdog-script' stdout output:

[info] No torrents with state 'Error' found

2026-03-01 21:00:54,728 DEBG 'watchdog-script' stdout output:

[info] Starting Deluge Web UI...

2026-03-01 21:00:54,728 DEBG 'watchdog-script' stdout output:

[info] Deluge Web UI started

2026-03-01 21:00:54,731 DEBG 'watchdog-script' stdout output:

[info] Attempting to start Privoxy...

2026-03-01 21:00:55,386 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/pluginmanagerbase.py:16: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

import pkg_resources

2026-03-01 21:00:55,741 DEBG 'watchdog-script' stdout output:

[info] Privoxy process started

[info] Waiting for Privoxy process to start listening on port 8118...

2026-03-01 21:00:55,751 DEBG 'watchdog-script' stdout output:

[info] Privoxy process listening on port 8118

If you leave the logs a bit longer do you get any messages listing out PIA locations?

Firstly, thank you for your efforts and support.

Scenario 1 - I had exactly the same scenario as described above. It just stopped working. Stopping the docker, waiting for a while, starting the docker, it just hung at this point and would go no further, even after a long wait.

did a server restart

Scenario 2 - after a server restart it hung waiting for configuration from PIA and would just loop trying to download configuration (using the wireguard option)

did a server restart

the application started up successfully but is running very slowly barely achieving 1.0M/s down. I dare not stop the docker or restart the server just in case it goes sideways again.

... edit... I also think tha the app is locking drives and causing the server to freeze. stopping the docker seems to free things up, but i have no proof that this is the cause

Edited March 3Mar 3 by Flendor

Attached is a longer log capture. I have tried starting and stopping with no luck. Deluge Logs.rtf

On 2/22/2026 at 9:59 PM, Free Man said:

From the Deluge docs:

How can I reset forgotten password?

    Stop the Web UI before modifying the web.conf file.
    Edit web.conf in config and delete the entire pwd_sha1 line or use quick method via command-line e.g.:

sed -i.bak "/pwd_sha1/d" ~/.config/deluge/web.conf

    Start the Web UI and the password will have been reset to default password deluge.

However, even after deleting the pwd_sha1 line and restarting the container, it's still telling me the password is invalid!
I've typed the default password in plain text in notepad++ (to be sure I have it correct) and copy/pasted into the password prompt and it's not working.

Anyone have any suggestions?

I see no one has answered this! I'm in the same position. No way to change the password if forgotten? Do we have to delete the Docker image?

My DelugVPN webui currently isn't connecting. I had an issue with my server's power supply, which led to it being offline for a few weeks, but when I managed to get all the hardware in it working and the Unraid server restarted, all of a sudden my DelugVPN webui won't connect. Tried restarting the docker, rebooting the server, to no avail. Added logs. Any help would be awesome, I know this issue probably comes up a lot, but I've seen no solution to my specific instance so far.

DelugeVPN logs.txt

So it doesn't look like the VPN has actually connected. If your DelugeVPN config is set to not allow connection or has a VPN kill switch, and the VPN is not connected, the UI will not work.

I had the same problem many have reported recently; web GUI would not open. I tried some of the "fixes" mentioned above and none worked.

I have PIA and had configured DelugeVPN for Wireguard.

The only thing that resolved the problem for me was deleting DelugeVPN and the image, clearing out its appdata folder and reinstalling. I did not use Previous Apps to reinstall. I installed and configured DelugeVPN as if it were the first time I had used it. Success! The web GUI now opens as it should.

Deluge Logs.rtfDeluge Logs.rtfLooking for some help. I am running Unraid 7.2.4. My DelugeVPN went bad, so I uninstalled and reinstalled. It works, it's up, I can get to the web GUI, I can use the deluge extension in Edge to start a torrent. When the Torrent is added to the deluge GUI, I get the green light on the left, but under progress, it says downloading 0.00% and nothing downloads. I will paste the logs from the docker, but I did verify that VPN is up and working. I will also show a PIC of the bottom right corner with the error. I have all downloads pointed to the cache drive, the cache drive is half full, it has 126 GIG Free. I tried to change the down load location but same result. Any help would be hugely appreciated. I am stumped.

Edited April 10Apr 10 by knoorda

1 hour ago, knoorda said:

Deluge Logs.rtfDeluge Logs.rtfLooking for some help. I am running Unraid 7.2.4. My DelugeVPN went bad, so I uninstalled and reinstalled. It works, it's up, I can get to the web GUI, I can use the deluge extension in Edge to start a torrent. When the Torrent is added to the deluge GUI, I get the green light on the left, but under progress, it says downloading 0.00% and nothing downloads. I will paste the logs from the docker, but I did verify that VPN is up and working. I will also show a PIC of the bottom right corner with the error. I have all downloads pointed to the cache drive, the cache drive is half full, it has 126 GIG Free. I tried to change the down load location but same result. Any help would be hugely appreciated. I am stumped.

This sounds to me like permissions, we get this all the time at the Deluge forums (I'm a moderator and team member for Deluge) - if you wanna throw the book at the situation and see if its permissions, then just use chmod -R 777 /mnt/user/downloadsv2 and then restart the torrent download. If it doesn't work then I would take a look at the tracker announce itself - you can turn on LOGLEVEL to DEBUG and (assuming you don't have a shitload of torrents) you will see in the logs the announce and its response.

If you get a peer/seeder count, generallyt its ok but it could also not be able to connect to the peers and seeders themselves, which is an entirely different story.

Does the Status under Tracker tab show that Announce was Sent or Announce OK? Are you using a .torrent file when you say "Torrent is added" or a Magnet?

No offense, but those logs really only seem to show your VPN and startup stuff, and nothing to do with torrents being added. You'll need to enable AT LEAST info level logging - but preferably DEBUG for actual announce messsaging and responses.

Ambipro, thanks for the suggestions. I spent some time with Claude and was able to figure out I am not as bright as I thought and I had a bad data path in my config. All is working. Have a great weekend.

On 3/1/2026 at 1:00 AM, elbobo said:

Yes, ran into same issue with PIA today.

It looks like the zipped ovpn files aren't working.

I logged into the PIA VPN site, and went to downloads

From there I scrolled to the bottom and went to the OpenVPN Configuration Generator

https://www.privateinternetaccess.com/account/ovpn-config-generator

I left it as OpenVPN 2.4 or newer

I left it as Windows (I hadn't paid attention, and since it worked I am typing it up with that)

For the location I chose the CA Ontario (because it was in the port forward list, I had tried Ireland before, which is also in the port forward list, but that failed)

Under Select Port I picked UDP/1197 - RSA-4096 - AES-256-GCM (top row, far right)

and then generated the file.

I then removed all other ovpn files from the OpenVPN config directory and restarted the container.

It finally got me back into Deluge.

I'm sure someone will be able to say what actually went wrong and also a better (more reasoned) solution. But for now this has me reconnected and hopefully it works for you as well!

This seemed to work for me too - not sure if just certain locations are no longer forwarded or what the deal is...very strange. Thanks for sharing!

I tried to download the binhex-delugevpn docker container today and I am getting the following error during the install.

"

9110a387d7bf: Pull complete

06aec48c8706: Pull complete

Digest: sha256:2ff474cba3af585e15a608ffe03ca81ec4ac2e588f4462f584005081804fbd28

Status: Downloaded newer image for ghcr.io/binhex/arch-delugevpn:latest

9bed3ce35acc60da110bf0694525d2d7c15cf40a0bc9a22162621beb3e816e88

docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn (2eeb89e006f4eaa8416ab91ddf12943b2cff771bcf8b82a188ab84bffc57fab8): Bind for 0.0.0.0:58946 failed: port is already allocated.

The command failed.

"

Needless to say, the actual install failed. The Folder in Appdata is empty bu the docker container appears in my list of installed containers. Here are the allocations data listed for the container in UnRaid (version 7.2.4). Only the binhex-delugevpn containers is using the 58946 port, it is not allocated to any other container,

Is anyone able to connect to the webui when the vpn is enabled on 7.3? Since updating to Unraid 7.3 I'm no longer able to connect to the WebUi if the VPN is enabled. I don't see any errors in the log as well.

2 hours ago, TapIt said:

Is anyone able to connect to the webui when the vpn is enabled on 7.3? Since updating to Unraid 7.3 I'm no longer able to connect to the WebUi if the VPN is enabled. I don't see any errors in the log as well.

Working fine here. Please do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

1 hour ago, strike said:

Working fine here. Please do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Thanks for the quick reply, attached are the logs and the command

supervisord.logCommand Execution.txt

11 hours ago, TapIt said:

Thanks for the quick reply, attached are the logs and the command

supervisord.logCommand Execution.txt

Thanks. So your vpn tunnel is not connecting, and there are a few things here, you have this repeating in your log:

2026-05-14 15:38:46,957 DEBG 'start-script' stdout output:
2026-05-14 15:38:46 SIGHUP[soft,ping-restart] received, process restarting

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

You also have this in your log:

[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

Make sure the password is only a-z (upper or lower case),0-9, and not more than 99 characters long.