ThePirateBay "Test" option fails when Cloudflare/Flaresolverr is active

[acg5159]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Cannot enable The Pirate bay as test always fails when Cloudlare and FlareSolverr enabled:
"Unable to access apibay.org, blocked by CloudFlare Protection."

Manually running the either baseurl or the json file through Flaresolverr works.
It appears that we expect a json file, but when FS is enabled, it will return the html file with json in <pre> tags in the body.

Expected Behavior

Test should pass

Steps To Reproduce

1. From Prowlarr select The Pirate Bay indexer
2. Ensure Cloudflare is active and FlareSolverr is enabled on indexer
3. Run Test
4. See error

Environment

- OS: Ubuntu 24.04.3
- Prowlarr: 2.3.0.5236-ls134 by linuxserver.io
- Docker Install: Yes - lscr.io/linuxserver/prowlarr:latest
- Using Reverse Proxy: no
- Browser: N/A

What branch are you running?

Master

Trace Logs? Not Optional

What I see in the Trace: prowlarr.trace.txt

1. GET https://apibay.org/precompiled/data_top100_recent.json

2. Detect Cloudflare

3. Retry with FlareSolverr

4. Get HTML with embeded json <--- Is this an issue as yml seems to expect json not HTML
   See https://github.com/Prowlarr/Indexers/blob/master/definitions/v11/thepiratebay.yml#L156-L158

5. RateLimit Trigger

6. Retry GET https://apibay.org/precompiled/data_top100_recent.json

7. Fail as Cloudflare still enabled...

8. Return Error

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

• 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.

[ilike2burnthing]

FlareSolverr isn't detecting a challenge, so no cookie can be returned.

So long as Prowlarr and FlareSolverr are on the same device, sharing the same public IP (no proxy or VPN), and IPv6 is disabled, there's more that can be done.

Some people are having the same issue, so it seems that it's a mix of IP and something about Prowlarr (UA?).