-
Notifications
You must be signed in to change notification settings - Fork 0
- Is Deluge Free? Can I get the source?
- How to start the various user-interfaces
- Where does Deluge store its settings/config?
- Where does Deluge store the .torrent files?
- How do I reset the settings back to default?
- The files tab shows a different percentage-completed than the torrent
- What do all those numbers in parentheses mean?
- Seeding torrents have no queue position! Why?
- What bandwidth settings should I use?
- Deluge sometimes creates files that I didn't ask it to download?
- I lost data on force recheck?
- Does Deluge support Initial/Super Seed?
- Does Deluge have an embedded tracker?
- Does Deluge support multi-tracker torrents?
- What is the difference between full allocation and compact allocation?
- Selective downloading isn't working. How come?
- Which ports should I use?
- Deluge uses random ports instead of selected one, why?
- What does "Auto Managed" do?
- Does Deluge have an equivalent to "Force Start"?
- What is a magnet uri, and how do I get Deluge to handle them?
- What is Peer TOS Byte
- Can Deluge use blocklists such as SafePeer or PeerGuardian?
- I have a status bar warning: "No Incoming Connections!"
- Why is Deluge still listed in my task manager even after I close it?
- How do I start and stop the daemon?
- How do I start the daemon with logging enabled?
- I can't connect to the daemon from another machine
- How do I make Deluge connect to a different daemon?
- How do I stop Deluge from killing the daemon when I quit the GTK UI?
- How do I use https?
- Can I bind the webui to port :80 in Linux?
- How do I configure plugins with the WebUI?
- How do I auto-connect to a specific daemon?
- How do I install Deluge?
- Does Deluge have its own repository?
- How do I set Deluge as my default BitTorrent program?
- Deluge won't start! What should I do?
- Deluge won't start with a "ImportError: No module named pkg_resources" error.
- Deluge won't start with a "ImportError: No module named libtorrent" error.
- How do I find what libtorrent version I am using
- Deluge won't start with a “gobject.GError: Unrecognised image file format” error.
- Deluge's GTK UI won't connect to a remote daemon
- Deluge isn't working! What should I do?
- How do I add an already completed torrent to Deluge?
- Torrent stuck at 99% or some other point, even though seeders available
- Deluge doesn't start!
- Error: 14001 side-by-side configuration
- Samba Network Shares
- How can i change language in Deluge GUI for Windows
Yes, Deluge is Free Software, as defined by the Free Software Foundation, and is released under the GPL, giving our users complete freedom. The source code is available on the download section of our site. Our GPL nature allows you to be 100% sure that our program will never “spy” on your activities. Closed-source BitTorrent clients cannot make that same claim.
The main graphical interface. Can be started with either of the following:
deluge
deluge-gtk
The text-based interface, ideal for terminal use:
deluge-console
The console can be also run in a non-interactive manor to get direct output at the terminal:
deluge-console "info [[torrent]]"
Note: Requires the Deluge daemon, deluged, to be running.
The web interface enables access to Deluge from your browser. There are two ways to enable this interface:
- From the GTK UI you can enable the
WebUIplugin - If running the Deluge daemon the recommended method is to disable the plugin and run it standalone instead:
deluge-web
Point your browser to http://localhost:8112 and the default password is: deluge
The default location for the Deluge config is in the home directory of the current user.
- When running as a service the config is relative to the user specified in the service configuration
- The config location can be manually changed by using the
--configoption at startup
~/.config/deluge/
%APPDATA%\deluge\
Within the Deluge config directory in a directory named state.
If you don't care about losing your current torrents then delete everything in Deluge's config directory.
If you do want to keep your current torrents then delete everything except for the state folder.
The files tab will only show percentages based on completed pieces while the main view will show total completed including incomplete pieces.
| Field | # | (#) |
|---|---|---|
| Seeders | Number of connected seeders | Total number of seeders |
| Peers | Number of connected peers | Total number of peers |
| Downloaded | Total amount downloaded | Total amount downloaded this session |
| Uploaded | Total amount uploaded | Total amount uploaded this session |
Seeds use something called "seed rank" to determine which should be active and which should be queued. The seed rank is determined by the number of seed cycles a torrent has completed. Torrents with fewer completed seed cycles are prioritized for seeding. A seed cycle is completed when a torrent meets either the share ratio limit (uploaded bytes / downloaded bytes), the share time ratio (time seeding / time downloading) or seed time limit (time seeded).
Start with the following:
| Maximum Connections | 200 |
|---|---|
| Maximum Download Speed (Kib/s) | -1 |
| Maximum Upload Speed (Kib/s) | 80% of upload speed |
| Maximum Upload Slots | 4 |
| Maximum Half-Open Connections | 20 |
| Maximum Connection Attempts per Second | 20 |
If you're using Windows XP*:
| Maximum Half-Open Connections | 8 |
|---|
If you're using pre-SP2 Windows Vista*:
| Maximum Half-Open Connections | 4 |
|---|
You can then tweak those settings to suit your connection. See Bandwidth Tweaking.
Note: if you do not know your upload speed, go to http://speedtest.net and run a test. You can view the results in KB/s by choosing "kilobytes" for "Speed Measurement" which can be accessed under "Settings" in the top left corner of the page.
- If you have Deluge setup as a ThinClient then this setting is determined by the OS the daemon is running on, not the thin client.
Deluge handles files as pieces, not as individual files. This gets tricky, as sometimes the same piece is shared between consecutive files. So if you tell Deluge to download a file, it'll download all of the pieces within that file, and if one of those pieces is shared with another file, that file will also be created, although not necessarily entirely downloaded.
Note: Deluge can be run with experimental libtorrent from libtorrent_aio branch. In this case all pieces of not wanted files will be stored in one temporary file per torrent.
Force recheck discards all incomplete pieces.
Not yet, but it will be added in the future when libtorrent 0.15 is released.
No and it probably never will. We want to be the best BitTorrent client around, and to do that we need to focus on just being a client.
Yes it does. You can edit the trackers associated with a torrent by right-clicking on a torrent within Deluge, and clicking on “Edit Trackers.”
This conforms to the BitTorrent Multitracker specifications
Compact allocation only allocates as much storage as it needs to keep the pieces downloaded so far. This means that pieces will be moved around to be placed at their final position in the files while downloading (to make sure the completed download has all its pieces in the correct place). In full allocation, the entire space that a file needs is allocated as soon as one piece of that file is downloaded, thus decreasing fragmentation.
We suggest that our users use full allocation.
Deluge uses sparse files for full allocation, the compact allocation option is only useful on file systems that don't support sparse files (such as FAT or HFS+).
Selective downloading requires full allocation, check you are not using compact allocation. See above for details between the two.
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.
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.
Run netstat to check if the port is free.
An "auto managed" torrent, is a torrent managed by Deluge. This means that it obeys Deluge's queue settings. By disabling "auto managed", a torrent will become active (i.e. start downloading/uploading). It will still be be bound by the stop ratio though (see 'Stop seed at ratio' under the Queue section of the torrent's Options tab).
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.
Deluge has "auto managed" torrents which are similar, see above for details.
To make a torrent no longer "auto managed": 1. Select the torrent in question. 1. Select the options tab. 1. Unselect "Auto Managed".
Magnet URIs are an easy way to add torrents by their info-hash. You can learn more about them here
If you're using GNOME, then you can do these following commands to associate magnets with Deluge:
gconftool-2 -t string -s /desktop/gnome/url-handlers/magnet/command 'deluge "%s"'
gconftool-2 -t bool -s /desktop/gnome/url-handlers/magnet/needs_terminal false
gconftool-2 -t bool -s /desktop/gnome/url-handlers/magnet/enabled true
If you aren't using GNOME, but using Firefox 3.0 or earlier, you can set it up this way:
- Type about:config into the address bar and press Enter.
- Add a key by Right-click -> New -> Boolean -> Name: network.protocol-handler.external.magnet with value -> true
- Add another key, by Right-click -> New -> String -> Name: network.protocol-handler.app.magnet with Value -> deluge
- Ensure that the key network.protocol-handler.expose-all is set to true.
For Firefox 3.5+ use the same approach to create a boolean key network.protocol-handler.expose.magnet and set its value to False, you will be prompted to pick up a handler next time you attempt a magnet download.
In Windows, you can simply re-run the installer and select the magnet association option.
IPv4 Header Type Of Service Byte [(More Info)]
Example Settings:
tos-minimize-delay 0x10
tos-maximize-throughput 0x08
tos-maximize-reliability 0x04
tos-minimize-cost 0x02
tos-normal-service 0x00
Yes. Enable the Blocklist Plugin
You need to configure your router or firewall to allow (unblock) incoming torrent traffic for the network ports that Deluge uses.
Enabling UPnP in Deluge and on your router can automatically open the ports as needed.
$ deluge-console
>>> connect localhost 12345
You closed only the UI, but you did not close the daemon. Choose "Quit & Shutdown Daemon" to close both Daemon and GtkUI.
deluged
pkill deluged
Note: Deluge accepts the SIGTERM signal and cleanly shuts down.
Using the --do-not-daemonize (-d) option you can also log to console:
deluged -d [-L <loglevel>] [-l <logfile>]
See ThinClient for more information but the summary steps are:
1. Configure the daemon to allow remote connections 1. Configure Authentication 1. Restart the daemon.
By default, Deluge (GTK UI) is in classic mode, the daemon and GTK UI are linked together.
To disable classic mode:
1. Preferences -> Interface
1. Disable (untick) Classic Mode
1. Restart Deluge and it will now start in thin-client mode
- Use the Connection Manager to enter the other daemon details See ThinClient for more information on remote GTK UI
See above.
The default password for the web interface is 'deluge'. You should change this upon first login for security reasons.
In the Web UI:
- Click on "Preferences"
- Select the "Interface" category
- Fill out the fields under "Password"
- Click "Change"
Note: you need to stop the Web UI before you do any of the following.
If you have forgotten the password, you can reset it by deleting web.conf from Deluge's config directory.
Important: This will delete _all_ of your Web UI settings.
You can also reset it by using the following script (which does not delete your existing settings):
#!/usr/bin/env python
# Changes the password for Deluge's Web UI
from deluge.config import Config
import hashlib
import os.path
import sys
if len(sys.argv) == 2:
deluge_dir = os.path.expanduser(sys.argv[1])
if os.path.isdir(deluge_dir):
try:
config = Config("web.conf", config_dir=deluge_dir)
except IOError, e:
print "Can't open web ui config file: ", e
else:
password = raw_input("Enter new password: ")
s = hashlib.sha1()
s.update(config['pwd_salt'])
s.update(password)
config['pwd_sha1'] = s.hexdigest()
try:
config.save()
except IOError, e:
print "Couldn't save new password: ", e
else:
print "New password successfully set!"
else:
print "%s is not a directory!" % deluge_dir
else:
print "Usage: %s <deluge config dir>" % (os.path.basename(sys.argv[0]))1. Create (self-signed) ssl certificates: http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#selfcert
=== Linux ===
- Put
deluge.cert.pemanddeluge.key.pemin~/.config/deluge/ssl/
=== Windows ===
1. Put deluge.cert.pem and deluge.key.pem in %APPDATA%\deluge\ssl\
=== ALL ===
1. Enable https in the webui config. 1. Restart the webui
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:
- sudo apt-get install libcap2-bin
- sudo setcap 'cap_net_bind_service=+ep' /path/to/python
- Configure the WebUI to use port 80
- Restart
delugeddaemon.
Not all plugins are configurable directly with the WebUI right now. The easiest way to configure the plugins is to use the GTK UI. If you cannot install the GTK UI on the machine with your daemon, it is possible to connect to that daemon from another computer with the GTK UI. See ThinClient for more information on remote GTK UI.
- Stop the Web UI
- Edit
web.conf, find "default_daemon" and set its value to the daemonidinhostlist.confbr e.g. to connect to localhost you would open hostlist.conf as see a snippet like this:
...
"123459d5a5b414159caa1323f6e0c9b240c7abcd",
"localhost",
58846,
...
use the first entry, which is the id and add it to web.conf
"default_daemon": "123459d5a5b414159caa1323f6e0c9b240c7abcd",
- Restart the Web UI
There is an unofficial Ubuntu repository hosted at launchpad: More Info
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.
Sometimes Deluge's settings get corrupted and need to be reset. See: Reset Settings
You need to install setuptools.
You need to install libtorrent-rasterbar
The latest versions of Deluge include libtorrent version information in Help|About or with --version from the terminal.
Alternatively use python to import and query libtorrent:
python -c "from deluge._libtorrent import lt; print lt.version"
You need to install SVG support. On Debian/Ubuntu, the package is librsvg2-common.
Make sure both the GTK UI and the daemon are the same (or similar) versions.
Deluge 1.2 was a complete rewrite and hence is unable to connect to 1.1.x
Otherwise make sure you've followed the thin client userguide.
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).
This is currently not the case.
~~If you are on Windows, the debug logs are located in your [settings folder](#where-does-deluge-store-its-settingsconfig) under the names `deluged.log` and `deluge.log`.~~
If you are in Linux, see Enable Deluge Logging below
If you are pasting the log on the forums, please use the code!-code tags.
If you are pasting the log on IRC, please use dpaste or pastebin or something similar.
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.
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/
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'
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).
Make sure Visual C++ 2008 SP1 Redistributable Package (x86) is installed.
This error is solved by installing the Visual C++ 2008 SP1 Redistributable Package (x86)
In order for Deluge to use a Samba share from within Windows, the share has to be mapped to a drive letter.
There is a bug in the way GTK sets language on Windows but there are several workarounds:
-
Set the global LANG environment variable to the language you require.
-
Delete the following language files from Deluge program folder:
C:\Program Files\Deluge\deluge-1.3.x-py2.6.egg\deluge\i18nC:\Program Files\Deluge\share\locale -
Open notepad, type in:
set lang=en
start deluge.exe
}}}
Save the file as Deluge.cmd in the same folder as Deluge.exe. Create a shortcut to the .cmd file and use it to start Deluge.
To enable logging run Deluge from a terminal with the following options.
- These options apply to all Deluge applications:
deluged,deluge-gtk,deluge-web&deluge-console
deluge -L <loglevel>
deluge -L <loglevel> -l <logfile>
nonecriticalerrorwarninginfodebug
Note: debug is very verbose and with a lot of torrents log files will be MB's in size.