when using x1337 the request not pass to flaresolverr

[Nikibasso94]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

when using x1337 the request not pass to flaresolverr

Expected Behavior

when using x1337 the request not pass to flaresolverr

Steps To Reproduce

i try move flovesolverr to vpn but nothing

Environment

- OS:ubuntu
- Prowlarr:2.3.5.5327
- Docker Install: 2.3.5.5327-ls143 di linuxserver.io
- Using Reverse Proxy: no
- Browser: edge

What branch are you running?

Master

Trace Logs? Not Optional

HTTP Error - Res: HTTP/2.0 [GET] https://1337x.to/cat/Movies/1/: 403.Forbidden (16 bytes)
error code: 1006

2026-04-23 13:02:38 INFO FlareSolverr 3.4.6
2026-04-23 13:02:38 INFO Testing web browser installation...
2026-04-23 13:02:38 INFO Platform: Linux-5.15.0-174-generic-x86_64-with-glibc2.36
2026-04-23 13:02:38 INFO Chrome / Chromium path: /bin/chromium
2026-04-23 13:02:38 INFO Chrome / Chromium major version: 142
2026-04-23 13:02:38 INFO Launching web browser...
2026-04-23 13:02:40 INFO FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36
2026-04-23 13:02:40 INFO Test successful!
2026-04-23 13:02:40 INFO Serving on http://0.0.0.0:8191
2026-04-23 13:03:44 INFO Incoming request => POST /v1 body: {'maxTimeout': 180000, 'cmd': 'request.get', 'url': 'https://prowlarr.servarr.com/v1/ping', 'proxy': {}}
2026-04-23 13:03:46 INFO Challenge not detected!
2026-04-23 13:03:46 INFO Response in 2.341 s
2026-04-23 13:03:46 INFO 192.168.80.1 POST http://192.168.0.79:8191/v1 200 OK
2026-04-23 13:03:47 INFO Incoming request => POST /v1 body: {'maxTimeout': 180000, 'cmd': 'request.get', 'url': 'https://prowlarr.servarr.com/v1/ping', 'proxy': {}}
2026-04-23 13:03:50 INFO Challenge not detected!
2026-04-23 13:03:50 INFO Response in 2.305 s
2026-04-23 13:03:50 INFO 192.168.80.1 POST http://192.168.0.79:8191/v1 200 OK
2026-04-23 13:03:55 INFO Incoming request => POST /v1 body: {'maxTimeout': 180000, 'cmd': 'request.get', 'url': 'https://prowlarr.servarr.com/v1/ping', 'proxy': {}}
2026-04-23 13:03:57 INFO Challenge not detected!
2026-04-23 13:03:57 INFO Response in 2.335 s
2026-04-23 13:03:57 INFO 192.168.80.1 POST http://192.168.0.79:8191/v1 200 OK
2026-04-23 13:04:06 INFO Incoming request => POST /v1 body: {'maxTimeout': 180000, 'cmd': 'request.get', 'url': 'https://prowlarr.servarr.com/v1/ping', 'proxy': {}}
2026-04-23 13:04:08 INFO Challenge not detected!
2026-04-23 13:04:08 INFO Response in 2.485 s
2026-04-23 13:04:08 INFO 192.168.80.1 POST http://192.168.0.79:8191/v1 200 OK
2026-04-23 13:06:02 INFO Incoming request => POST /v1 body: {'maxTimeout': 180000, 'cmd': 'request.get', 'url': 'https://kickass.torrentsbay.org/17/All/', 'proxy': {}}
2026-04-23 13:06:05 INFO Challenge detected. Title found: Just a moment...
2026-04-23 13:07:52 INFO Challenge solved!
2026-04-23 13:07:52 INFO Response in 109.947 s
2026-04-23 13:07:52 INFO 192.168.80.1 POST http://192.168.0.79:8191/v1 200 OK

2026-04-23 13:09:25.0|Warn|Cardigann|HTTP Error - Res: HTTP/2.0 [GET] https://1337x.to/cat/Movies/1/: 403.Forbidden (16 bytes)
error code: 1006
2026-04-23 13:09:25.0|Warn|Cardigann|Unable to connect to indexer

[v2.3.5.5327] NzbDrone.Core.Indexers.Exceptions.IndexerException: Unexpected response status Forbidden code from indexer request
at NzbDrone.Core.Indexers.Definitions.Cardigann.CardigannParser.ParseResponse(IndexerResponse indexerResponse) in ./NzbDrone.Core/Indexers/Definitions/Cardigann/CardigannParser.cs:line 58
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 591 at NzbDrone.Core.Indexers.HttpIndexerBase1.TestConnection() in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 766
RequestUri: https://1337x.to/cat/Movies/1/;StatusCode: Forbidden;ContentType: text/plain; charset=UTF-8;ContentLength: 16;ContentSample: error code: 1006

