Version 12 (modified by johnnyg, 12 years ago) (diff)

add note about adding 127.0.0.2 to loopback device (necessary for macs)

Thin Client

  1. GTK UI
    1. Server Setup
      1. Without SSH Tunneling
      2. With SSH Tunneling
    2. Client Setup
      1. Without SSH Tunneling
      2. With SSH Tunneling
  2. Web UI
    1. Server Setup
    2. Client Setup

Deluge can be setup in such a way that several machines (clients) can control deluge on a central machine (server) through one of deluge's UI. When the client is not on the same private network as the server, it is recommended that only the Web UI is used or that the GTK UI is used with SSH tunneling if you are using a version earlier than 1.2. In Deluge 1.2, all communication between the GTK UI and daemon is encrypted.

The server setup sections are written for a headless linux server although they could be adapted for other platforms. The client setup sections are platform independent.

Note: Both the client and the server need to be similar versions, i.e. both 1.2.x or both 1.3.x.

GTK UI

Server Setup

Without SSH Tunneling

  1. Install Deluge on the server.
  2. Run the deluge daemon: 
    deluged
    You may want to enable logging and/or use an InitScript.
  3. Run the Console UI: 
    deluge-console
  4. Enable remote connections: 
    config -s allow_remote True
    This allows other machines besides the localhost to be able to connect to the daemon using the GTK UI.
  5. Double check it was set properly: 
    config allow_remote
  6. Exit the Console UI: 
    exit
  7. Shutdown the daemon: 
    killall deluged
  8. Add yourself to the authentication file: 
    echo "yourusername:yourpassword:level" >> ~/.config/deluge/auth
    where "yourusername" and "yourpassword" are the username and password you intend to use and "level" is your desired authentication level. For example: 
    echo "bob:letMEin:10" >> ~/.config/deluge/auth

See UserGuide/Authentication for more information on authentication levels.

Note: the username and password can be anything - they do not necessarily have to be your server's username and password.

  1. Restart the daemon: 
    deluged
  2. (Optional) If you do not know your server's private ip, run: 
    ifconfig | grep -e 'inet addr' | grep -v '127.0.0.1' | cut -f2 -d':' | cut -f1 -d' '
    You will need to know this for setting up the client(s).

Congratulations! The server is now setup for GTK UI access.

With SSH Tunneling

  1. Install Deluge on the server.
  2. Run the deluge daemon: 
    deluged
    You may want to enable logging and/or use an InitScript.
  3. Add yourself to the authentication file: 
    echo "yourusername:yourpassword:level" >> ~/.config/deluge/auth
    where "yourusername" and "yourpassword" are the username and password you intend to use and "level" is your desired authentication level. For example: 
    echo "bob:letMEin:10" >> ~/.config/deluge/auth

See UserGuide/Authentication for more information on authentication levels.

Note: the username and password can be anything - they do not necessarily have to be your server's username and password.

  1. Restart the daemon: 
    deluged
  2. (Optional) If you do not know your server's public ip, run: 
    wget www.whatismyip.com/automation/n09230945.asp -O - 2> /dev/null && echo
    You will need to know this for setting up the client(s).

Congratulations! The server is now setup for GTK UI access using a SSH tunnel.

Client Setup

Without SSH Tunneling

  1. Run deluge.
  2. Go to "Preferences -> Interface" and untick "Enable" under "Classic Mode".
  3. Restart deluge. You should now see a connection manager box pop up.
  4. Remove the localhost daemon.
  5. Click "Add" and enter your server's ip.
  6. Leave the port as default.
  7. Enter the username & password you added to the authentication file.
  8. Click "Add" to add your server's daemon. You should now see a green tick as the status for the host you just added.
  9. (Optional) Expand "Options" and select "Automatically connect to selected host on startup" and "Do not show this dialog on start-up".
  10. Click "Connect" and the connection manager pop up box should disappear.

Congratulations! You can now access deluge on the server via the GTK UI.

With SSH Tunneling

  1. Open up a terminal and enter 
    ssh -fNL 127.0.0.2:58846:localhost:58846 <server>
    Where <server> is the public ip of your server.

Note: We use 127.0.0.2 instead of localhost so that deluge realises that we are actually connecting to a remote daemon.

Note: If you get the error: 

bind: Can't assign requested address

You need to add 127.0.0.2 as an alias for the loopback device: 

sudo ifconfig lo0 add 127.0.0.2
  1. Run deluge.
  2. Go to "Preferences -> Interface" and untick "Enable" under "Classic Mode".
  3. Restart deluge. You should now see a connection manager box pop up.
  4. Remove the localhost daemon.
  5. Click "Add" and enter "127.0.0.2".
  6. Leave the port as default.
  7. Enter the username & password you added to the authentication file.
  8. Click "Add" to add your server's daemon. You should now see a green tick as the status for the host you just added.
  9. (Optional) Expand "Options" and select "Automatically connect to selected host on startup" and "Do not show this dialog on start-up".
  10. Click "Connect" and the connection manager pop up box should disappear.

Congratulations! You can now access deluge on the server via the GTK UI and SSH tunneling.

Web UI

Server Setup

  1. Install Deluge on the server.
  2. Run the deluge daemon: 
    deluged
    You may want to enable logging and/or use an InitScript.
  3. Run deluge Web UI: 
    deluge-web
    You can also use the --fork option to have the deluge-web process run in the background. 
    deluge-web --fork
    Again, you may want to use an InitScript.
  4. (Optional) If you do not know your server's public ip, run: 
    wget www.whatismyip.com/automation/n09230945.asp -O - 2> /dev/null && echo

Congratulations! The server is now setup for web UI access.

Client Setup

  1. Open your preferred web browser.
  2. Open the URL: 
    http://<server>:8112
    where <server> is either the private or public ip of the server depending if you are on the server's private network or not.
  1. Default password is "deluge".

Congratulations! You can now access deluge on the server via the web UI.