Difference between revisions of "Deluge"

From ArchWiki
Jump to: navigation, search
Line 22: Line 22:
 
==Daemon Setup==  
 
==Daemon Setup==  
 
Deluge can run as a system daemon which is accessible to any system user or it can run in a non-daemon mode.  The focus of this article is on the daemon mode of operation.
 
Deluge can run as a system daemon which is accessible to any system user or it can run in a non-daemon mode.  The focus of this article is on the daemon mode of operation.
 +
 +
{{Note|Advanced users are free to edit the configuration files in the deluge daemon home directory {{ic|/srv/deluge/.config/}} manually or from the {{ic|/usr/bin/deluge-console}}. The rest of this guide is written using the gtk client to do this from convenience of a GUI.}}
  
 
Start the deluge backend daemon like any other systemd service:
 
Start the deluge backend daemon like any other systemd service:
Line 48: Line 50:
 
{{Note|In Deluge 1.35, these values have no effect, but multiuser options are under development.}}
 
{{Note|In Deluge 1.35, these values have no effect, but multiuser options are under development.}}
  
===GTK UI===
+
 
 +
 
 
#Load the gtk client {{ic|/usr/bin/deluge-gtk}}  
 
#Load the gtk client {{ic|/usr/bin/deluge-gtk}}  
 
#Disable '''classic mode''' from the Edit>Preferences>Interface.
 
#Disable '''classic mode''' from the Edit>Preferences>Interface.
Line 59: Line 62:
 
#Click the "+ Add" button.
 
#Click the "+ Add" button.
  
If the correct credentials were populated, a green light should appear adjacent to the name of the server.  To connect, hit the "Connect" button.
+
If the correct credentials were populated, a green light should appear options for interaction  adjacent to the name of the server.  To connect, hit the "Connect" button.
  
 
Users can now configure their server from the GUI.  Most of the options are self explanatory and intuitive.  More details are available on the official [http://dev.deluge-torrent.org/wiki/UserGuide/BandwidthTweaking Deluge wiki] for details.   
 
Users can now configure their server from the GUI.  Most of the options are self explanatory and intuitive.  More details are available on the official [http://dev.deluge-torrent.org/wiki/UserGuide/BandwidthTweaking Deluge wiki] for details.   

Revision as of 15:32, 1 January 2013

Summary help replacing me
Deluge is a lightweight, BitTorrent client written in python that offers users a powerful client/server architecture. Once a headless daemon has been setup, user can interact with it in three ways including a WebUI, GTK-UI, and console interface.
Related Articles
PeerGuardian Linux
Ufw

Installation

deluge is available from the official repositories.

# pacman -S deluge

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

python2-notify: libnotify notifications
pygtk: needed for gtk ui
librsvg: needed for gtk ui
python2-mako: needed for web ui

Daemon Setup

Deluge can run as a system daemon which is accessible to any system user or it can run in a non-daemon mode. The focus of this article is on the daemon mode of operation.

Note: Advanced users are free to edit the configuration files in the deluge daemon home directory /srv/deluge/.config/ manually or from the /usr/bin/deluge-console. The rest of this guide is written using the gtk client to do this from convenience of a GUI.

Start the deluge backend daemon like any other systemd service:

# systemd start deluged

To allow interaction with the daemon, create a user:password:level in /srv/deluge/.config/deluge/auth. For example:

# echo "delugeuser:p422WoRd:10" >> /srv/deluge/.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!

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.


  1. Load the gtk client /usr/bin/deluge-gtk
  2. Disable classic mode from the Edit>Preferences>Interface.

A restart of the client is required for these changes to take effect. Exit the client and reload it.

  1. Setup the client to point to the daemon from Edit>Connection Manager.
  2. Delete the dummy server by hightlighting it and clicking the "Remove" button.
  3. Create an entry to the daemon via the "Add" button populating the resulting dialog with either the IP address or the word "localhost" as the hostname. Populate the "Username" and "Password" fields with the username and password used in the daemons setup.
  4. Click the "+ Add" button.

If the correct credentials were populated, a green light should appear options for interaction adjacent to the name of the server. To connect, hit the "Connect" button.

Users can now configure their server from the GUI. Most of the options are self explanatory and intuitive. More details are available on the official Deluge wiki for details.

Web UI

A web UI daemon runs on the server and the clients only need a web browser. You need to install python2-mako on the server.

First, start the web UI daemon, named deluge-web, and login at 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.

Automatically Connect To Daemon

If you want to avoid clicking "connect" everytime you start the Deluge web UI, edit the web.conf file in your configuration directory (usually /srv/deluge/.config/deluge). It should have a line like this towards the bottom:

"default_daemon": "" 

Change it to:

"default_daemon": "127.0.0.1:58846" 

This assumes that your Deluge port is the default 58846.

SSL

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 /srv/deluge/.config/deluge/ssl/:

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

Next you need to edit /srv/deluge/.config/deluge/web.conf 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 daemon again.

Apache configuration

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, add the following lines to your httpd.conf.

Uncomment the Virtual Hosts line:

Include conf/extra/httpd-vhosts.conf

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

<VirtualHost *:80>
    ServerAlias subdomain.example.com
    ProxyRequests off
    ProxyPass / http://127.0.0.1:8112/
    ProxyPassReverse / http://127.0.0.1:8112/
</VirtualHost>

Troubleshooting

Magnet Links Are Broken with Chromium

The following command should return "deluge.desktop":

$ xdg-mime query default "x-scheme-handler/magnet"

If it returns a null, run this command:

$ xdg-mime default deluge.desktop application/x-bittorrent x-scheme-handler/magnet

Reference: https://bugs.archlinux.org/task/28011

Downloads don't start

As of libtorrent-rasterbar version 0.16, Deluge will not download torrents that are added by a magnet link.

Downgrading libtorrent-rasterbar to 1:0.16.3-1 should fix it. Use the following PKGBUILD: https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/libtorrent-rasterbar&id=da6a845f1f66026c2e0df71e8728ab0d8fd660b0

Web UI doesn't store settings

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.

/srv/deluge/.config/deluge/core.conf
...
 "enc_prefer_rc4": true, 
 "listen_ports": [
   49160, 
   49249
 ], 
 "dht": false, 
 ...

Daemon won't start on fresh install

There seems to be an issue creating a folder with the correct permissions when the package installs, try:

# chmod u+x /srv/deluge