Not sure if something like this exists or not. I didn’t come across anything in my searches. And I’ve gotten completely sick of the constant .rar, .scr, .iso, etc junk/fake releases getting downloaded. So, I created my own app to put a stop to it. I know Sonarr is supposedly going to have this blocking ability built in on their next major release, but who knows when that’ll be available. So for the meantime…
It’s a super light-weight app that runs in a docker container.
Basically it works by Sonarr sending a webhook to the application when it starts a new download.
App receives the webhook.
App checks your torrent client for the download and reviews the file list in the torrent for blocked extensions.
If a blocked extension is found in the file list, it removes the torrent through Sonarr’s API, and optionally adds it to the Sonarr block list.
Takes a few minutes to get it running with docker.
I’ve only actually tested this on MacOS where I run Plex/Sonarr, and with qBittorrent. However I added support for Transmission and Deluge as well. BUT, like I said, untested. Also untested on Windows and Linux, but as it’s designed to run as a docker image, theoretically it should work just fine.
May I ask why you made it as an external software? Since sonarr already refuses to import and shows “unsupported file extension…” it seems like it should be possible to let sonarr automatically remove the download and search for another one when this happens. Any reason why my approach wouldn’t work?
At the moment Sonarr has no option to do anything with these downloads. They just sit there and refuse to import indefinitely until removed manually. From what I hear, in Sonarr v5 whenever it’s released, they will have something built in to address this problem. But for the time being, it requires some type of external tool to remove them. I’m not really trying to participate in development of Sonarr. Sure I could fork it and probably implement this feature pretty easily, but I doubt my changes would get approved back into the main branch.
I just got tired of dealing with them myself so did this as a little side project. Once v5 is released, it will become a useless tool.
The message was on hold because my account was new but I actually found an answer in the sonarr discord support channel. There is an advanced option, by indexer, to consider “failed” downloads where “potentially dangerous files” are detected. What’s not possible ATM is to customize the extensions, but it’s coming for v5.
Hopefully it will be a easy update to 5 from 4 whenever it drops. Hopefully there will be a import / export feature to import / export a list of ones shows. Hopefully the occasional issue of Sonarr grabbing much larger files then one has allowed for will be addressed.