Changes between Version 14 and Version 15 of UserGuide/ThinClient


Ignore:
Timestamp:
11/28/2011 03:39:35 PM (10 years ago)
Author:
Cas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserGuide/ThinClient

    v14 v15  
    33[[PageOutline(2-4,,inline)]] 
    44 
    5 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. 
    6 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. 
    7 In Deluge 1.2, all communication between the GTK UI and daemon is encrypted. 
     5Deluge can be setup in such a way that several machines (clients) can control deluge (daemon) on a central machine (server) through one of deluge's UI. 
     6For Deluge 1.2 upwards, all communication between the GTK UI and daemon is encrypted so SSH tunnelling is not a requirement.  
    87 
    98The server setup sections are written for a headless linux server although they could be adapted for other platforms. 
     
    1615=== Server Setup === 
    1716 
    18 ==== Without SSH Tunneling ==== 
    19  
    20  1. [wiki:Installing Install Deluge] on the server. 
    21  1. Run the deluge daemon: 
     17 1. [wiki:Installing Install Deluge] (including ''deluged'') on the server. 
     18 1. Run ''deluged'', the Deluge daemon: (You may wish to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an [UserGuide/InitScript InitScript]) 
    2219{{{ 
    2320#!sh 
    2421deluged 
    2522}}} 
    26  You may want to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an [UserGuide/InitScript InitScript]. 
    27  1. Run the Console UI: 
     23 1. Add a user and password to the authentication file (this does not have to be your server's user/pass): 
    2824{{{ 
    2925#!sh 
    30 deluge-console 
     26echo "username:password:level" >> ~/.config/deluge/auth 
    3127}}} 
    32  1. Enable remote connections: 
    33 {{{ 
    34 config -s allow_remote True 
    35 }}} 
    36  This allows other machines besides the localhost to be able to connect to the daemon using the GTK UI. 
    37  1. Double check it was set properly: 
    38 {{{ 
    39 config allow_remote 
    40 }}} 
    41  1. Exit the Console UI: 
    42 {{{ 
    43 exit 
    44 }}} 
    45  1. Shutdown the daemon: 
    46 {{{ 
    47 #!sh 
    48 killall deluged 
    49 }}} 
    50  1. Add yourself to the authentication file: 
    51 {{{ 
    52 #!sh 
    53 echo "yourusername:yourpassword:level" >> ~/.config/deluge/auth 
    54 }}} 
    55  where "yourusername" and "yourpassword" are the username and password you intend to use and "level" is your desired authentication level.  For example: 
     28 where "username" and "password" are the username and password you intend to use and "level" is your desired authentication level.  For example: 
    5629{{{ 
    5730#!sh 
     
    6134 See UserGuide/Authentication for more information on authentication levels. 
    6235 
    63  '''Note:''' the username and password can be anything - they do not necessarily have to be your server's username and password. 
     36==== Enable Remote Connection ==== 
    6437 
    65  1. Restart the daemon: 
     38We will use deluge-console to configure deluged to accept connections from machines other than localhost. 
     39 
     40'''Note:''' ''These steps can be omitted if you are using SSH Tunnelling.'' 
     41  
     42 1. Run the Console UI: 
    6643{{{ 
    6744#!sh 
     45deluge-console 
     46}}} 
     47 1. Enable remote connections and check it was set properly: 
     48{{{ 
     49config -s allow_remote True 
     50config allow_remote 
     51}}} 
     52 1. Exit the Console UI: 
     53{{{ 
     54exit 
     55}}} 
     56 
     57==== Restart Daemon ====  
     58 
     59{{{ 
     60#!sh 
     61pkill deluged 
    6862deluged 
    6963}}} 
    70  1. (Optional) If you do not know your server's private ip, run: 
     64 
     65==== Verify IP Addresses ==== 
     66 
     67You will need to know the server IP address for setting up the client(s). If you do not know your server's private or public IP address use these commands: 
     68 
     69 1. Private IP: 
    7170{{{ 
    7271#!sh 
    7372ifconfig | grep -e 'inet addr' | grep -v '127.0.0.1' | cut -f2 -d':' | cut -f1 -d' ' 
    7473}}} 
    75  You will need to know this for setting up the client(s). 
    7674 
    77 Congratulations! The server is now setup for GTK UI access. 
    78  
    79 ==== With SSH Tunneling ==== 
    80  
    81  1. [wiki:Installing Install Deluge] on the server. 
    82  1. Run the deluge daemon: 
    83 {{{ 
    84 #!sh 
    85 deluged 
    86 }}} 
    87  You may want to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an [UserGuide/InitScript InitScript]. 
    88  1. Add yourself to the authentication file: 
    89 {{{ 
    90 #!sh 
    91 echo "yourusername:yourpassword:level" >> ~/.config/deluge/auth 
    92 }}} 
    93  where "yourusername" and "yourpassword" are the username and password you intend to use and "level" is your desired authentication level.  For example: 
    94 {{{ 
    95 #!sh 
    96 echo "bob:letMEin:10" >> ~/.config/deluge/auth 
    97 }}} 
    98  
    99  
    100  See UserGuide/Authentication for more information on authentication levels. 
    101  
    102  '''Note:''' the username and password can be anything - they do not necessarily have to be your server's  username and password. 
    103  
    104  1. Restart the daemon: 
    105 {{{ 
    106 #!sh 
    107 deluged 
    108 }}} 
    109  1. (Optional) If you do not know your server's public ip, run: 
     75 1. Public IP: 
    11076{{{ 
    11177#!sh 
    11278curl ifconfig.me 
    11379}}} 
    114  You will need to know this for setting up the client(s). 
    11580 
    116 Congratulations! The server is now setup for GTK UI access using a SSH tunnel. 
     81Congratulations! The server is now setup for remote GTK UI access. 
    11782 
    11883=== Client Setup === 
    11984 
    120 ==== Without SSH Tunneling ==== 
    121  1. Run deluge. 
    122  1. Go to "Preferences -> Interface" and untick "Enable" under "Classic Mode". 
    123  1. Restart deluge. You should now see a connection manager box pop up. 
     85 1. Run ''deluge''. 
     86 1. Go to "Preferences -> Interface" and ''untick'' 'Classic Mode' to disable it. 
     87 1. Restart deluge. You should now see the Connection Manager pop up. 
    12488 1. Remove the localhost daemon. 
    125  1. Click "Add" and enter your server's ip. 
    126  1. Leave the port as default. 
    127  1. Enter the username & password you added to the authentication file. 
    128  1. Click "Add" to add your server's daemon. 
    129  You should now see a green tick as the status for the host you just added. 
    130  1. (Optional) Expand "Options" and select "Automatically connect to selected host on startup" and "Do not show this dialog on start-up". 
     89 1. Click "Add" and for 'Hostname' enter your server's IP. (For SSH Tunnelling use '127.0.0.2' and [UserGuide/ThinClient#CreateSSHTunnel Create SSH Tunnel] before continuing) 
     90 1. Leave the Port as default (58846). 
     91 1. Enter the Username & Password you added to the authentication file then finish by clicking 'Add'. 
     92 A green tick should now appear as the status for the host you just added. 
     93 1. ''(Optional)'' Expand "Options" and select "Automatically connect to selected host on startup" and "Do not show this dialog on start-up". 
    13194 1. Click "Connect" and the connection manager pop up box should disappear. 
    13295 
    13396Congratulations! You can now access deluge on the server via the GTK UI. 
    13497 
    135 ==== With SSH Tunneling ==== 
    136  1. Open up a terminal and enter 
     98==== Create SSH Tunnel ==== 
     99 1. Open up a terminal and enter the following, replacing <server> with the public IP of your server. 
    137100{{{ 
    138101#!sh 
    139102ssh -fNL 127.0.0.2:58846:localhost:58846 <server> 
    140103}}} 
    141  Where <server> is the public ip of your server. 
    142104 
    143  '''Note:''' We use 127.0.0.2 instead of localhost so that deluge realises that we are actually connecting to a remote daemon. 
     105 '''Note:''' We use 127.0.0.2 instead of localhost so that deluge client knows that we are connecting to a remote daemon. 
    144106 
    145107 '''Note:''' If you get the error: 
     
    152114sudo ifconfig lo0 add 127.0.0.2 
    153115}}} 
    154  1. Run deluge. 
    155  1. Go to "Preferences -> Interface" and untick "Enable" under "Classic Mode". 
    156  1. Restart deluge. You should now see a connection manager box pop up. 
    157  1. Remove the localhost daemon. 
    158  1. Click "Add" and enter "127.0.0.2". 
    159  1. Leave the port as default. 
    160  1. Enter the username & password you added to the authentication file. 
    161  1. Click "Add" to add your server's daemon. 
    162  You should now see a green tick as the status for the host you just added. 
    163  1. (Optional) Expand "Options" and select "Automatically connect to selected host on startup" and "Do not show this dialog on start-up". 
    164  1. Click "Connect" and the connection manager pop up box should disappear. 
    165116 
    166 Congratulations! You can now access deluge on the server via the GTK UI and SSH tunneling. 
    167117 
    168118== Web UI == 
     
    170120 
    171121 1. [wiki:Installing Install Deluge] on the server. 
    172  1. Run the deluge daemon: 
     122 1. Run the deluge daemon (You may want to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an [UserGuide/InitScript InitScript].): 
    173123{{{ 
    174124#!sh 
    175125deluged 
    176126}}} 
    177  You may want to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an [UserGuide/InitScript InitScript]. 
    178127 1. Run deluge Web UI: 
    179128{{{ 
     
    181130deluge-web 
    182131}}} 
    183  You can also use the --fork option to have the deluge-web process run in the background. 
     132 You can also use the --fork option to have the deluge-web process run in the background and again, you may want to use an [UserGuide/InitScript InitScript]. 
    184133{{{ 
    185134#!sh 
    186135deluge-web --fork 
    187136}}} 
    188  Again, you may want to use an [UserGuide/InitScript InitScript]. 
    189  1. (Optional) If you do not know your server's public ip, run: 
     137 
     138 1. ''(Optional)'' If you do not know your server's public ip, run: 
    190139{{{ 
    191140#!sh