Deluge
Changes between Version 21 and Version 22 of UserGuide/ThinClient
- Timestamp:
- 10/01/2014 10:45:18 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UserGuide/ThinClient
v21 v22 5 5 Deluge can be setup in such a way that a Deluge daemon, `deluged`, can be setup on a central computer, `server`, which can then be accessed and controlled by other computers, `clients`, using one of Deluge's UIs. 6 6 7 * From Deluge 1.2 onwards, all communication between the GTK UI and daemon is encrypted so SSH tunnelling is not a requirement.8 9 7 * Both the Deluge client and daemon need to be the same major versions, i.e. both `1.2.x` or both `1.3.x`. 10 11 * Windows users should append `.exe` to Deluge commands, e.g. `deluged.exe`, `deluge-console.exe`12 13 -------14 8 15 9 == Deluge Daemon Setup == 16 10 17 The Deluge daemon `deluged` should be installed on the central server that you want your other computers to connect to.11 The Deluge daemon `deluged` and `deluge-console` should be [wiki:Installing installed] on the server. 18 12 19 Follow the [wiki:Installing install] instructions to install `deluged` and `deluge-console` as a minimum on the server.13 See the [UserGuide/Service service guides] to run `deluged` as a service so that it starts/stops on server boot/shutdown. Substitute any daemon start or stop commands below with the appropriate service commands. 20 14 21 To run `deluged` as a service so that it starts/stops on server boot/shutdown, see these [UserGuide/InitScript guides]. Replace any daemon start or stop commands below with the appropriate service commands. 22 23 If you have problems setting up `deluged` [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and check for errors. 15 To debug any problems setting up `deluged` [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and check for errors. 24 16 25 17 === Create Default Config === 26 18 27 To create the config directory and populate with the default files, run and then stop `deluged` :19 To create the config directory and populate with the default files, run and then stop `deluged`, if using a service substitute appropriate commands: 28 20 {{{ 21 #!sh 29 22 deluged 30 pkill deluged23 killall deluged 31 24 }}} 32 25 26 ''Note: The config location is either the [wiki:Faq#WheredoesDelugestoreitssettingsconfig default location] with reference to the `user` that `deluged` is running as. Alternatively if using a service it will be specified in the service config files with `-c <path>` option.'' 33 27 34 28 === Add User to the authentication file === 35 29 36 The next step is to create a Deluge user for clients/UIs to access the daemon remotely by editing the authentication file, `auth`, located in your [wiki:Faq#WheredoesDelugestoreitssettingsconfig config directory]. 30 Create a Deluge user for clients/UIs to access the daemon by editing the authentication file, `auth`, located in the above config location. 37 31 38 The `auth` file should con tain lines with only '`<username>:<password>:<level>`', replacing `<username>` and `<password>` with your choice and `<level>`with the desired [UserGuide/Authentication authentication level].32 The `auth` file should consist of lines of `<username>:<password>:<level>`. Replace <username> and <password> with your choice and <level> with the desired [UserGuide/Authentication authentication level]. 39 33 40 34 You can use your favourite text editor to achieve this or can be done with a one-line echo command e.g.: … … 46 40 === Enable Remote Connection === 47 41 48 We will use `deluge-console` to configure `deluged` to accept connections from computers other than `localhost`. 42 We will use `deluge-console` to configure `deluged` to accept connections from computers other than `localhost`. For `SSH Tunnelling` you do not need to enable remote connections so this step can be skipped. 49 43 50 ''Note: For `SSH Tunnelling` you do not need to enable remote connections so this step can be skipped.'' 51 52 Run the Console UI in non-interactive mode to set then view the `allow_remote` option with these commands: 44 Using the Console in command-line mode, set the `allow_remote` option and then verify with these commands: 53 45 {{{ 54 46 #!sh … … 57 49 }}} 58 50 59 If you are running `deluged` under another user you will need to temporarily login as that user to enable deluge-console to access that daemon's config:51 If you are running `deluged` under another user (e.g. `deluge`) you will need to temporarily login as that user to enable deluge-console to access that daemon's config: 60 52 {{{ 53 #!sh 61 54 su --shell /bin/bash --login deluge 62 55 }}} 63 56 64 A s a last resort you can edit `core.conf` in the config and change "allow_remote" from `false` to `true`. Note that editing conf files can only be done with `deluged` stopped.57 Alternatively you can edit `core.conf` (`deluged` must not be running) in the config and change `allow_remote` from `false` to `true`. 65 58 66 === Start D aemon ===59 === Start Deluge Daemon === 67 60 68 61 {{{ 69 #!sh70 62 deluged 71 63 }}} 72 64 73 74 65 === Verify Server IP Address === 75 66 76 You will need to know the server's IP address for setting up the client(s). If you do not know your server's private or public IP address use these commands: 77 78 1. Private IP: 79 {{{ 80 #!sh 81 hostname -I 82 }}} 83 84 1. Public IP: 85 {{{ 86 #!sh 87 curl ifconfig.me 88 }}} 67 You will need to know the server's IP address for configuring clients, for private IP: `hostname -I` or public IP: `curl ifconfig.me` 89 68 90 69 Congratulations! The server is now setup for remote client access. … … 154 133 155 134 == Create SSH Tunnel == 156 Open up a terminal and enter the following, replacing `<server>` with the public IP of your server. 135 136 From Deluge 1.2 onwards, all communication between the GTK UI and daemon is encrypted so SSH tunnelling is not a requirement. 137 138 In a Terminal, enter the following, replacing `<server>` with the public IP of your server. 157 139 {{{ 158 140 #!sh 159 141 ssh -fNL 127.0.0.2:58846:localhost:58846 <server> 160 142 }}} 161 We use `127.0.0.2` instead of `localhost` so that Deluge client knows that we are connecting to a remote daemon. You will encounter problems otherwise with file browsing atit will assume to be on local client machine rather than remote server.143 Note: We use `127.0.0.2` instead of `localhost` so that Deluge client knows that we are connecting to a remote daemon. Otherwise you will encounter problems with file browsing as it will assume to be on local client machine rather than remote server. 162 144 163 145 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:
