BeyondHD search does not work when combining freeleech and limited #1241

New issue

Open

opened 2026-02-20 10:08:55 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 10:08:55 -05:00

Owner

Originally created by @nateify on GitHub (Oct 31, 2025).

I attest that there is not an existing issue for this?

I have searched the existing open and closed issues

I confirm this is not related to a Cardigann YML Indexer

Current Behavior

When adding BeyondHD as an indexer and checking both "Freeleech Only" and "Limited Only" an error is returned: "Query successful, but no results were returned from your indexer"

Expected Behavior

When testing a site search and with httpie CLI app, it is still possible to get results when using both search options``

Steps To Reproduce

Trace logs with only limited selected:

2025-10-31 17:36:30.2|Trace|Http|Req: 342 [POST] /foobar/prowlarr/api/v1/indexer/test (from 24.*.*.135 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0)
2025-10-31 17:36:30.2|Debug|BeyondHD|Downloading Feed https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","limited":1}
2025-10-31 17:36:30.2|Trace|ConfigService|Using default config value for 'logindexerresponse' defaultValue:'False'
2025-10-31 17:36:30.3|Trace|IndexerHttpClient|Req: [POST] https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","limited":1}
2025-10-31 17:36:30.3|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False'
2025-10-31 17:36:30.8|Trace|IndexerHttpClient|Res: HTTP/2.0 [POST] https://beyond-hd.me/api/torrents/(removed): 200.OK (115735 bytes) (542 ms)
2025-10-31 17:36:30.8|Debug|FlareSolverr|CF Protection not detected, returning original response
2025-10-31 17:36:30.8|Trace|Http|Res: 342 [POST] /foobar/prowlarr/api/v1/indexer/test: 200.OK (558 ms)

Trace logs with only freeleech selected:

2025-10-31 17:40:16.0|Trace|Http|Req: 349 [POST] /foobar/prowlarr/api/v1/indexer/test (from 24.*.*.135 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0)
2025-10-31 17:40:16.0|Debug|BeyondHD|Downloading Feed https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","freeleech":1}
2025-10-31 17:40:16.0|Trace|ConfigService|Using default config value for 'logindexerresponse' defaultValue:'False'
2025-10-31 17:40:16.0|Trace|IndexerHttpClient|Req: [POST] https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","freeleech":1}
2025-10-31 17:40:16.0|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False'
2025-10-31 17:40:16.3|Trace|IndexerHttpClient|Res: HTTP/2.0 [POST] https://beyond-hd.me/api/torrents/(removed): 200.OK (6071 bytes) (378 ms)
2025-10-31 17:40:16.3|Debug|FlareSolverr|CF Protection not detected, returning original response
2025-10-31 17:40:16.3|Trace|Http|Res: 349 [POST] /foobar/prowlarr/api/v1/indexer/test: 200.OK (386 ms)

Below, the larger trace log is attached. The JSON ends with total_pages":3,"total_results":227,"success":true so the results were correctly returned from the API.

When I make 3 API calls myself:
limited returns 222 results
freeleech returns 5 results
with both turned in it returns 227 results, the same as what Prowlarr sees

Environment

- OS: Ubuntu 22.04.5 LTS
- Prowlarr: 2.1.5.5216-ls246 by linuxserver.io
- Docker Install: Yes
- Using Reverse Proxy: Yes
- Browser: Firefox 140

What branch are you running?

Develop

Trace Logs?

trace.txt

