Make sure the deluge daemon is running locally.

I'm not home right now, so I'm not able to be too much of a help at the moment.

It kind of sounds like an input sanitization problem, but you never know. I'm any of the devs would have come to the conclusion at a glance, or know more than I...

Some torrents don't work... Maybe you can give a few examples so that it's possible to get any sort of underztandingaof the problem?

Do you have logs you can post?

johnnyg wrote:Yes as long as you also provide different config directories (using -c).

You'll also need to make sure any network ports they use are not the same, e.g. webui listen port and daemon listen port.

Dmitry wrote:Is it possible? and how can I do that?

Run another instance of Deluge in a VM.

Put that command in a script and make sure it is executable by the user who is running the daemon. Put the full path to that file in the executable plugin. Make sure you have a valid/proper shebang. I've never had success just giving the plugins command, I'm pretty sure it expects a full path to an ...

Run this script from your .config/deluge/state directory and it will copy all of the torrent files into ~/renamedtorrents with the name they have in deluge. Make sure to mkdir ~/renamedtorrents first #!/usr/bin/python import shutil import os from deluge.ui.client import client from twisted.internet ...

chrisbay90 wrote:Please forgive my ignorance, but what is DDL in this context?

"Direct download" e.g. file hosters which require captcha, and some other hoops for a client to jump through to download.

If you add HTTP, some people might not find it useful without DDL support... at that point you may as well have a DDL solution with a deluge client integrated...

Restart the daemon, ensure the configuration is still applied, and see if the script still does not execute.