All default plugins gone on most recent docker image (2.2.0)

[dirchar]

2026-02-15-103728_hyprshot.png (40.69 KiB) Viewed 1080 times

This is a fresh pull with a default compose. If you have anything that relies on these plugins they will error out (sonarr/radarr)

[ambipro]

What Docker image are you using? I've worked with both binhex and LinuxServer to implement my GeoIP.dat update (you can manually find it at https://geo.el0.org) and to include my ltConfig plugin, which I maintain, as well as the updated Stats plugin with a bug fix.

These would have been copied when you pulled the image and ran it - so try stopping the container....

Pull ghcr.io/linuxserver/deluge:libtorrentv1-version-2.2.0 for no VPN

If using a VPN pull ghcr.io/binhex/arch-delugevpn:libtorrentv1

docker image rm --force imageid

Get the image ID by doing

docker image ls

and then run docker compose up -d again and see if they return.

[gist901]

Samething for me. The new image made all of my plugins including custom ones disappear.

I ended up just down grading my image back to deluge:2.2.0-r1-ls363 and all of my configs / plugins have properly returned

@ambipro - Whats the benefit of using arch-delugevpn:libtorrentv1 over the default version if using VPN, such as gluetun?

edit: using ghcr.io/linuxserver/deluge:libtorrentv1-version-2.2.0 worked for me

[dirchar]

This is my compose (which I pulled straight from linuxserver.io, only modified the directories)

Code: Select all

---
services:
  deluge:
    image: lscr.io/linuxserver/deluge:latest
    container_name: deluge
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - DELUGE_LOGLEVEL=error #optional
    volumes:
      - //mydirectories/deluge/config:/config
      - /mydirectories/downloads:/downloads
    ports:
      - 8112:8112
      - 6881:6881
      - 6881:6881/udp
      - 58846:58846 #optional
    restart: unless-stopped

image: lscr.io/linuxserver/deluge:latest

id: d2f2781cdaf3

This popped up because my container on my nas ran into the same problem so I tried a fresh install on another device and got the same results.

[dirchar]

This is my compose (which I pulled straight from linuxserver.io, only modified the directories)

Code: Select all

---
services:
  deluge:
    image: lscr.io/linuxserver/deluge:latest
    container_name: deluge
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - DELUGE_LOGLEVEL=error #optional
    volumes:
      - //mydirectories/deluge/config:/config
      - /mydirectories/downloads:/downloads
    ports:
      - 8112:8112
      - 6881:6881
      - 6881:6881/udp
      - 58846:58846 #optional
    restart: unless-stopped

image: lscr.io/linuxserver/deluge:latest

id: d2f2781cdaf3

This popped up because my container on my nas ran into the same problem so I tried a fresh install on another device and got the same results.

This, howeverworks: ghcr.io/linuxserver/deluge:libtorrentv1-version-2.2.0

[ambipro]

Samething for me. The new image made all of my plugins including custom ones disappear.

I ended up just down grading my image back to deluge:2.2.0-r1-ls363 and all of my configs / plugins have properly returned

@ambipro - Whats the benefit of using arch-delugevpn:libtorrentv1 over the default version if using VPN, such as gluetun?

edit: using ghcr.io/linuxserver/deluge:libtorrentv1-version-2.2.0 worked for me

Gluetun causes so many problems for users across all the projects I am part of and the Starr apps etc. Some torrent trackers even have rules against using VPN's that arent dedicated IP's just for you and approved after being told what provider it is...this goes for the API (think prowlarr/jackett) as well as browsing the site.

Generally speaking, unless you are in a restrictive country or a banned country like UK/DE or RU respectively, you only really need to run a VPN for the torrent client. Being in the swarms is what is dangerous, not browsing. If you are afraid of staff, that just means you are doing something wrong and you should reassess.

Anyway, run whatever you like - I'll get in touch with the LSIO team and let them know about the problem.

As far as libtorrentv1 goes, it just performs better - particularly with my profile for ltConfig - you can check the TUNING AND TWEAKS post in the plugins section for a play by play - and then go to my github and download the .egg, and follow the instructions in the README.

Keep in mind, its not a one size fits all solution to just copy someone config, but if your hardware is fairly similar to mine then you could just apply my profile and give it a try. There will be some more profiles added here in another release probably within a weeks time.

[ambipro]

This is my compose (which I pulled straight from linuxserver.io, only modified the directories)

Code: Select all

---
services:
  deluge:
    image: lscr.io/linuxserver/deluge:latest
    container_name: deluge
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - DELUGE_LOGLEVEL=error #optional
    volumes:
      - //mydirectories/deluge/config:/config
      - /mydirectories/downloads:/downloads
    ports:
      - 8112:8112
      - 6881:6881
      - 6881:6881/udp
      - 58846:58846 #optional
    restart: unless-stopped

image: lscr.io/linuxserver/deluge:latest

id: d2f2781cdaf3

This popped up because my container on my nas ran into the same problem so I tried a fresh install on another device and got the same results.

This, howeverworks: ghcr.io/linuxserver/deluge:libtorrentv1-version-2.2.0

First of all, you should never use the default torrent port of 6881 - I know they put it there, but there ARE clients that do not accept it because it is obvious what sort of traffic would be on that port, and DPI (Deep Packet Inspection) in certain countries is already bad enough of an obstacle. Pick a different random port above 20000 and change the settings, you should keep your outgoing port set as random.

[ambipro]

Found out what happened, the latest version of python setuptools dropped support for pkg_resources, so the Alpine packagers had to patch it, but in doing so they seem to have broken plugin display.

https://github.com/linuxserver/docker-deluge/issues/229

[dirchar]

First of all, you should never use the default torrent port of 6881 - I know they put it there, but there ARE clients that do not accept it because it is obvious what sort of traffic would be on that port, and DPI (Deep Packet Inspection) in certain countries is already bad enough of an obstacle. Pick a different random port above 20000 and change the settings, you should keep your outgoing port set as random.

My guy this is the default compose from the default docker image from the first hit on 'deluge docker' @ https://hub.docker.com/r/linuxserver/deluge, take it up with linuxserver.io. I am trying to show you that using the default compose file suggested the software is obviously broken and instead of going "oh **** it is broken, you're right" you come back with "UHMN ACKSHUALLY YOU SHOULD USE A DIFFERENT PORT"

How about fix your **** instead of having whatever disease devs have where they gotta prove they're right all the time, ****

[ambipro]

Removed my reply that was here:

Evidently I can be subject to profanity and name calling, but am unable to defend myself in kind on the internet to abuse and name calling without receiving subsequent complaints to an easily temporarily solved problem while a more permanent solution is worked out.

From the very beginning I had reached out to linuxserver, and even noted that I was doing so - but that apparently was ignored completely.