Details

Name: Deluge

Website: http://deluge-torrent.org

Added on: 10th of June 2014

Description

Bytesized's favorite torrent client.

Version management

Static version support. You get the option of choosing which version you want to install when you install the app. New versions are usually added within a week after release.

Changelog

23th of July 2014

This update moves away from the traditional 'move on completed' action. Deluge will now always download to torrents/data. This will help reseeding and cross-seeding ease of use.

21th of July 2014

FileBot now gets triggered even without assigning a label to it. It should ignore non-movies/tv content and only link the correct content.

19th of July 2014

Deluge has been switched to using FileBot to index/rename files by default now. To make content show up in Plex now just give it a movies or tv label. It will automatically be renamed to a Plex supported format after the download has been completed.

LabelPlus is disabled by default but if you enable it you can use it as before this App update.

13th March 2015

Updated guide to running two separate daemons on the same box.

Tips and tricks

Transdroid

Setting up Transdroid is fairly easy.

• Servertype: Deluge 1.2+
• IP/Domain: Your servername.bysh.me
• Username: Your lowercased username
• Password: Your deluge password
• Deluge Web Password: Your deluge password
• Advanced settings port-> Your deluge web port.

Make sure your web-interface is connected to the daemon or else Transdroid won't work.

Update Deluge App

If you wish to update Deluge App to the latest version (presently 1.3.12) you can do the following.

Open ~/.bysh_versions and edit the version from present version (1.3.x) to 1.3.12 then save the file. Next, from your boxes Account Details page, Stop the Deluge App and then Start the Deluge App. The app should now be updated. If you always want to be on the latest available version Bytesized offers you can also type in latest.

Disable auto-renaming (FileBot) of media

If you don't want your files analysed and renamed, extracted on download you can do the following.

Open ~/.config/deluge/filebot.py and look for the part that looks like:

scriptOptions = {
    'whitelist': []
 ..more stuff here
}

Change 'whitelist': [] to 'whitelist': ['tagged'].

Now Filebot will only analyse torrents that have the 'tagged' label assigned to them. Of course you can name the label anything you want.

Deluge & Plex with LabelPlus

This is a deprecated method. You can just use normal labels; "tv" and "movies" now to use the FileBot approach.

Deluge and Plex can also us the LabelPlus to help index files. The files won't be renamed so there is a decreased chance Plex will be able to pick it up with this method. First enable the LabelPlus plugin via settings then do the following.

• Add a torrent
• Right-mouse click on the torrent go to LabelPlus and select either Tv or Movies depending on your content.
  

• Plex will automatically pick up the torrent once it's done downloading.

Autolabels

It's also possible for LabelPlus to automatically set labels based on the name of torrent or the tracker.

This only works via the thin client however so make sure you configure the thin client and install the LabelPlus plugin locally.

Once that's done go to the LabelPlus tab and right-mouse one of your labels and select "Label Options".

Press the autolabel tab and select how you want to filter. For instance if you have a tracker that is called "canigetsomepopcorn" you can set it up like this to match all torrents from this tracker.

Of course there are more possibilities so play around with it :)

Multiple Deluge Daemons

While the awesome app installer handles a single instance of deluge flawlessly, there isn't an easy way for running another descrete instance of the deluged daemon. This can be done from SSH however.

Note: You'll only be able to start and stop this daemon from the command line. If you're not confortable with that, don't do it.

Step 1: duplicate config directory

First you'll need to create a copy of your ~/.config/deluge/ folder. Do this from a file manager or from ssh

cp -r ~/.config/deluge ~/.config/deluge2

Note: if you already have torrents in an instance of deluge which you do not wish duplicate on the second daemon, you'll want to remove them from the ~/.config/deluge/state directory. Again, use your file manager or from ssh

rm ~/.config/deluge2/state/*

Step 2: alter the listening ports for daemon and WebUI

Because we can't have 2 daemons listening on the same port, we have to change the port.

In your new config directory open ~/.config/deluge2/core.conf` and find

 "daemon_port": ####,

Change this number. Incriment it by 1, etc.

Next we'll change the WebUI port

locate web_port further down the core.conf file.

 "web_port": ####,

Do the same here, incriment by 1.

Step 4: Start deluged and tell it to look for this new directory

Now that we've made a new directory, deluged needs to know where to find it. Thakfully, the deveolpers have included a command line syntax just for this occasion. Start deluged this way:

deluged --config ~/.config/deluge2

Do this once, if you receive an error stating that there is already a daemon running using this config directory, first check you have targeted the correct file with the above command, then enter the following into the terminal.

killall deluged

then

deluged --config ~/.config/deluge2

and it should not present any errors.

NOTE - This would have also killed your primary deluge daemon, restart this as normal from the Bytesized Dashboard.

Step 5: Configure Auth File

Following this deluged will create a auth file in your .config/deluge folder, open it and it should read local client:(identifier key here):10. Leave this intact and on the second line insert your choice of username and password in the same format.

username:password:10

save the changes.

Using this Daemon

Connect to your new daemon the from the GUI or WebUI the same way as always, using the same address but with the new port no. and the username and password you defined in the auth file.

Profit.

Troubleshooting

I see download speeds of 100MB/s fall to sub 10MB/s and then going back up again.

Deluge uses it's own internal caching mechanism. Deluge handles this by first filling it's own internal cache, this is when you see 100MB/s. When it's cache is full it will stop requesting pieces from the swarm while it flushes it's cache to disk, this is when you will see speeds fall down. Once the cache has been flushed to disk it will start downloading again going back to the 100Mb/s.

rTorrent uses linux caching and doesn't have this 'problem'. However benchmarking shows that Deluge is still faster even with this weird quirk.

Browser Addons

Chrome

Remote Torrent Adder

You can configure Remote Torrent Adder in the following way:

Add Server

Give it a name - Example: Bytesized - Deluge

Select Deluge WebUI press Add

Host Example: "username.server.bytesized-hosting.com" (Do not include /deluge/ here)

Port - 80 - Leave SSL unchecked.

Username - Your username. Password - Your Deluge password.

Relative Path - Here you put /deluge

With this done, when you are browsing and if the plugin detects a torrent download link on a page, it will show the plugin icon in your address bar (green icon). If you click a .torrent download link, it should be automatically added to your deluge intsance.