Sonarr version (exact version): 4.0.15.2941 Mono version (if Sonarr is not running on Windows): OS: Unraid docker Debug logs: Description of issue: I have added iso and .iso to “Must Not Contain” in the Profiles section but Sonarr still grabs iso files.
Also tried adding these file extensions to my download client with no results. The files will get downloaded and then Sonarr will fail to import them with an error that they are not valid. Is there some solution for this? The only postings I have found all say to add the iso extension to “Must Not Contain” but that doesn’t work.
If your download client has a blacklist, add *.iso to that. That’s the only way to prevent the files being downloaded (Sonarr can’t see the filenames until the files are downloaded). It doesn’t stop Sonarr trying (and failing) to import them, but you can install Cleanuparr and set it up to automatically remove the failed imports from the queue.
As long as the files are enclosed in a folder, you won’t be able to blacklist them. Only when they are not enclosed in a folder will blacklist work …
cc: olliebean
If it works, them why hasn’t it been incorporated in Sonarr? (@markus101) - my understanding is that it ‘may’ not download the torrent but it will seed it which defeats the ultimate goal.
I use qbittorrent as well but get probably a dozen iso files every week that I’ll have to blacklist and start a new search in Sonarr. You can see in the screenshot above that *.iso is set in the excluded window.
I ended up adding cleanuparr since I am using a seedbox with an older version of qbittorrent that doesn’t have blacklisting. This won’t stop it from downloading initially, but it will eventually remove and blacklist it when the import fails.
Must Not Contain applies to the release name, if the release name doesn’t contain .iso then it won’t make a difference.
There will be changes in v5 to prevent downloading before release, which will help in most cases, but ultimately poor quality indexers result in these sorts of issues.
We do not have plans to add file level blocking within downloads, like is being done with blocking at the the client level. There are just too complications for Sonarr to do it in every supported client. Blocking at the client level introduces a different issue and prevents Sonarr from processing the download at all, which is why you see recommendations to use Cleaneruparr or similar tools. Sonarr can address malicious files, but only does so after downloading when processing the download and that does not extend to .iso files, at least at this time.
If the file isn’t downloaded it’s not actually seeding anything, though you may be “seeding” a torrent and providing no files.
