304 Exception calling RPC request: 'CorePlugin.uTorrentImport'

[laharah]

304 Exception calling RPC request: 'CorePlugin.uTorrentImport'

[Laharah]

Hmmm, I'm not familiar with running deluge on a synology box, but I'll see if I can help. From the looks of that stack trace, deluge can't find the plugin to load it correctly. My first instinct is that the wrong .egg version is installed. You'll be needing the uTorrentImport-x.x-py2.7.egg egg from the release page.

If you're sure you've got the correct egg I'm a bit stumped, since it doesn't seem that any of my code is getting called before the error. Is there anything interesting before the error in the log? There should be a block with lines like "Found plugin: __ __ at __", is utorrentimport in there?

For some reason, it seems the plugin isn't registered with the component manager, this should be happening automatically when the plugin is loaded.

[Laharah]

I've pushed an attempt at a fix here. With this at least we should at least be able to tell if the error is in the deluge installation or in the plugin.

Install those versions of the eggs and see if there's a log line that looks like [uTorrentImport] initialized successfully..., if there isn't we'll have to keep digging.

[houdini3009]

The beta does seem to resolve the error:

[INFO    ] 16:15:36 pluginmanagerbase:170 Plugin uTorrentImport disabled..
[INFO    ] 16:15:40 pluginmanagerbase:158 Plugin uTorrentImport enabled..

However, I still can't seem to access the web UI? Nothing shows up in the sidebar.

[Laharah]

Glad that first error is fixed, really weird.

Unfortunately, the plugin doesn't have a web UI. You'll have to use deluge in thin client mode if your synology is running deluge headlessly. There are instructions how to do that here:

http://dev.deluge-torrent.org/wiki/UserGuide/ThinClient

Keep in mind, the plugin will import your uTorrent files from the same machine where the "deluged" server is running, not necessarily the machine where you're running the client.