Deluge Forum

https://ftp.osuosl.org/pub/deluge/windows/?C=M;O=D

Complete 2.1.1 -> 2.2.0 changelog is available here

As always, I recommend libtorrent v1.2.x for torrenting (running a thin client does not matter, just the daemon part). If you are looking for containers (Docker) for this latest version, they will be available shortly. You can always check Help -> About to see which version of the client and server are running and which libtorrent is running.

Hot Tip: I recommend putting the "Tracker" column on the farthest left of the torrent view pane and sliding it down as small as possible. I made a PR that fixes all tracker icons displaying as long as the tracker URL itself has a favicon.ico. If the tracker itself's URL does not have a favicon,you'll need to go to the "real" tracker site and add /favicon.ico to save it, then you can have the tracker icon by itself on the farthest left to reference which tracker they belong to quickly!

You must go to the tracker's real site with /favicon.ico added. This must be resized to 16x16 and saved as a PNG file with zero compression. The filename must be the same as the one displayed in the Trackers list. So if it's "tracker.domain.com/announce" for the full tracker URL in 'edit trackers', your filename needs to be "domain.com.png" 16x16 and placed in your config folder (%APPDATA%/deluge/icons), and Deluge will need to be restarted.

If you are having issues with tracker icons not loading, simply go to `%APPDATA%/deluge/icons` in explorer or wherever your config directory is, stop deluge's daemon and client, delete all the files in the icons folder, and restart deluge. They will repopulate slowly, but they will be formatted automatically and correctly and show up.

If you have any other questions, ideas/thoughts, start up a conversation!

Edit: Both Linuxserver.io and Binhex's containers are now on 2.2.0 - I will be removing my containers for the time being and recommend switching to one of the two. Binhex also has a VPN container for wireguard and OpenVPN if you need that capability. You can google "linuxserver deluge", "binhex deluge", or "binhex delugevpn" to find these containers and their respective repository links.

alternatively, https://hub.docker.com/search?q=deluge has a wealth of deluge containers including the first being linuxserver's. Binhex's container is called "arch-deluge" so wont show up first and is located https://hub.docker.com/r/binhex/arch-deluge

great work, thank you very much

deluge 2.2.0 is flagged with eset antivirus

As my good friend highvoltage above, really appreciate your dedication and efforts bud, well besides severely pixxed off about the unjust OS outing slash mockering, and with that mean of-course honored for the mention. Anyway just a quick pad on back from me too, even though little late to party, sorry, and to be honest actually only learned of deluge 2.2.0 right now from your post lol, feel little embarrassed, but hey, not as involved as you I must admit. Again, or what called, much love bro, thanks for the contribution and will leave you to it, sure have your hands full.

razki4302 wrote: ↑Thu May 01, 2025 7:00 pm deluge 2.2.0 is flagged with eset antivirus

See this post.

viewtopic.php?t=57055

ambipro wrote: ↑Tue May 06, 2025 5:11 am I've just pushed updates for my Docker images. The images correspond as described below and will remain with the tags listed for the time being.

ghcr.io/zakkarry/deluge-develop-docker for the container image associated below

image tags for develop branch
master - develop branch (identified as 2.1.1-dev146) using libttorrent v2.0.11
libtorrentv1 - develop branch like above using libtorrent v1.2.20

image tags for 2.2.0
libtorrentv1-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 2.0.11
libtorrentv2-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 1.2.20

(previously did not checkout release tag properly, version should now show "2.2.0" without any post per Cas)

You can view all images at the packages page for my fork of LSIO here.

There still may be tracker which have not whitelisted 2.2.0 so check your trackers before you go and pull the latest version, some take time to validate.

Will be working on getting the binhex repo up to date as well, have not had the time to do so yet.

Also, GeoIP flags are automatically updated when ran if they have not been updated in the last week in these images, so your flags will always be up to date.

I noticed the binhex-delugevpn was updated today, and the /icons dir made and populated with some images. They show fine on webUI for me, but not on thin client (Windows 11, client version 2.2.0). The GeoIP flags also aren't working - do I need to point to a specific file in the Settings -> Other section? Or should I leave that bit blank?

I've just pushed updates for my Docker images. The images correspond as described below and will remain with the tags listed for the time being.

ghcr.io/zakkarry/deluge-develop-docker for the container image associated below

image tags for develop branch
master - develop branch (identified as 2.1.1-dev146) using libttorrent v2.0.11
libtorrentv1 - develop branch like above using libtorrent v1.2.20

image tags for 2.2.0
libtorrentv1-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 2.0.11
libtorrentv2-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 1.2.20

(previously did not checkout release tag properly, version should now show "2.2.0" without any post per Cas)

You can view all images at the packages page for my fork of LSIO here.

There still may be tracker which have not whitelisted 2.2.0 so check your trackers before you go and pull the latest version, some take time to validate.

Will be working on getting the binhex repo up to date as well, have not had the time to do so yet.

Also, GeoIP flags are automatically updated when ran if they have not been updated in the last week in these images, so your flags will always be up to date.

sevo wrote: ↑Thu May 22, 2025 8:37 pm

ambipro wrote: ↑Tue May 06, 2025 5:11 am I've just pushed updates for my Docker images. The images correspond as described below and will remain with the tags listed for the time being.

ghcr.io/zakkarry/deluge-develop-docker for the container image associated below

image tags for develop branch
master - develop branch (identified as 2.1.1-dev146) using libttorrent v2.0.11
libtorrentv1 - develop branch like above using libtorrent v1.2.20

image tags for 2.2.0
libtorrentv1-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 2.0.11
libtorrentv2-2.2.0 - stable release (master branch - identifies as 2.2.0) using libtorrent 1.2.20

(previously did not checkout release tag properly, version should now show "2.2.0" without any post per Cas)

You can view all images at the packages page for my fork of LSIO here.

There still may be tracker which have not whitelisted 2.2.0 so check your trackers before you go and pull the latest version, some take time to validate.

Will be working on getting the binhex repo up to date as well, have not had the time to do so yet.

Also, GeoIP flags are automatically updated when ran if they have not been updated in the last week in these images, so your flags will always be up to date.

I noticed the binhex-delugevpn was updated today, and the /icons dir made and populated with some images. They show fine on webUI for me, but not on thin client (Windows 11, client version 2.2.0). The GeoIP flags also aren't working - do I need to point to a specific file in the Settings -> Other section? Or should I leave that bit blank?

I've been speaking with

mhertz wrote:tagging quote block

about how to do this on arch-base, which will apply to both his standard and VPN images.

But the icons on the thin client are entirely local, and have nothing to do with your daemon. As discussed in my now edited post above, you may have to clear the icons folder in your config while deluge isn't running on your windows machine, and then restart. They will sometimes take a bit to repopulate (few minutes) and if there are a lot of announces simultaneously, you may need to pause a bunch of the torrents so only like a few are active from each tracker, and restart deluge. timeouts and stuff happen as well, it's just pulling down the favicon.

They all work though, I haven''t found a tracker I'm on yet that doesn't have an icon available.