Rarbg index returns results only sporadically

[hydriniumh2]

Is there an existing issue for this?

• I have searched the existing open and closed issues

Current Behavior

Hi,
I'm currently running prowlarr in a docker container and have been running into a Rarbg issue.
I'm only getting results from Rarbg every 10th search or so. It's difficult to provide proof because it's a sporadic issue, but I've checked the debug logs and there are no log messages which mention rate limiting at all, so I don't think this is due to the rate limiting.

If I search Rarbg it will return 0 results about 9/10 times, then suddenly it will work once and afterwards not work.

2023-01-31 18:24:36.4|Debug|Api|[GET] /api/v1/search?query=Velma&indexerIds=10&categories=5000&categories=5010&categories=5020&categories=5030&categories=5040&categories=5045&categories=5050&categories=5060&categories=5070&categories=5080&type=search&limit=100&offset=200: 200.OK (292 ms)
2023-01-31 18:24:53.3|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated.
2023-01-31 18:24:53.4|Info|ReleaseSearchService|Searching indexer(s): [Rarbg] for Term: [Velma], Offset: 0, Limit: 100, Categories: [5000, 5010, 5020, 5030, 5040, 5045, 5050, 5060, 5070, 5080]
2023-01-31 18:24:53.4|Debug|Rarbg|Downloading Feed https://torrentapi.org/pubapi_v2.php?mode=search&search_string=Velma&ranked=0&category=18%3B41%3B49&limit=100&token=(removed)&format=json_extended&app_id=Prowlarr
2023-01-31 18:24:53.6|Debug|ReleaseSearchService|Total of 0 reports were found for Term: [Velma], Offset: 0, Limit: 100, Categories: [5000, 5010, 5020, 5030, 5040, 5045, 5050, 5060, 5070, 5080] from 1 indexer(s)
2023-01-31 18:24:53.6|Debug|Api|[GET] /api/v1/search?query=Velma&indexerIds=10&categories=5000&categories=5010&categories=5020&categories=5030&categories=5040&categories=5045&categories=5050&categories=5060&categories=5070&categories=5080&type=search&limit=100&offset=0: 200.OK (282 ms)
2023-01-31 18:25:00.2|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated.
2023-01-31 18:25:00.2|Info|ReleaseSearchService|Searching indexer(s): [Rarbg] for Term: [Velma], Offset: 100, Limit: 100, Categories: [5000, 5010, 5020, 5030, 5040, 5045, 5050, 5060, 5070, 5080]
2023-01-31 18:25:00.2|Debug|Rarbg|Downloading Feed https://torrentapi.org/pubapi_v2.php?mode=search&search_string=Velma&ranked=0&category=18%3B41%3B49&limit=100&token=(removed)&format=json_extended&app_id=Prowlarr
2023-01-31 18:25:00.4|Debug|ReleaseSearchService|Total of 0 reports were found for Term: [Velma], Offset: 100, Limit: 100, Categories: [5000, 5010, 5020, 5030, 5040, 5045, 5050, 5060, 5070, 5080] from 1 indexer(s)
2023-01-31 18:25:00.5|Debug|Api|[GET] /api/v1/search?query=Velma&indexerIds=10&categories=5000&categories=5010&categories=5020&categories=5030&categories=5040&categories=5045&categories=5050&categories=5060&categories=5070&categories=5080&type=search&limit=100&offset=100: 200.OK (300 ms)

I genuinely believe this is not an API rate limiting issue, but if anyone can provide any context or guidance to resolve this issue I'd be very grateful.
Thanks

Expected Behavior

For the Rarbg indexer to return the results every time it's queried

Steps To Reproduce

1. Search anything in the Rarbg indexer
2. It won't return results most of the time

Environment

- OS: Openmediavault (Debian 10)
- Prowlarr: 1.0.1.2220-ls4 by linuxserver.io
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser: Firefox 110.0b7 (64-bit)

What branch are you running?

Master

Trace Logs?

prowlarr.debug.txt
prowlarr.txt

AB#4829

[hydriniumh2]

Oh nvm is this related to Rarbg returning a 200 status but still being rate limited?
And I guess there's no mention of this in the logs or documentation or anything.
In that case, a message to the user when it happens in Prowlarr would be helpful
#1277

[bakerboy448]

• trace which is required for bug reports likely has the response
• Prowlarr abides by the rate limits rarbg specifies and will backoff per their timed specifications
• Rarbg's 200 with a rate limit cannot be handled due to the GHI you referenced