Deluge is a full-featured open source BitTorrent client. It uses libtorrent in its backend and features multiple user interfaces. It has been designed using the client server model. The Deluge daemon is able to run on the server and handle all bittorrent activity while user interfaces are able to connect remotely from any platform.
GTK+ "Thin Client"
The GTK+ user interface can be used as a thin client to connect with the daemon running on your Whatbox slot. It is the recommended way to control Deluge.
- Download version 1.3.15 and install Deluge. Versions 2.0 and above are not compatible at this time.
- Run Deluge
- Go to "Edit -> Preferences -> Interface" and untick "Enable" under "Classic Mode".
- Restart deluge. You should now see a connection manager box pop up.
- Remove the localhost daemon.
- Click "Add" and enter your server next to hostname:
- Enter the port your Deluge daemon is running on
(The port can be found on your Slot Info page)
- Enter your username and slot password
- Click "Add" to add your server's daemon.
- Click "Connect" and the connection manager pop up box should disappear.
Congratulations! You can now access deluge on your Whatbox slot via the GTK UI.
Tunnel the GTK+ Thin Client's Connection
All communication between the GTK UI and daemon is encrypted using an automatically generated self-signed certificate so SSH tunneling is not a requirement if you are on a trusted local network. If you access the daemon over the internet, you should still use a SSH tunnel.
- Follow the instructions for setting up an SSH Tunnel
- Create a new forwarded port. For Windows users using KiTTY (or PuTTY), the source port will be your daemon's port (check the "Info" page to get your daemon port). The destination will be
127.0.0.2:#####where ##### is your daemon port again. Unlike the SSH Tunneling wiki article, you will set this to be a local port forward, not dynamic. Lastly, make sure that the "Local ports accept connections from other hosts checkbox" is checked.
- Create a new connection in the thin client's connection manager. The only difference in the above instructions for the GTK+ Thin Client is that you will enter
127.0.0.2for the hostname rather than your server's hostname.
You will need to have the SSH tunnel active if you wish to connect to your remote daemon.
The Web user interface offers easy access to Deluge from a web browser. It is not recommended that you use this interface for large amounts of torrents.
Enable SSL (optional)
HTTPS for Deluge's WebUI is an either/or scenario; You can either solely access the WebUI through HTTP, or you can solely access it through HTTPS. To do this, you will be creating a self-signed certificate, so note that your web browser might say that the connection is untrusted.
- SSH into your slot.
- Create the self-signed certificate.
openssl req -new -x509 -nodes -out ~/.config/deluge/ssl/deluge.crt -keyout ~/.config/deluge/ssl/deluge.key -days 365
- Stop all running deluge processes.
killall deluged; killall deluge-web
- Open Deluge's WebUI configuration file in a text editor.
- Change the following lines:
- Save the configuration file. Ctrl+x if you used the nano text editor like above.
- Start the Deluge processes again, either from your Manage page, or in SSH:
deluged; deluge-web --forkRefresh the manage page and you will find the WebUI hyperlink to appropriately adjust for the usage of SSL.
The console user interface offers a convenient way to control Deluge over SSH. The deluge-console can be started by executing
deluge-console through SSH.
For more information, take a look at the full Deluge console documentation.
For installation instructions and more information take a look at the main article.
All the interfaces should provide a way to change Deluge's settings. If you want, you can edit the core settings file. It is located at
~/deluge/core.conf. Stop the "deluged" process before editing this file.