NOTE: i don't use Deluge anymore, this page might get outdated over time.

Deluge is a solid torrent downloader daemon. After having some issues with Transmission, i decided to give Deluge a try and while i don't like the web UI of Deluge, it works.

Let's be clear: Deluge is perfect, just the UI has some issues for me:

  • doesn't scale at all for mobile browsers
  • cannot disable authentication
  • feels a bit Windows 95 Nostalgia style


Deluge is easily installed and managed within Gentoo Linux since there is an ebuild for it. All you need to do is to emerge it, but you want to enable both the console and web interface first. So create a file called /etc/portage/package.use/deluge with the following content:

net-p2p/deluge console webinterface

then emerge Deluge:

emerge -vp deluge

As usual move the home folder to /data/daemons/deluge:

usermod -m -d /data/daemons/deluge deluge

and add the deluge user to the media group:

usermod -a -G media deluge

Now you need to fix some settings in deluged config file, so edit /etc/conf.d/deluged:

DELUGED_OPTS="-p 58846 -l /data/daemons/deluge/deluged.log"

We want to:

  • start the service as group media
  • set umask to 0002 so that any downloaded files are accessible by the other tools
  • move the logfile of deluge to the /data/daemons/deluge folder
  • start with the new home folder

you might also want to play with the port (option -p).

Deluge comes with two pieces of software: the daemon itself and the nice web GUI. You also need to tweak the gui setup, so edit /etc/conf.d/deluge-web to reflect the change in the deluge data folder:


One last required step is to ensure that the other tools can access the deluge folder (to reach the download folders inside), so:

chgrp media /data/daemons/deluge

That's is, deluge is installed.

Reverse-Proxy configuration

Before you proceed, you should make Deluge web accessible via the reverse-proxy, so that access, configuration and usage will be simplified from the beginning.

Add this file to /etc/nginx/folders:

location /deluge {
    proxy_pass http://localhost:8112/;
    proxy_set_header X-Deluge-Base "/deluge/";
    add_header X-Frame-Options SAMEORIGIN;

Add the config to the Reverse Proxy and restart it.


You need to change a few configuration options but you need to to it after starting Deluge.

first start the Deluge services and set them to auto-start on reboot:

rc-update add deluged default
rc-update add deluge-web default
/etc/init.d/deluged start
/etc/init.d/deluge-web start

Now login to the web GUI at, you will need the default password “deluge” for the first login. You will also to confirm the connection in the popup dialog.

Open the Preference button, go to interface and update the password to an empty password: this will prevent Deluge to ask for a password again in the Web GUI. Go to the Plugins tab and enable the Labels plugin. Note that label creation is unconsistent, in some tools (like the *Arr's) labels will be created automatically, while on other tools you will have to manually create the labels from Deluge web GUI.


Every download client needs to be integrated in your other tools. Unfortunately, you need to do it by hand for every tool.

Every *Arr's tool has the same settingsdownloaders section that you can populate with the downloaders. Tap on the plus button and add the downloader. Test it before saving.

Prowlarr is a special case: you only need to define the downloader IF you plan to search from the Prowlarr web GUI, otherwise it's not needed. And no, Prowlarr will not synchronize your downloader to the other *Arr's, like it's done for indexers. Sad, but that's the way it is.


Head to from which you add your manual downloads or manage the automatic downloads added by the other tools.