Exception: The cookies provided by FlareSolverr are not valid

Jackett - Docker v0.17.50-ls9 amd64 FlareSolver - Docker v1.2.0 amd64

When not using a proxy/VPN in Jackett’s settings, this affects:

• ~cpasbien~ - region blocked
• Epizod

Indexers which are working when not using a proxy/VPN:

• dhmy
• EXT
• HDDolby
• MejorTorrent
• MyPornClub
• ProStyleX
• TorrentKitty
• TorrentProject
• YGGcookie

Indexers which get Exception (INDEXER): FlareSolverr was able to process the request, but a captcha was detected. Message: Captcha detected but no automatic solver is configured. (so would probably work if I set one up) when not using proxy/VPN:

• Pirateiro
• ~TorrentBomb~ - URL updated, currently no Cloudflare - https://torrentb.site/
• Torrentz2k
• YGGtorrent

However, the only indexers which work when using a proxy/VPN in Jackett’s settings are:

• EXT
• HDDolby

The rest show that the cookies aren’t valid, or that a captcha was detected. Any way to extend the proxy settings for Jackett to FlareSolver, or add similar environment variables to FlareSolver?

[ngosang]

@ilike2burnthing I think this can be closed.

• Epizod was fixed in => https://github.com/Jackett/Jackett/pull/10528 and https://github.com/Jackett/Jackett/pull/10529
• Proxy is not supported by now. We have another issue #26
• For the captchas, well, I think it is better to lower expectations. There are some plugins but nothing works 100% #31

[ngosang]

As far as I can tell while debugging YGGCookies the user-agent string is cosmetic(in Cardigann) and not use at all, it use the one in BrowserUtil.cs. Some indexer in c#, for example abnormal, use a custom useragent that work

I will take a look and fix Jackett if required.

I didn’t like it either but I wanted to be safe in case it detected the word mile a part in the page. Like error code: this is a long line 1020

It’s safer to check the http response code than the response text. I’m getting 403 forbidden with Linux useragent in epizod.tv. If we can’t find cloduflare selectors and response code = 403 i think it’s safe to say the user is blocked or banned.