From ArchWiki
Jump to navigation Jump to search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

This article will show you how to set up Deluge for daemon-based torrenting.


# pacman -S deluge

Well, that was easy.

For web ui you will also need python-mako:

# pacman -S python-mako

For gtk ui you will also additionally need pygtk and librsvg:

# pacman -S pygtk librsvg


daemon and web ui

The default user for deluged, the Deluge daemon, is "deluge". You can change this in Template:Filename. Of course, the user needs to exist. In the case of the default "deluge" user, no manual user creation is necessary as the package script has done that for you.

The rest of this guide will assume you use the default "deluge" user. This user's default home dir and therefore its configuration location is in /srv/deluge. This should be fine under most circumstances. Note that this is NOT the default download location, it only holds its configuration and ssl certificates. You will be able to change all other options later on once you get a client working.

Next, start the daemon to generate its default configuration in its homedir:

# /etc/rc.d/deluged start

Finally, start the web ui:

# /etc/rc.d/deluge-web start

and login in on http://deluge-machine:8112. Where 'deluge-machine' is name of your deluge server or its private or public IP address. When asked for a password, enter "deluge" as it's the default password.

The preferences in the web ui should be rather self explanatory and the first obvious thing to do is to change your password.

As usual, you should add the daemons to your Template:Filename:

DAEMONS=( ... network deluged deluge-web ... )

Just make sure your network connection is up at the time you start either of those Deluge daemons.


In case you want SSL for the web ui, you need to generate a new cert/key set. To do this, first stop the web ui:

# /etc/rc.d/deluge-web stop

then go to /srv/deluge/.config/deluge/ssl/ and issue:

# openssl req -new -x509 -nodes -out deluge.cert.pem -keyout deluge.key.pem

Next you need to edit Template:Filename and change the pkey and cert configuration directives to use your new self-signed certificates and also enable SSL:

"pkey": "ssl/deluge.key.pem",
"cert": "ssl/deluge.cert.pem",
"https": true,

Afterwards just start the web ui again and you should be good to go:

# /etc/rc.d/deluge-web start