[http://deluge-torrent.org/ Deluge] is a full-featured BitTorrent client for Linux, OS X, Unix and Windows. It uses libtorrent in its backend and features multiple user-interfaces including: GTK+, web and console. It has been designed using the client server model with a daemon process that handles all the bittorrent activity. The Deluge daemon is able to run on headless machines with the user-interfaces being able to connect remotely from any platform. Deluge is not designed for any one desktop environment and will work just fine in GNOME, KDE, XFCE and others. Deluge is Free Software and is licensed under the GNU General Public License.

[http://deluge-torrent.org/ Deluge] is a lightweight but full-featured BitTorrent application written in python2. It has a variety of features, including but not limited to: a client/server model, DHT support, magnet links, a plugin system, UPnP support, full-stream encryption, proxy support, and three different client applications. When the server daemon is running, users can connect to it via a console client, a gtk-based GUI, or a Web-based UI. A full list of features can be viewed [http://dev.deluge-torrent.org/wiki/About here].

The gtk UI requires additional dependencies as does the Web UI. Inspect the pacman output to determine which are right for the intended application.

−

Please note, deluge works perfectly fine without its daemon running. The default user for the Deluge daemon, is '''deluge''', which is created upon package installation. You can change this in {{ic|/etc/conf.d/deluged}}. Of course, the user needs to exist.

+

python2-notify: libnotify notifications

+

pygtk: needed for gtk ui

+

librsvg: needed for gtk ui

+

python2-mako: needed for web ui

−

The rest of this guide will assume you use the default '''deluge''' user. This is that user's default home directory and therefore its configuration location is in {{ic|/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.

+

==Daemon Setup==

+

{{Warning|If multiple users are running a daemon, the default port (58846) will need to be changed for each user.}}

+

Deluge comes with a daemon called {{ic|deluged}}. If it is not running when one of the clients is run, it will be started. It is useful, however, to have it started with systemd to allow torrents to run without starting a client and/or Xorg. This can be accomplished in one of two ways: a system service or a user service.

−

Next, start the [[daemon]] to generate its default configuration in its home directory:

+

===System Service===

+

A system service will allow {{ic|deluged}} to run at boot without the need to start Xorg or a client. Deluge comes with a system service called {{ic|deluged.service}}, which can be started and enabled without change:

+

# systemctl start deluged

+

# systemctl enable deluged

+

This will run the deluge daemon as the '''deluge''' user, which is created by the deluge package. If you wish to run the daemon as another user, copy {{ic|/usr/lib/systemd/system/deluged.service}} to {{ic|/etc/systemd/system/deluged.service}} and change the User parameter within the file, such as the '''torrent''' user:

+

User='''torrent'''

+

In that case, you will have to create a user called '''torrent'''.

−

==Graphical Clients==

+

===User Service===

+

A user service will allow {{ic|deluged}} to run when {{ic|systemd --user}} is started. This is accomplished by creating a user service file:

+

{{hc|/etc/systemd/user/deluged.service|<nowiki>

+

[Unit]

+

Description=Deluge Daemon

+

After=network.target

−

===GTK UI===

+

[Service]

−

The GTK UI needs to have {{Pkg|pygtk}} and {{Pkg|librsvg}} installed on the clients.

+

Exec=/usr/bin/deluged -d -P %h/.config/deluge/deluge.pid

−

If the deluge daemon is running stop it.

+

−

In order to connect remotely via the GTK UI, there should be something like this in {{ic|/srv/deluge/.config/deluge/core.conf}}:

+

[Install]

−

"allow_remote": true,

+

WantedBy=default.target

+

</nowiki>}}

+

The deluge user service can now be started and enabled by the user:

+

$ systemctl --user start deluged

+

$ systemctl --user enable deluged

−

Now add yourself to the authentification file:

+

The {{ic|deluged}} user service can also be placed in {{ic|$HOME/.config/systemd/user/}}. See [[systemd/User]] for more information on user services.

The authentification level is not used at this time. Read [http://dev.deluge-torrent.org/wiki/UserGuide/Authentication more] about that.

+

==Configuration==

−

+

Deluge can be configured through any of the clients as well as by simply editting the JSON-formatted configuration files located in {{ic|$HOME/.config/deluge/}}. '''$HOME''' refers to the home directory of the user that {{ic|deluged}} is running as. This means that if the daemon is running as the '''deluge''' user, the default home directory is {{ic|/srv/deluge/}}.

−

Start the Deluge daemon again.

+

−

+

−

Now start the GTK UI. If you prefer, you can edit the preferences in {{ic|~/.config/deluge/gtkui.conf}}, but there's also a nice configuration tool in the UI.

The web UI daemon runs on the server and the clients only need a web browser. You need to install {{Pkg|python2-mako}} on the server.

+

−

+

−

First, start the web UI [[daemon]], named ''deluge-web'', and login at {{ic|http://''ip-address'':8112}}. Where ''ip-address'' is the name of your Deluge server or its private or public IP address. When asked for a password, enter "deluge" as it is 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.

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 daemon and then append to {{ic|/srv/deluge/.config/deluge/ssl/}}:

+

Deluge requires at least one port open for TCP and UDP to allow incoming connections for seeding. If deluge is informing you that it cannot open a port for incoming connections, you must open ports you wish to use. In this example, ports 56881 through 56889 are opened for TCP and UDP:

+

# iptables -A INPUT -p tcp --dport 56881:56889 -j ACCEPT

+

# iptables -A INPUT -p udp --dport 56881:56889 -j ACCEPT

+

If you are behind a NAT router/firewall, port forwards are also required there. UPnP may also be used, but that will not work with the local firewall on the system that the daemon is running on because it requires predefined ports.

+

{{Note|You can limit this to just one port, but you must open any ports for both TCP and UDP.}}

{{Warning|If multiple users are running a daemon, the default port (8112) will need to be changed for each user.}}

+

{{Note|It is recommended that you use '''https''' for the Web client.}}

+

{{Warning|The deluge Web client comes with a default password. See the Setup section.}}

+

The Web UI can be started by running {{ic|deluge-web}}, through a plugin in the gtk UI, or via systemd. It has many of the same features of the gtk UI, including the plugin system.

−

As of this writing, it is possible to use ProxyPass and ProxyPassReverse with Apache to run your Deluge web UI with a web server. To do so, install {{AUR|mod_proxy_html}} from the [[AUR]]. Then add the following lines to your {{ic|httpd.conf}}.

+

====System Service====

+

Deluge comes with a system service file called {{ic|deluge-web.service}}. The process for this is the same as starting {{ic|deluged.service}}, except with {{ic|deluge-web}} instead of {{ic|deluged}}. This service will also run as the '''deluge''' user unless the service file is modified in the same way as {{ic|deluged.service}}.

−

In the modules section add:

+

====User Service====

+

A user service will allow {{ic|deluge-web}} to run when {{ic|systemd --user}} is started. This is accomplished by creating a user service file:

+

{{hc|/etc/systemd/user/deluge-web.service|<nowiki>

+

[Unit]

+

Description=Deluge Web UI

+

After=deluged.service

−

LoadFile /usr/lib/libxml2.so

+

[Service]

−

LoadModule proxy_html_module modules/mod_proxy_html.so

+

Exec=/usr/bin/deluge-web --ssl

−

At the end of the file, in the Supplemental Configuration section, add the following two lines:

+

[Install]

+

WantedBy=default.target

+

</nowiki>}}

+

The deluge user service can now be started and enabled by the user:

+

$ systemctl --user start deluge-web

+

$ systemctl --user enable deluge-web

−

# Custom proxy html configuration

+

The {{ic|deluge-web}} user service can also be placed in {{ic|$HOME/.config/systemd/user/}}. See [[systemd/User]] for more information on user services.

−

Include conf/extra/httpd-proxy-html.conf

+

−

Also uncomment the Virtual Hosts line:

+

====Setup====

+

When {{ic|deluge-web}} is initially started, it will create {{ic|$HOME/.config/deluge/web.conf}}. The password in this file is hashed with SHA1 and salted. The default password is '''deluge'''. On the first visit, you will be advised to change the password.

−

Include conf/extra/httpd-vhosts.conf

+

You will also be greeted by a warning from your browser that the SSL certificate is untrusted. You must add an exception to this in your browser to continue on. See the [[OpenSSL]] page for information on creating your own certificate.

−

That is all the editing that needs to be done for the {{ic|httpd.conf}}. Next, navigate to the {{ic|extra/}} folder and edit the {{ic|httpd-vhosts.conf}} file. Append to the file, the following:

+

==Headless Setup==

+

Deluge is quite useful on a headless system, often referred to as a seed box, because of its client/server model. To set up deluge on a headless system, set up the daemon as shown above.

−

{{bc|<VirtualHost *:80>

+

===Create a User===

+

To allow interaction with the server remotely, create a user in {{ic|$HOME/.config/deluge/auth}}. For example:

+

$ echo "delugeuser:p422WoRd:10" >> $HOME/.config/deluge/auth

+

{{Note|The user/password created does not have to match any system users, and to maintain good security practices it should NOT!}}

+

{{Note|The user/password in this file are not hashed or salted like in the web client config.}}

−

Servername dmz

+

The number '''10''' corresponds to a level of '''Admin'''. Refer to the following table for additional values:

−

ProxyRequests off

+

{| class="wikitable" align="center"

−

ProxyHTMLExtended on

+

|-

−

ProxyPass /deluge http://127.0.0.1:8112/

+

! Level Name !! Level Value

−

ProxyHTMLURLMap http://127.0.0.1:8112 /deluge

+

|-

+

| None || 0

+

|-

+

|Read Only || 1

+

|-

+

| Normal || 5

+

|-

+

| Admin || 10

+

|}

−

Header unset Server

+

{{Note|In Deluge 1.35, these values have no effect, but multiuser options are under development.}}

−

<location /deluge>

+

===Firewall===

−

ProxyPassReverse /

+

You will need to open the port for remote access. The following example uses the default daemon port (58846):

−

ProxyPassReverseCookiePath / /deluge/

+

# iptables -A INPUT -p tcp --dport 58846 -j ACCEPT

−

SetOutputFilter INFLATE;proxy-html;DEFLATE

+

See [[iptables]] for more information on firewall rules.

−

ProxyHTMLURLMap / /deluge/ ec <br>

+

−

ProxyHTMLURLMap /deluge /deluge ec <br>

+

−

ProxyHTMLURLMap ([^*])(\/[^*].*) $1/deluge$2 hRxL

+

−

#ProxyHTMLLogVerbose On

+

−

Order allow,deny

+

−

Allow from all

+

−

</Location>

+

−

</VirtualHost>

+

If you are behind a NAT router/firewall, a port forward is also required there to access the daemon from outside the network.

−

}}

+

−

See http://blog.stoked-security.com/2011/03/deluge-bittorrent-webui-behind-reverse.html for the source and more information.

+

===Connect===

+

In the console client:

+

connect <host>[:<port>] <user> <password>

−

==Troubleshooting==

+

In the gtk client, {{ic|'''Edit -> Connection Manager -> Add'''}}.

−

=== Web UI doesn't store settings ===

+

In the Web client, {{ic|'''Connection Manager -> Add'''}}.

−

For some yet unknown reason, the web interface with Deluge 1.3.3 refuses to properly store the incoming (listen) ports configuration. This can manually be edited in core.conf. The Deluge bugtracker mentions this is fixed, it is not in 1.3.3.

Deluge is a lightweight but full-featured BitTorrent application written in python2. It has a variety of features, including but not limited to: a client/server model, DHT support, magnet links, a plugin system, UPnP support, full-stream encryption, proxy support, and three different client applications. When the server daemon is running, users can connect to it via a console client, a gtk-based GUI, or a Web-based UI. A full list of features can be viewed here.

Daemon Setup

Warning: If multiple users are running a daemon, the default port (58846) will need to be changed for each user.

Deluge comes with a daemon called deluged. If it is not running when one of the clients is run, it will be started. It is useful, however, to have it started with systemd to allow torrents to run without starting a client and/or Xorg. This can be accomplished in one of two ways: a system service or a user service.

System Service

A system service will allow deluged to run at boot without the need to start Xorg or a client. Deluge comes with a system service called deluged.service, which can be started and enabled without change:

# systemctl start deluged
# systemctl enable deluged

This will run the deluge daemon as the deluge user, which is created by the deluge package. If you wish to run the daemon as another user, copy /usr/lib/systemd/system/deluged.service to /etc/systemd/system/deluged.service and change the User parameter within the file, such as the torrent user:

User=torrent

In that case, you will have to create a user called torrent.

User Service

A user service will allow deluged to run when systemd --user is started. This is accomplished by creating a user service file:

The deluged user service can also be placed in $HOME/.config/systemd/user/. See systemd/User for more information on user services.

Configuration

Deluge can be configured through any of the clients as well as by simply editting the JSON-formatted configuration files located in $HOME/.config/deluge/. $HOME refers to the home directory of the user that deluged is running as. This means that if the daemon is running as the deluge user, the default home directory is /srv/deluge/.

Firewall

Deluge requires at least one port open for TCP and UDP to allow incoming connections for seeding. If deluge is informing you that it cannot open a port for incoming connections, you must open ports you wish to use. In this example, ports 56881 through 56889 are opened for TCP and UDP:

If you are behind a NAT router/firewall, port forwards are also required there. UPnP may also be used, but that will not work with the local firewall on the system that the daemon is running on because it requires predefined ports.

Note: You can limit this to just one port, but you must open any ports for both TCP and UDP.

Clients

Console

The console client can be run with:

$ deluge-console

Enter the help command for a list of available commands.

Gtk

Note: If you plan on using the daemon (server) functionality, it is wise to disable Classic Mode in Edit -> Preferences -> Interface. This requires a restart of the client.

Label - Allows labels to be assigned to torrents, as well as state, tracker, and keyword filters

Notifications - Provides notifications (email, pop-up, blink, sound) for events as well as other plugins

Scheduler - Limits active torrents and their speed on a per-hour, per-day basis

WebUi - Allows the Web UI to be started via the gtk client

Web

Warning: If multiple users are running a daemon, the default port (8112) will need to be changed for each user.

Note: It is recommended that you use https for the Web client.

Warning: The deluge Web client comes with a default password. See the Setup section.

The Web UI can be started by running deluge-web, through a plugin in the gtk UI, or via systemd. It has many of the same features of the gtk UI, including the plugin system.

System Service

Deluge comes with a system service file called deluge-web.service. The process for this is the same as starting deluged.service, except with deluge-web instead of deluged. This service will also run as the deluge user unless the service file is modified in the same way as deluged.service.

User Service

A user service will allow deluge-web to run when systemd --user is started. This is accomplished by creating a user service file:

The deluge-web user service can also be placed in $HOME/.config/systemd/user/. See systemd/User for more information on user services.

Setup

When deluge-web is initially started, it will create $HOME/.config/deluge/web.conf. The password in this file is hashed with SHA1 and salted. The default password is deluge. On the first visit, you will be advised to change the password.

You will also be greeted by a warning from your browser that the SSL certificate is untrusted. You must add an exception to this in your browser to continue on. See the OpenSSL page for information on creating your own certificate.

Headless Setup

Deluge is quite useful on a headless system, often referred to as a seed box, because of its client/server model. To set up deluge on a headless system, set up the daemon as shown above.

Create a User

To allow interaction with the server remotely, create a user in $HOME/.config/deluge/auth. For example:

$ echo "delugeuser:p422WoRd:10" >> $HOME/.config/deluge/auth

Note: The user/password created does not have to match any system users, and to maintain good security practices it should NOT!

Note: The user/password in this file are not hashed or salted like in the web client config.

The number 10 corresponds to a level of Admin. Refer to the following table for additional values:

Level Name

Level Value

None

0

Read Only

1

Normal

5

Admin

10

Note: In Deluge 1.35, these values have no effect, but multiuser options are under development.

Firewall

You will need to open the port for remote access. The following example uses the default daemon port (58846):