2026-04-23 13:09:25.0|Warn|ProwlarrErrorPipeline|Invalid request Validation failed:
-- : Unable to connect to indexer. Unexpected response status Forbidden code from indexer request
2026-04-23 13:09:25.3|Warn|Cardigann|Request for Il Corsaro Nero failed with status GatewayTimeout. Retrying in 1.9364014s.
2026-04-23 13:09:28.0|Warn|Cardigann|HTTP Error - Res: HTTP/2.0 [GET] https://1337x.to/cat/Movies/1/: 403.Forbidden (16 bytes)
error code: 1006
2026-04-23 13:09:28.0|Warn|Cardigann|Unable to connect to indexer

[v2.3.5.5327] NzbDrone.Core.Indexers.Exceptions.IndexerException: Unexpected response status Forbidden code from indexer request
at NzbDrone.Core.Indexers.Definitions.Cardigann.CardigannParser.ParseResponse(IndexerResponse indexerResponse) in ./NzbDrone.Core/Indexers/Definitions/Cardigann/CardigannParser.cs:line 58
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 591 at NzbDrone.Core.Indexers.HttpIndexerBase1.TestConnection() in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 766
RequestUri: https://1337x.to/cat/Movies/1/;StatusCode: Forbidden;ContentType: text/plain; charset=UTF-8;ContentLength: 16;ContentSample: error code: 1006

2026-04-23 13:09:28.0|Warn|ProwlarrErrorPipeline|Invalid request Validation failed:
-- : Unable to connect to indexer. Unexpected response status Forbidden code from indexer request
2026-04-23 13:09:31.0|Warn|Cardigann|HTTP Error - Res: HTTP/2.0 [GET] https://1337x.to/cat/Movies/1/: 403.Forbidden (16 bytes)
error code: 1006
2026-04-23 13:09:31.0|Warn|Cardigann|Unable to connect to indexer

[v2.3.5.5327] NzbDrone.Core.Indexers.Exceptions.IndexerException: Unexpected response status Forbidden code from indexer request
at NzbDrone.Core.Indexers.Definitions.Cardigann.CardigannParser.ParseResponse(IndexerResponse indexerResponse) in ./NzbDrone.Core/Indexers/Definitions/Cardigann/CardigannParser.cs:line 58
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 591 at NzbDrone.Core.Indexers.HttpIndexerBase1.TestConnection() in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 766
RequestUri: https://1337x.to/cat/Movies/1/;StatusCode: Forbidden;ContentType: text/plain; charset=UTF-8;ContentLength: 16;ContentSample: error code: 1006

2026-04-23 13:09:31.0|Warn|ProwlarrErrorPipeline|Invalid request Validation failed:
-- : Unable to connect to indexer. Unexpected response status Forbidden code from indexer request
2026-04-23 13:09:38.5|Info|ReleaseSearchService|Searching indexer(s): [Il Corsaro Blu] for Term: [], Offset: 0, Limit: 100, Categories: [2000, 2040, 2020, 2070, 2060, 2045]
2026-04-23 13:09:38.6|Info|ReleaseSearchService|Searching indexer(s): [The Pirate Bay] for Term: [], Offset: 0, Limit: 100, Categories: [2000, 2020, 2040, 2060, 2030, 2045]
2026-04-23 13:09:38.6|Info|ReleaseSearchService|Searching indexer(s): [kickasstorrents.ws] for Term: [], Offset: 0, Limit: 100, Categories: [2000]
2026-04-23 13:09:38.6|Info|ReleaseSearchService|Searching indexer(s): [FutureTorrent] for Term: [], Offset: 0, Limit: 100, Categories: [2000, 2040, 2060, 2050, 2020, 2080, 2030, 2070, 2010, 2045]
2026-04-23 13:09:55.4|Warn|ProwlarrErrorPipeline|Invalid request Validation failed:
-- Name: Should be unique
2026-04-23 13:10:00.3|Warn|Cardigann|HTTP Error - Res: HTTP/2.0 [GET] https://1337x.to/cat/Movies/1/: 403.Forbidden (16 bytes)
error code: 1006
2026-04-23 13:10:00.3|Warn|Cardigann|Unable to connect to indexer

[v2.3.5.5327] NzbDrone.Core.Indexers.Exceptions.IndexerException: Unexpected response status Forbidden code from indexer request
at NzbDrone.Core.Indexers.Definitions.Cardigann.CardigannParser.ParseResponse(IndexerResponse indexerResponse) in ./NzbDrone.Core/Indexers/Definitions/Cardigann/CardigannParser.cs:line 58
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 591 at NzbDrone.Core.Indexers.HttpIndexerBase1.TestConnection() in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 766
RequestUri: https://1337x.to/cat/Movies/1/;StatusCode: Forbidden;ContentType: text/plain; charset=UTF-8;ContentLength: 16;ContentSample: error code: 1006

2026-04-23 13:10:00.3|Warn|ProwlarrErrorPipeline|Invalid request Validation failed:
-- : Unable to connect to indexer. Unexpected response status Forbidden code from indexer request
2026-04-23 13:10:57.3|Warn|Cardigann|Request for Il Corsaro Nero failed with status GatewayTimeout. Retrying in 3.0560069s.
2026-04-23 13:12:30.4|Warn|Cardigann|HTTP Error - Res: HTTP/2.0 [GET] https://ilcorsaronero.link/: 504.GatewayTimeout (15 bytes)
error code: 504
2026-04-23 13:12:30.4|Warn|Cardigann|Unable to connect to indexer

[v2.3.5.5327] NzbDrone.Common.Http.HttpException: HTTP request failed: [504:GatewayTimeout] [GET] at [https://ilcorsaronero.link/]
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchIndexerResponse(IndexerRequest request) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 701 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 587
at NzbDrone.Core.Indexers.HttpIndexerBase`1.TestConnection() in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 766
error code: 504

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]

Prowlarr/Prowlarr#2561 / Prowlarr/Prowlarr#2600 / Prowlarr/Prowlarr#2646

[seanmb]

Still reproduces on the latest version (2.4.0.5397, Docker/linuxserver, master branch) — and I think I can add the missing piece here: FlareSolverr genuinely does solve the challenge for the exact same URL that Prowlarr then fails on, in the same search operation. That should rule out "the site is just blocking your IP" as the explanation.

Reproduced with kickasstorrents-to (same symptom as the 1337x case above — a working FlareSolverr proxy tagged to a Cardigann indexer, both the Add-time Test and real searches fail with a 403).

1. Querying FlareSolverr directly for the failing URL works fine, outside of Prowlarr entirely:

POST http://<flaresolverr>:8191/v1
{"cmd": "request.get", "url": "https://kickass.torrentbay.st/17/All/", "maxTimeout": 60000}

→ "status": 200, response body is the real page (genuine torrent listing HTML), not a block page.

2. In a live Prowlarr search, FlareSolverr's own log shows it succeeding on that exact URL:

INFO     Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://kickass.torrentbay.st/search/?q=inception', 'proxy': {}}
INFO     Challenge detected. Title found: Just a moment...
INFO     Challenge solved!
INFO     Response in 12.578 s
INFO     172.18.0.5 POST http://flaresolverr:8191/v1 200 OK

3. Prowlarr's own trace log, same search, same URL, moments later — a raw unproxied request that gets a plain nginx 403 (not even a Cloudflare challenge page):

[Info] ReleaseSearchService: Searching indexer(s): [kickasstorrents.to] for Term: [inception], Offset: 0, Limit: 0, Categories: []
[Warn] Cardigann: HTTP Error - Res: HTTP/2.0 [GET] https://kickass.torrentbay.st/search/?q=inception: 403.Forbidden (548 bytes)
[Warn] Cardigann: https://kickass.torrentbay.st/search/?q=inception

NzbDrone.Core.Indexers.Exceptions.IndexerException: Unexpected response status Forbidden code from indexer request
   at NzbDrone.Core.Indexers.Definitions.Cardigann.CardigannParser.ParseResponse(IndexerResponse indexerResponse) in ./NzbDrone.Core/Indexers/Definitions/Cardigann/CardigannParser.cs:line 58
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 591
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchReleases(...) in ./NzbDrone.Core/Indexers/HttpIndexerBase.cs:line 428
RequestUri: https://kickass.torrentbay.st/search/?q=inception;StatusCode: Forbidden;ContentType: text/html;ContentLength: 548;ContentSample: <html><head><title>403 Forbidden</title></head><body><center><h1>403 Forbidden</h1></center><hr><center>nginx</center></body></html>

So within a single search, FlareSolverr solves the challenge and gets a real 200 for this URL, but Prowlarr/Cardigann still ends up making (or falling back to) a separate, unproxied request to the identical URL and fails on that instead — even though the indexer is correctly tagged to the working FlareSolverr proxy (confirmed via Settings → Indexer Proxies → Test, and via the indexer's own "This site may use Cloudflare DDoS Protection, therefore Prowlarr requires FlareSolverr" notice showing the tag is recognized).

Also worth noting: the add-time "Test" step fails identically and can't be bypassed from the UI (Test and Save both enforce the same check), so there's currently no way to add this kind of indexer through the UI at all, even temporarily — it has to be inserted directly into the database to get past that gate, and it still won't actually return results afterward.

Happy to provide the full un-truncated trace log or DB/config details if useful for tracking this down further.

[augustuen]

Prowlarr's own trace log, same search, same URL, moments later — a raw unproxied request that gets a plain nginx 403 (not even a Cloudflare challenge page):

Thank you, seanmb's LLM. This supports our hypothesis that it isn't an issue with our cloudflare/flaresolverr handling, but rather that 1337x is blocking specific Prowlarr users. This also aligns with the fact that us maintainers are unable to reproduce the issue, since we're not banned. The reason flaresolverr works, and why it works when using flaresolverr's response is because flaresolverr uses a different User-Agent than Prowlarr.

[ejkarne]

I'll add some data to this. A couple months back I was IP banned from 1337x for heavy use through Prowlarr. Cycled my IP and was able to access the website again but would get errors through Prowlarr. A couple months ago I moved to a new house with a new ISP but I would still get the errors through Prowlarr (I also don't use a VPN for indexers so not that) but again the website worked fine. Ended up switching back to Jackett for the time being which doesn't have this issue.