Sonarr and Radarr keep grabbing releases from a couple specific groups ( ‘SuccessfulCrab’ and ‘ELiTE’) for items that clearly haven’t even aired yet. These almost always contain only .scr or .lnk files, which have been blocklisted in my torrent client. This leaves Sonarr/Radarr awaiting manual intervention for ‘complete’ downloads that contain no files.

How do I get them to block anything and everything that contain the strings ‘SuccessfulCrab’ and ‘ELiTE’ ??? I want them to stop even trying to grab anything released by those two groups.

I’m so sick of dealing with these.


[EDIT]

OK, so I have been looking at this from the wrong angle.

It is not these groups that I’m upset with, but malware uploaders masquerading as release groups. These names can and will change, making this a game of wack-a-mole if I try to fight it this way.

Initially I’d followed instructions below to block these names/strings being grabbed by the arrs and that does work fantastically; but as above, wack-a-mole. Plus both SuccessfulCrab and ELiTE have plenty of good releases out there, it’s not their fault someone’s using their names.

So, I’m now running Cleanuparr.

This will maintain a large list of unwanted filetypes in qbittorrent. Then when qbit marks a torrent as complete because there are no wanted files, cleanupparr removes it from both qbit and the arr that requested it, while also triggering a new search for the item.

It can also cleanup items failing to import, stalled downloads, torrents stuck downloading metedata, or things that are just absurdly slow; with varying time scales/stringency.

I’ll run this for a bit and see how it goes.

  • Zozano@aussie.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 day ago

    I made this exact post on Github lol.

    The takeaway is this: Sonarr/Radarr v5 will solve this by setting the airtime, and restricting torrent grabs before that. There may also be a manual offset override (hours).

    I still think the easier solution is to set the indexer to manually choose what qualifies as a dangerous file type.

    • Darkassassin07@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      That will solve part of the problem, preventing downloads before an item has even released; but there’s still lots of potential to grab unwanted torrents and leave the arrs asking for intervention when they can’t import it.

      Ideally the indexers would be filtering out this junk before users can even grab them, but failing that I think we’ve got a decent solution. Check out the edited OP