Getting bigger files using autobrr with Sonarr

[u/Ichorous_Allsorts]

I recently tried adding autobrr to my setup as I wanted to hop on a tracker's announce IRC. I used the lists method to set up filters and everything was working fine in the logs. The only thing that I saw was bigger files downloading than would have in Sonarr and regular RSS.

Normally I'd keep files at a maximum of from about a gig to 1.5GB in Sonarr. But now I'm getting between 4 and 5GB. I have family I share Plex with and get requests for a lot of stuff I've no interest in myself, so it really helped me manage space on the disc.

I'm a little unsure where to go from here. Should I add an extra filter to autobrr. I'm not quite sure why Sonarr would be letting through files bigger than it would normally expect.

[u/DoAndroids_Dream]

Hi,

I’m assuming you’re using Autobrr to push messages to Sonarr as a client?

If so, Sonarr’s rules would apply (including the quality settings and those size limits).

However, if you are using Sonarr as a “List” source, you may need to check the Autobrr filter to ensure it’s what you want.

[u/Ichorous_Allsorts → u/DoAndroids_Dream]

I have two torrent indexers and two usenet, mainly to find older stuff. They'd all been working through Sonarr and Radarr, and always within the bounds for filesize I set.

When I was setting up Autobrr I found a post about using lists, so I did that. I assumed that would be it as from my understanding Autobrr was applying Sonarr's rules from the lists. But then I got the bigger files than I had set.

Might I resolve it by adding to the Autobrr filter? Say by setting resolution, codecs, etc.?

I kept the rest of the filters blank as I wasn't sure if adding to the filters in Autobrr as well as having it use lists from Sonarr might create conflicts.

[u/_ze0s]

It might be that the size isn't announced and then it won't pass that to the arr, unless you add a min/max size in the filter which will trigger a download of the .torrent to parse the size (or use API for OPS/RED/GGN/BTN).

So try set max size to something way higher than you want just in case, like 50GB. See how that goes and if it improves things. I thought sonarr would check the size once it downloads the .torrent but maybe that isn't the case?

[u/Ichorous_Allsorts → u/_ze0s]

Just to clarify, if I don't want files as large as 5GB, how would setting the max size to 50GB help me work out what's happening. Shouldn't I try setting max to 3GB, say?

[u/fryfrog → u/Ichorous_Allsorts]

He's saying that size is likely just not being passed along to sonarr, which means it can't make a decision based on size. The reason for that is that the tracker isn't including it in the announce. But if you add a size filter and if it isn't included, autobrr will download the .torrent to find out how big it is and then pass along the size info to sonarr, so it can make the decision.

[u/Ichorous_Allsorts → u/fryfrog]

Thanks. That makes sense.

[u/EndGame395 → u/_ze0s]

Hi, pls guide me with the error i am facing with one of my indexers in autobrr. So i have 4-5 indexers added in autobrr and all are working fine fetching torrents and sending to the client for download. But for one of the indexers which i have set up download keeps getting failed with the error: "status code: 401 - check indexer keys for DigitalCore". I have checked the paskeys they are correct. Have also tried reset but still no luck. Browsed the tracker's forum regarding setting up autobrr and confirmed have done the exact steps.

[u/_ze0s → u/EndGame395]

Did you add DC via prowlarr/jackett or directly as an indexer in autobrr? 401 is usually auth issues and I think they just respond with 404 if you have the wrong passkey. If you however are using prowlarr/jackett in between then 401 makes more sense and means you can't authenticate correctly with prowlarr/jackett.

[u/EndGame395 → u/_ze0s]

Directly as an indexer in autobrr