Troubleshooting
First be sure to download and install both .egg files from the latest release. Deluge will choose the correct one to use. If the install process still does not work, check deluge's plugin folder and place both .egg files there manually.
On windows the plugins folder can be found at: %APPDATA%\deluge\plugins
and on linux and OSX: ~/.config/deluge/plugins
A few things to check:
-
If you are running deluge in client/server or thin-client mode (classic mode is unchecked in the preferences) FileBot must be installed and accessible on the server machine.
-
Deluge may not have permission to access FileBot, ensure that filebot and deluge have the correct permissions. A quick way to check is to open a cmd terminal and type
filebot -version. If you do not get version info back, it is a good indicator that filebot.exe does not have the needed permissions. -
On Linux this message can show up if your install of FileBot is non-functional. Ensure FileBot can be run from the command line by typing
filebot -version. FileBot 4.5 and above requires the oracle-jre, and may throw an error if it is not found. Follow the instructions at this link to fix your FileBot installation: http://ubuntuhandbook.org/index.php/2015/07/install-filebot-4-6-ubuntu-15-10/ -
Synology users: there have been reports of trouble getting filebot to install and play nice with deluge using some default packages. You can try the steps that @ryancom16 used in issue #22:
Install Node JS v4 *might not be necessary
Use both synoCommunity and Filebot official syno packages
Make sure symlinks for Filebot and java are in usr/bin
Do a test with task scheduler, add a task as root, running every minute, Script is "filebot -version"
In the main scheduler window, Click Settings and enable output. Select a location and it will start printing logs there. You should get your customaryFileBot 4.7.7 (r4678) / OpenJDK Runtime Environment 1.8.0_101 / Linux 3.10.77 (amd64)
If this doesn't work, neither will the filebot plugin
This can sometimes happen when deluge doesn't have permission to modify the FileBot cache files. On linux they are located at ~/.filebot/cache. You should make sure the deluge user has full access to the entire .filebot configuration folder.
Depending on how FileBot and Deluge are installed, Deluge may not have access to the user profile where the license is installed. If you go to Preferences > FileBotTool there is a "Register FileBot" button that will allow you to chose your license file and activate FileBot on whatever user profile is running Deluge.
FileBot depreciated the revert script to instead use built-in functionality to handle reverts. Make sure you are on the newest version of filebot and that you are on the newest version of FileBotTool (at least version 1.2.6).