I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I attest that I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @nateify on GitHub (Oct 31, 2025). ### I attest that there is not an existing issue for this? - [x] I have searched the existing open and closed issues ### I attest this is not related to a Cardigann YML Indexer. - [x] I confirm this is not related to a Cardigann YML Indexer ### Current Behavior When adding BeyondHD as an indexer and checking both "Freeleech Only" and "Limited Only" an error is returned: "Query successful, but no results were returned from your indexer" ### Expected Behavior When testing a site search and with httpie CLI app, it is still possible to get results when using both search options`` ### Steps To Reproduce Trace logs with only `limited` selected: ``` 2025-10-31 17:36:30.2|Trace|Http|Req: 342 [POST] /foobar/prowlarr/api/v1/indexer/test (from 24.*.*.135 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0) 2025-10-31 17:36:30.2|Debug|BeyondHD|Downloading Feed https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","limited":1} 2025-10-31 17:36:30.2|Trace|ConfigService|Using default config value for 'logindexerresponse' defaultValue:'False' 2025-10-31 17:36:30.3|Trace|IndexerHttpClient|Req: [POST] https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","limited":1} 2025-10-31 17:36:30.3|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False' 2025-10-31 17:36:30.8|Trace|IndexerHttpClient|Res: HTTP/2.0 [POST] https://beyond-hd.me/api/torrents/(removed): 200.OK (115735 bytes) (542 ms) 2025-10-31 17:36:30.8|Debug|FlareSolverr|CF Protection not detected, returning original response 2025-10-31 17:36:30.8|Trace|Http|Res: 342 [POST] /foobar/prowlarr/api/v1/indexer/test: 200.OK (558 ms) ``` Trace logs with only `freeleech` selected: ``` 2025-10-31 17:40:16.0|Trace|Http|Req: 349 [POST] /foobar/prowlarr/api/v1/indexer/test (from 24.*.*.135 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0) 2025-10-31 17:40:16.0|Debug|BeyondHD|Downloading Feed https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","freeleech":1} 2025-10-31 17:40:16.0|Trace|ConfigService|Using default config value for 'logindexerresponse' defaultValue:'False' 2025-10-31 17:40:16.0|Trace|IndexerHttpClient|Req: [POST] https://beyond-hd.me/api/torrents/(removed): {"action":"search","rsskey":"(removed)","freeleech":1} 2025-10-31 17:40:16.0|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False' 2025-10-31 17:40:16.3|Trace|IndexerHttpClient|Res: HTTP/2.0 [POST] https://beyond-hd.me/api/torrents/(removed): 200.OK (6071 bytes) (378 ms) 2025-10-31 17:40:16.3|Debug|FlareSolverr|CF Protection not detected, returning original response 2025-10-31 17:40:16.3|Trace|Http|Res: 349 [POST] /foobar/prowlarr/api/v1/indexer/test: 200.OK (386 ms) ``` Below, the larger trace log is attached. The JSON ends with `total_pages":3,"total_results":227,"success":true` so the results were correctly returned from the API. When I make 3 API calls myself: limited returns 222 results freeleech returns 5 results with both turned in it returns 227 results, the same as what Prowlarr sees ### Environment ```markdown - OS: Ubuntu 22.04.5 LTS - Prowlarr: 2.1.5.5216-ls246 by linuxserver.io - Docker Install: Yes - Using Reverse Proxy: Yes - Browser: Firefox 140 ``` ### What branch are you running? Develop ### Trace Logs? [trace.txt](https://github.com/user-attachments/files/23266531/trace.txt) ### I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I attest that I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman added the

Type: Bug

Status: Needs Triage

labels

2026-02-20 10:08:55 -05:00

deekerman commented

2026-02-20 10:08:56 -05:00

Author

Owner

@nateify commented on GitHub (Oct 31, 2025):

I also wanted to add that the trace log did remove sensitive data in some places but it did not remove the rsskey from the end of download_url

@nateify commented on GitHub (Oct 31, 2025): I also wanted to add that the trace log did remove sensitive data in some places but it did not remove the rsskey from the end of `download_url`

deekerman commented

2026-02-20 10:08:56 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Oct 31, 2025):

It's expected since the API conditions are AND, not OR. You can go around this by adding it twice, but there's nothing to do from code since it's how their API works.

@mynameisbogdan commented on GitHub (Oct 31, 2025): It's expected since the API conditions are AND, not OR. You can go around this by adding it twice, but there's nothing to do from code since it's how their API works.