Changes between Version 151 and Version 152 of Faq
- Timestamp:
- 05/25/2013 07:01:43 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Faq
v151 v152 14 14 == How to start the various user-interfaces == 15 15 16 Gtk: 16 === Gtk UI === 17 18 The main graphical interface. Can be started with either of the following: 17 19 {{{ 18 20 deluge 19 21 }}} 20 ''or''21 22 {{{ 22 23 deluge-gtk 23 24 }}} 24 Console: 25 25 26 === Console UI === 27 28 The text-based interface, ideal for terminal use: 26 29 {{{ 27 30 deluge-console 28 31 }}} 29 32 30 Web: 33 The console can be also run in a non-interactive manor to get direct output at the terminal: 34 {{{ 35 deluge-console "info [torrent]" 36 }}} 37 38 ''Note: Requires the Deluge daemon, `deluged`, to be running.'' 39 40 41 === Web UI === 42 43 The web interface enables access to Deluge from your browser. There are two ways to enable this interface: 44 45 1. From the GTK UI you can enable the `WebUI` plugin 46 1. If running the Deluge daemon the recommended method is to disable the plugin and run it standalone instead: 31 47 32 48 {{{ … … 34 50 }}} 35 51 36 From your browser go to http://localhost:8112/ default-password = "deluge" 52 Point your browser to `http://localhost:8112` and the default password is: `deluge` 37 53 38 54 == Where does Deluge store its settings/config? == 39 55 40 === Linux === 56 The default location for the Deluge config is in the `home` directory of the current user. 57 58 * ''When running as a service the config is relative to the user specified in the service configuration'' 59 * ''The config location can be manually changed by using the `--config` option at startup'' 60 61 === Linux (Mac OSX) === 41 62 42 63 {{{ … … 50 71 }}} 51 72 73 52 74 == Where does Deluge store the .torrent files? == 53 75 54 In a directory named '''`state`''' located within the Deluge config directory outlined above.76 Within the Deluge config directory in a directory named '''`state`'''. 55 77 56 78 == How do I reset the settings back to default? == 57 79 58 If you don't care about losing your current torrents then delete everything in Deluge's settings folder (see above for location).59 60 If you do want to keep your current torrents then delete everything except for the statefolder.80 If you don't care about losing your current torrents then delete everything in Deluge's config directory. 81 82 If you do want to keep your current torrents then delete everything except for the `state` folder. 61 83 62 84 ---- … … 140 162 == Which ports should I use? == 141 163 142 The official ports for Bittorrent are 6881-6889, but most ISPs block or at least throttle those ports, so users are encouraged to use a port range of something between 49152 and 65535.164 The official ports for Bittorrent are `6881-6889`, but most ISPs block or at least throttle those ports, so users are encouraged to use a port range of something between `49152` and `65535`. 143 165 144 166 == Deluge uses random ports instead of selected one, why? == 145 167 146 Click Apply after changing the port. Deluge will pick a random port if the chosen port is not available. 147 148 Run "netstat"to check if the port is free.168 You will need to click OK or Apply in Preferences after changing the port however Deluge will pick a random port if the chosen port is not available. 169 170 Run `netstat` to check if the port is free. 149 171 150 172 == What does "Auto Managed" do? == 151 173 152 An "auto managed" torrent, is a torrent managed by deluge.153 This means that it obeys deluge's queue settings.174 An "auto managed" torrent, is a torrent managed by Deluge. 175 This means that it obeys Deluge's queue settings. 154 176 By disabling "auto managed", a torrent will become active (i.e. start downloading/uploading). 155 177 It will still be be bound by the stop ratio though. 156 178 157 Note: All active torrents (including those not "auto managed") are counted in the total active queue settings. This means that if the total number of active torrents ("auto managed" and not) exceed the limit for total active torrents in the queue settings, deluge will automatically queue any "auto managed" torrents until the limit is no longer exceeded.179 Note: All active torrents (including those not "auto managed") are counted in the total active queue settings. This means that if the total number of active torrents ("auto managed" and not) exceed the limit for total active torrents in the queue settings, Deluge will automatically queue any "auto managed" torrents until the limit is no longer exceeded. 158 180 159 181 == Does Deluge have an equivalent to "Force Start"? == … … 209 231 You need to configure your router or firewall to allow (unblock) incoming torrent traffic for the network ports that Deluge uses. 210 232 211 Enabling uPnPin Deluge and on your router can automatically open the ports as needed.233 Enabling `UPnP` in Deluge and on your router can automatically open the ports as needed. 212 234 213 235 ---- … … 217 239 218 240 {{{ 219 $ deluge -uconsole241 $ deluge-console 220 242 >>> connect localhost 12345 221 243 }}} … … 224 246 = Daemon = 225 247 226 == Why is deluge still listed in my task manager even after I close it? ==248 == Why is Deluge still listed in my task manager even after I close it? == 227 249 228 250 You closed only the UI, but you did not close the daemon. 229 251 Choose "Quit & Shutdown Daemon" to close both Daemon and GtkUI. 230 252 231 == How do I only startthe daemon? ==253 == How do I start and stop the daemon? == 232 254 233 255 {{{ 234 256 deluged 235 257 }}} 258 {{{ 259 pkill deluged 260 }}} 261 262 ''Note: Deluge accepts the `SIGTERM` signal and cleanly shuts down.'' 236 263 237 264 == How do I start the daemon with logging enabled? == 238 265 239 === Logging to console === 240 241 {{{ 242 deluged -d 243 }}} 244 245 ==== With debug info ==== 246 247 {{{ 248 deluged -d -L debug 249 }}} 250 251 === Logging to file === 252 253 {{{ 254 deluged -l <logfile> 255 }}} 256 257 ==== With debug info ==== 258 259 {{{ 260 deluged -L debug -l <logfile> 261 }}} 262 263 264 == How do I stop the daemon? == 265 266 {{{ 267 killall deluged 268 }}} 269 270 Deluge accepts the SIGTERM signal and cleanly shuts down. 266 See: [wiki:Faq#EnableDelugeLogging] 267 268 Using the `--do-not-daemonize` (`-d`) option you can also log to console: 269 270 {{{ 271 deluged -d [-L <loglevel>] [-l <logfile>] 272 }}} 271 273 272 274 == I can't connect to the daemon from another machine == 275 276 See [wiki:UserGuide/ThinClient ThinClient] for more information but the summary steps are: 273 277 274 278 1. Configure the daemon to allow remote connections … … 276 280 1. Restart the daemon. 277 281 282 == How do I make Deluge connect to a different daemon? == 283 284 By default, Deluge (GTK UI) is in classic mode, the daemon and GTK UI are linked together. 285 To disable classic mode: 286 1. `Preferences` -> `Interface` 287 1. Disable (untick) `Classic Mode` 288 1. Restart Deluge and it will now start in thin-client mode 289 1. Use the Connection Manager to enter the other daemon details 278 290 See [wiki:UserGuide/ThinClient ThinClient] for more information on remote GTK UI 279 291 280 == How do I make deluge connect to a different daemon? == 281 282 By default, deluge is in classic mode: the daemon and gtk ui are linked together. 283 To disable classic mode: 284 1. "Preferences" 285 1. "Interface" 286 1. Untick "Enable" under "Classic Mode". 287 1. Restart deluge. 288 See [wiki:UserGuide/ThinClient ThinClient] for more information on remote GTK UI 289 290 == How do I stop deluge from killing the daemon when I quit the GTK UI? == 292 == How do I stop Deluge from killing the daemon when I quit the GTK UI? == 291 293 292 294 See above. … … 297 299 == What is the default password == 298 300 299 The default password for the web interface is "deluge". You should change this upon first login for security reasons.301 The default password for the web interface is `'deluge'`. You should change this upon first login for security reasons. 300 302 301 303 == How do I change the password? == … … 310 312 '''Note:''' you need to stop the Web UI before you do any of the following. 311 313 312 If you have forgotten the password, you can reset it by deleting web.conf from deluge's config directory (see http://dev.deluge-torrent.org/wiki/Faq#WheredoesDelugestoreitssettingsconfig if you do not know where this is).314 If you have forgotten the password, you can reset it by deleting web.conf from Deluge's config directory. 313 315 314 316 '''Important:''' This will delete '''''all''''' of your Web UI settings. … … 358 360 === Linux === 359 361 360 1. Put deluge.cert.pem and deluge.key.pem in ~/.config/deluge/ssl/362 1. Put `deluge.cert.pem` and `deluge.key.pem` in `~/.config/deluge/ssl/` 361 363 362 364 === Windows === 363 365 364 1. Put deluge.cert.pem and deluge.key.pem in %APPDATA%\deluge\ssl\366 1. Put `deluge.cert.pem` and `deluge.key.pem` in `%APPDATA%\deluge\ssl\` 365 367 366 368 === ALL === … … 370 372 371 373 == Can I bind the webui to port :80 in Linux? == 372 You cannot bind to anything under 1024 in linux, however if you have kernel 2.6.24 or higher, you can use capabilities to allow python to bind to port 80 securely. In debian/ubuntu:374 You cannot bind to anything under 1024 in Linux, however if you have kernel 2.6.24 or higher, you can use capabilities to allow python to bind to port 80 securely. In debian/ubuntu: 373 375 374 376 1. sudo apt-get install libcap2-bin 375 377 1. sudo setcap 'cap_net_bind_service=+ep' /path/to/python 376 378 1. Configure the WebUI to use port 80 377 1. Restart delugeddaemon.379 1. Restart `deluged` daemon. 378 380 379 381 == How do I configure plugins with the WebUI? == … … 403 405 == How do I set Deluge as my default !BitTorrent program? == 404 406 405 On Windows, the installer should do this automatically. On Linux/Unix (GNOME), right-click on a torrent file, click on properties, click on the "open with" tab. Is deluge listed there? If so, select it to be your default, if not, click on "add", then click on "use custom command". Insert /usr/bin/delugeand click add.407 On Windows, the installer should do this automatically. On Linux/Unix (GNOME), right-click on a torrent file, click on properties, click on the "open with" tab. Is Deluge listed there? If so, select it to be your default, if not, click on "add", then click on "use custom command". Insert `/usr/bin/deluge` and click add. 406 408 407 409 ---- … … 411 413 == Deluge won't start! What should I do? == 412 414 413 Sometimes deluge's settings get corrupted and need to be reset. See: [wiki:Faq#HowdoIrestoreallsettingstodefault Reset Settings]415 Sometimes Deluge's settings get corrupted and need to be reset. See: [wiki:Faq#HowdoIrestoreallsettingstodefault Reset Settings] 414 416 415 417 == Deluge won't start with a "!ImportError: No module named pkg_resources" error. == … … 446 448 == Deluge isn't working! What should I do? == 447 449 448 The best thing is to provide us with a debug log of deluged and/or deluge(depending if the error is related to the daemon and/or to a UI).450 The best thing is to provide us with a debug log of `deluged` and/or `deluge` (depending if the error is related to the daemon and/or to a UI). 449 451 450 452 {{{ 451 453 #!comment 452 454 This is currently not the case. 453 ~~If you are on Windows, the debug logs are located in your [wiki:Faq#WheredoesDelugestoreitssettings settings folder] under the names "deluged.log" and "deluge.log".~~455 ~~If you are on Windows, the debug logs are located in your [wiki:Faq#WheredoesDelugestoreitssettings settings folder] under the names `deluged.log` and `deluge.log`.~~ 454 456 }}} 455 457 If you are in Linux, see [wiki:Faq#EnableDelugeLogging Enable Deluge Logging] below … … 459 461 If you are pasting the log on IRC, please use [http://dpaste.com dpaste] or [http://pastebin.com pastebin] or something similar. 460 462 461 == How do I add an already completed torrent to deluge? ==462 463 If you add an already completed torrent to deluge, you just need to set 'download location' to the path where your data is, and deluge will continue downloading/seeding the torrent.463 == How do I add an already completed torrent to Deluge? == 464 465 If you add an already completed torrent to Deluge, you just need to set `Download Location` to the path where your data is, and Deluge will continue downloading/seeding the torrent. 464 466 465 467 A common error occurs if your torrent contained a folder. If your torrent contained a folder called Torrent.Name.2010, such that the data was in ~/downloads/Torrent.Name.2010/ You need to set the download location to ~/downloads/ '''not''' ~/downloads/Torrent.Name.2010/ 466 468 467 If you have already added the torrent to deluge, you can pause it, select 'Move Storage', point it to your data, then choose 'Force Re-check'469 If you have already added the torrent to Deluge, you can pause it, select 'Move Storage', point it to your data, then choose 'Force Re-check' 468 470 469 471 == Torrent stuck at 99% or some other point, even though seeders available == 470 472 471 Check that local machine firewall or router is not detecting a SYN flood and blocking packets. As a torrent reaches completion and you become a seeder, there can be a sudden inrush of connections from other peers that causes firewalls to start blocking. If so, try reducing the total connections allowed in deluge, or increasing the tolerance on the router, or turning off SYN flood detection. Also check local storage for the downloaded file is not out of space (shown on bottom status bar in Deluge UI).473 Check that local machine firewall or router is not detecting a SYN flood and blocking packets. As a torrent reaches completion and you become a seeder, there can be a sudden inrush of connections from other peers that causes firewalls to start blocking. If so, try reducing the total connections allowed in Deluge, or increasing the tolerance on the router, or turning off SYN flood detection. Also check local storage for the downloaded file is not out of space (shown on bottom status bar in Deluge UI). 472 474 473 475 ---- … … 477 479 == Deluge doesn't start! == 478 480 479 This is usually caused by a crufty GTK installation. This can be solved as follows: 480 481 * Uninstall the GTK2 Runtime 482 * Delete the C:\Program Files\GTK2-Runtime directory (or where ever it was installed) 483 * Reinstall GTK+ 484 485 Reinstall GTK by simply re-running the Deluge installer and selecting that option or download latest from our [http://download.deluge-torrent.org/windows/deps mirror] 481 Make sure [http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Visual C++ 2008 SP1 Redistributable Package (x86)] is installed. 486 482 487 483 == Error: 14001 side-by-side configuration == … … 511 507 512 508 = Enable Deluge Logging = 513 To enable logging run deluge from a shell with the following options. 514 These also apply to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled deluged], deluge-gtk, deluge-web & deluge-console 509 To enable logging run Deluge from a terminal with the following options. 510 511 * These options apply to all Deluge applications: `deluged`, `deluge-gtk`, `deluge-web` & `deluge-console` 515 512 516 513 === Logging to shell === … … 524 521 525 522 === Available Log levels === 526 ''none'', ''critical'', ''error'', ''warning'', ''info'', ''debug'' 523 * `none` 524 * `critical` 525 * `error` 526 * `warning` 527 * `info` 528 * `debug` 529 530 Note: `debug` is ''very'' verbose and with a lot of torrents log files will be MB's in size.