On 9/30/2026 at 1:40 PM, Alex_75 said:

I have some issue with pia wireguard. The docker not start i got this error:

2026-09-30 20:38:47,877 DEBG 'start-script' stderr output:

jq: parse error: Invalid numeric literal at line 1, column 6

2026-09-30 20:38:47,877 DEBG 'start-script' stdout output:

[warn] Failed to download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

2026-09-30 20:38:47,877 DEBG 'start-script' stdout output:

[warn] Unable to generate token for port forwarding, creating file '/tmp/portfailure' to indicate failure...

2026-09-30 20:38:47,879 DEBG 'start-script' stdout output:

[info] Script finished to assign incoming port

I am having this issue suddenly now as well. I am not sure when it started as I have been away for over a week. deluge will not start with strict port forwarding enabled with PIA. I cannot seem to get it to work.

Binhex, do you have any update that can correct this please?

Never mind. PIA changed the server addresses. I was using Toronto and it wasca-torontoca.privacy.network but NOW it's ca-toronto.pvt.site Thanks again PIA for changing long running parameters willienilly without notifying your users. My server has been down for who knows how long. Effing wonderful. At least it's fixed now.

Edited October 2Oct 2 by craigr

Binhex. Thank you for making the log so outstanding. I got this fixed quickly because of it and it's helped me more times than I can remember over the many many years I have used your Docker.

Much respect man!

It appears an update that rolled out in the past few hours has broken the label plugin.

The label plugin is showing on the left hand side but the label column is no longer there.

Disabling and reenabling has not fixed the issue.

34 minutes ago, JWMutant said:

It appears an update that rolled out in the past few hours has broken the label plugin.

The label plugin is showing on the left hand side but the label column is no longer there.

Disabling and reenabling has not fixed the issue.

Yup, most of my settings were erased and defaulted. All plugins seem to no longer be working, I think deluge dropped support for Python 2 entirely and maybe those plugins relied on that?

From what I can see python has gone from 3.13 to 3.14 with the update.

2 hours ago, JWMutant said:

It appears an update that rolled out in the past few hours has broken the label plugin.

The label plugin is showing on the left hand side but the label column is no longer there.

Disabling and reenabling has not fixed the issue.

Glad I came here before updating - I'll hold off for now.

22 hours ago, binhex said:

This should now be fixed, please pull down latest.

Yes! Working as normal. Thanks!!

19 hours ago, z0ki said:

Glad I came here before updating - I'll hold off for now.

What do I have to roll back too for the labels to work again?

15 minutes ago, strahd_zarovich said:

What do I have to roll back too for the labels to work again?

It doesn't work to install the plugin again? You can try to roll back by going to the template and add ":2.2.0-1-04" (without quotes) to the end of the repository field.

1 hour ago, strike said:

It doesn't work to install the plugin again? You can try to roll back by going to the template and add ":2.2.0-1-04" (without quotes) to the end of the repository field.

I tried a whole fresh install and it none of the plugins I usually use worked (block list, label, auto add, it-utils, ect). I rolled back to ":2.2.0-1-04" and they work again. Worst part of label not working is that the arr's cant pass the identifier label over so they cant import or monitor what's being passed into deluge.

Edited October 3Oct 3 by macieksoft

22 minutes ago, macieksoft said:

I tried a whole fresh install and it none of the plugins I usually use worked (block list, label, auto add, it-utils, ect). I rolled back to ":2.2.0-1-04" and they work again. Worst part of label not working is that the arr's cant pass the identifier label over so they cant import or monitor what's being passed into deluge.

Yeah, I know. I would suggest moving over to qbittorrent when you have the chance, as it's more actively maintained and is now the most-used client.

@binhex just adding some info here in case there's anything you can/want to do about the issue with plugins not loading on the latest image.

Looks like a known but unresolved issue upstream: https://dev.deluge-torrent.org/ticket/3653

Relevant part from my logs:

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

LSIO have worked around it with this: https://github.com/linuxserver/docker-deluge/issues/229#issuecomment-4183426698

I also tried a fresh install (tag "latest") and found that the AutoAdd plugin worked as I'd configured it, but it wasn't listed in the Preferences sidebar, and I couldn't change the AutoAdd configuration. I rolled back to ":2.2.0-1-04", and the AutoAdd plugin was listed in the Preferences sidebar, and I could edit the AutoAdd config in the web interface.

I appreciate stike's suggestion to perhaps have a closer look at qbittorrent ("it's more actively maintained and is now the most-used client"). I will do so when I have a bit more time. Thanks.

On 10/3/2026 at 5:35 PM, strike said:

It doesn't work to install the plugin again? You can try to roll back by going to the template and add ":2.2.0-1-04" (without quotes) to the end of the repository field.

Thank you, the latest version was simply not working for me. It wouldn't generate a new wg0.conf file based on my PIA credentials and was spamming errors in the logs. Rolling back to that version got it working as before.

On 10/3/2026 at 4:35 PM, strike said:

It doesn't work to install the plugin again? You can try to roll back by going to the template and add ":2.2.0-1-04" (without quotes) to the end of the repository field.

Thank you very much!

Has the label issue been fixed yet?

I can not get my password to reset. I've tried removing the container, removing the password from /auth and 'web.conf'. The program keeps making this edit to the auth files. Does anyone know what the SHA1 is supposed to be?

```admin:deluge:10

localclient:d3a1a56475d07f43dabc86a4473c4790a67d6b68:10```

On 10/9/2026 at 5:35 PM, jacob2040 said:

I can not get my password to reset. I've tried removing the container, removing the password from /auth and 'web.conf'. The program keeps making this edit to the auth files. Does anyone know what the SHA1 is supposed to be?

```admin:deluge:10

localclient:d3a1a56475d07f43dabc86a4473c4790a67d6b68:10```

Which password are you talking about? For the webui or thin client? The auth file is for the thin client, so there's no need to mess with that if it's the webui password you want to reset.

On 10/8/2026 at 8:00 PM, z0ki said:

Has the label issue been fixed yet?

After the latest update to the container, the labels are showing again for me.

On 10/8/2026 at 8:00 PM, z0ki said:

Has the label issue been fixed yet?

After the latest update, labels are showing again for me.

Yep, plugins are fixed for me too, thanks Binhex!
I had to do a force update from the docker page to get the version with the fix when using the :latest tag.

docker exec binhex-delugevpn cat /etc/image-build-info

# expect IMAGE_RELEASE_TAG=2.2.0-7-09 or later

While troubleshooting the broken plugins I also discovered I was using two out-of-date plugins that have newer versions by new maintainers in new repos. If anyone else are using these it's probably a good idea to install the newer versions

• ltConfig

  • https://github.com/zakkarry/deluge-ltconfig/releases/tag/v2.1.1

  • Also see tuning tips here: https://forum.deluge-torrent.org/viewtopic.php?t=56921

• AutoRemovePlus

  • http://github.com/tote94

Tried a fresh pull with ghcr.io/binhex/arch-delugevpn and ghcr.io/binhex/arch-delugevpn:latest. I still get a build where the WebUI plugins will not work.

4 minutes ago, Antibios said:

Tried a fresh pull with ghcr.io/binhex/arch-delugevpn and ghcr.io/binhex/arch-delugevpn:latest. I still get a build where the WebUI plugins will not work.

Did you try a force update like suggested in the post over yours?

5 minutes ago, Antibios said:

Adding "# expect IMAGE_RELEASE_TAG=2.2.0-7-09 or later" to /etc/image-build-info? Didn't do anything for me no.
Going back to :2.2.0-1-04 until this is properly sorted.

You're on unriad right? Did you click the "force update" button?

That fixed it. I completely misread that post. I think it's time for bed LOL

Edited October 17Oct 17 by Antibios