-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FlareSolverr: Bypass Cloudflare protection in Jackett #9029
Comments
I'm not sure how long the challange codes last until they require a new code, but you can add the cookie inside .config/Jackett/Indexers/TorrentWebsite.json Go to the desired website → Inspect Element → Network → Copy the cookie Go to .config/Jackett/Indexers/TorrentWebsite.json and add this (change out value to the cookie you copied):
The cookie might look something like this: |
Very needed feature ! Yggtorrent (which is the main french torrent indexer) uses cloudflare Upvote for implementing a durable solution to handle those dynamic cloudflare challenges |
Any updates on this ? For m'y knowledge, why dont you merge this PR ? |
Add tvchaosuk to the growing list of trackers using the new cloudflare. I'm trying to download the Jackett beta linked above, but the link goes to an empty web page. |
@ilike2burnthing Is it possible to pull the Jackett beta version if running in docker? |
Unless @ngosang or someone else has Dockerised it (or you want to give it a shot), then no. Sorry :/ |
This is the issue I am having as well. Would LOVE to be able to use this... EDIT: I was able to pull the source and build it. Verified working with SceneTime at least. Never containerized something before but may give it a shot. |
Sounds like this feature is mostly working. Any updates on if this could be considered a first-class feature? Even as a separate docker container it'd be amazing. |
My thought is that maybe Jackett is using IPv6 and Flaresolverr IPv4? If so, there should be an option to force Jackett to only use IPv4. |
This is a great suggestion but neither the jail nor the vm are configured to use IPv6. |
Then idk in your case what could be the issue. |
Does your ISP actually provide IPv6 support? |
Mine? Yes, it does. |
Unless you configure Ipv6 fully with NAT v6 from your docker host, or allocate the right IPv6 Range into your docker daemon it's going to be an issue. So either configure IPv6 fully or completely disable IPv6 on your docker host in any case, you should call your flaresolverr container from jackett container via it's name say you got 2 containers named : jackett & flaresolverr you can try if this works by doing from your docker host "docker exec jackett ping flaresolverr" |
Are you talking to me or manalive? |
Well, indeed it seems to be problematic you can pass to your container on creation options like you can also add this to your /etc/docker/daemon.json file on your host
then reload docker daemon Alternate, go full IPv6 |
Thanks, but I don't use docker for Jackett. Only for FlareSolverr.
Yeah, I'm considering doing this. Appears to be the only way to make it work while running Jackett outside docker. |
If your docker host is a windows PC, just open the properties of your network card, untick IPV6 and you're good |
Did you find an elegant solution ? |
Anyone has bypassed the captcha error?
Tried to configure |
Same here :/ |
https://github.com/FlareSolverr/FlareSolverr#captcha-solvers |
Is it possible to change the maxTimeout setting in a windows environment? |
@ngosang ^ |
In Jackett is not possible to change FlareSolverr maxTimeout, it's fixed to 55 s. It could be implemented of course. |
User configurable maxTimeout might be worthwhile for those with slower systems. |
That would be great if it could. I am getting maxTimeout errors every time for oMg[WtF]trackr and a handful of others. I am using this with Jackett and the PC is also behind a VPN, has Jackett, Radarr, Sonarr, Lidarr and qBit running on the same PC. |
Make sure you're running FlareSolverr v2.1.0, was released 21hrs ago, resolved a lot of the recent issues. |
For people continuing to have the issue of Jackett reporting invalid cookies, try using |
I'm not able to access kickasstorrents.to indexer and Jacket is referencing a FlareSolverr log. Here is the log,
|
@pharpe open a new issue over on the FlareSolverr repo with debug FlareSolverr logs - https://github.com/FlareSolverr/FlareSolverr#environment-variables |
TLDR; Since Jun 2020 Jackett can't resolve the Cloudflare challenge. In this issue I will try to explain the cause, affected trackers and a tentative solution.
There are some torrent sites which use Cloudflare protection to avoid DDoS attacks. The challenge used to be a small JavaScript code with mathematical operations. The browser does the maths for you and after a few seconds you can see the web site.
Jackett has been using CloudflareSolverRe library to resolve Cloudflare challenges for years. That library was really fast and lightweight, but it had to be updated each time Cloudflare changed the challenge. In Jun 2020 Cloudflare increased the complexity of the challenge and it can't be solved with that library anymore. More details: #8840 (comment)
Affected trackers: bteye, gktorrent, limetorrents, pornleech, torrent9clone, torrentz2, zetorrents (could be more because they enable/disable Cloudflare on demand)
To solve the new challenge we need a full web browser. This brings new problems: huge RAM usage, more disk space, OS compatibility... so we decide to not include it in Jackett. See #8840 (comment)
Since Cloudflare is present in 7 of 500 supported trackers, it doesn't make sense to make it mandatory for all users, so it's optional.
Instructions to test the POC:
This feature is experimental. It may never be a part of Jackett. Everything will depend on whether it is useful for users.
Please help us to test it and if you find any problems in any of the three projects open an issue.
The text was updated successfully, but these errors were encountered: