FlareSolverr integration. Bypass Cloudflare protection

[ngosang]

POC with FlareSolverr integration.
https://github.com/ngosang/FlareSolverr

Details: #9029

[JakeShirley]

@ngosang any update on this? This PR looks pretty small and from the sounds of it others have compiled and tested this locally. Any idea when you might have enough time to merge this in?

This sort of thing is super appreciated for a lot of us, so thanks a ton for taking the time to investigate/prototype this.

[toxic0berliner]

ping again. Any news ? I'm currently in the process of building my custom docker image with the Jackett fork of @ngosang just to add this FlareSolverr API option in Jackett, and I know I'll be passing out on many many commits since he did this PR, but beeing able to pass cloudflare challenges is my current limiting factor...

Thnks in advance for integrating that into Jackett. We will take care of spinning up a flaresolverr instance by ourselves for those interested, I think adding this might not cause too much of a disturbance for those who don't need it.

Edit: plus I must be bad, but I get to build jackett properly on my desktop and it works with flaresolverr, but I don't know how to package it properly for a docker container, each time I managed it, Jackkett complained that FlareSolverr provided some invalid cookie... Did not happen on my desktop. Seems building and packaging Jackett with this option to use Flaresolverr is of real added value, at least to me ;)

[jscoys]

Hey @ngosang & @toxic0berliner it would be awesome if you create a docker image including Jackett and the FlareSolverr API all included! Let us know if you succeed the name of the docker image, especially if you need someone to test it.

[JakeShirley]

While a combined docker image would be amazing, I think a separate image would be fine too (especially if you Docker Compose it). I'd love to have it officially supported though! I don't mind spinning up a separate docker container just for this.

[toxic0berliner]

I agree with @JakeShirley , one you have the feature, one or 2 docker containers is not going to make a huge difference, be it compose or k8s or anything else, having the feature at least available is the biggest deal, installing FlareSolverr separately or spinning it up in a docker container are both supported and easy... But making by ourselves an up-to-date Jackett including this PR is more of a hassle I believe.

Thanks in advance to @ngosang for his efforts merging that in.

[CyberPoison]

Please merge this code to be able to use it on docker and test it, or at least create a specific image for testing purposes.

Kind regards

[Twanislas]

@CyberPoison there are already some users who built docker images, you can try sclemenceau/docker-jackett:cloudproxy for instance.

Bear in mind that these are no official Jackett images and are there for testing purposes, until this PR is merged and the changes pushed into the official LSIO ones.

Cheers !

[Lockie85]

Is this going into Jackett?

[ngosang]

Is this going into Jackett?

Yes, but there are some issues in CloudProxy that have to be addressed first => NoahCardoza/CloudProxy#31

[ngosang]

Fresh news!

• Jackett v0.17.50 is out and it includes this feature. If you are using a custom build, you can install the official release and enable auto-updates. Documentation
• FlareSolverr v1.2.0 is out. It includes all features from CloudProxy and we have new Docker images and documentation

Current workarounds are still working but I recommend you to install latest releases from Jackett and FlareSolverr. If we all use the same versions it is easier to provide support. If you have any issue with CloudFlare, YGG, etc open the issues in FlareSolverr.

@garfield69 @ilike2burnthing fyi

[ilike2burnthing]

v0.17.50 is out for Docker as well - https://github.com/linuxserver/docker-jackett/releases/tag/v0.17.50-ls9