Sonarr version (exact version): 2.0.0.4645 Mono version (if Sonarr is not running on Windows): 4.8.0 OS: Ubuntu Desktop 16.04 qBittorrent Version: 3.3.11 + 3.3.4alpha ( both tested ) ((Debug logs)): http://pastebin.com/WB6W1ata Description of issue: Sonnar succesfully grabs the epidoses and push them to qbittorrent but ignores the label that it is configured to use “Series” and after that it fails to monitor any progress of the download. When the download is finnished i have to manual move it to the Series folder and run the “rescan drone factory folder”.
The connection was refused, Firewall, qbit, something refused it so Sonarr thinks the grab failed and would never set the label (qbit forces Sonarr to set the label after the torrent is added unfortunately).
Drone Factory doesn’t rescan series folders and if you have drone factory pointed to the root folder for your TV shows you shouldn’t (hence the warning against that in the UI).
There is no firewall that can cause any problem here. Everything is running on on the same machine.
As for the “Series” folder let me explain. I don’t mean the folder where me series library exist. Qbittorrent can create download subfolders based on the name of the torrent label.
So it goes like this :
1 sonarr grabs and push the torrent to the Qbittorrent but fails to add the label
2 qbitorrent downloads the torrent and stays inactive
3 sonarr loses the connection and doesn’t know if the torrent is still downloading or is it finished
4 I manually put the label series on the torrent that as a result moves the downloaded content to the download subfolders with the name of the label. In our situation the folder name is Series
5 sonarr detects the content and send it to the library series folder.
Gotcha, that makes sense. Though you should avoid Drone Factory when it comes to torrents as it will move the file instead of copying/hard linking which would break seeding.
A for the actual error, the connection is being refused by something, it’s not something Sonarr is refusing, I’m not aware of qbit doing anything like that, but maybe the qbit logs show something.
We’ll also need more of the ((debug log)) file including the grab to see the whole process (not just the snippet with the error).