Flaresolverr alternative, using Scrappey.com
Developed with the software and tools below.
Replaces Flaresolverr by listening to the same port and parsing the requests the same way Flaresolverr would. (Only GET requests for now) Instead of doing all the bypassing work itself, the script simply delegate the task to scrappey.com and returns the necessary cookies and content.
As Cloudflare cf_clearance cookie is tied to a specific User-Agent and IP address, you need a public working forward proxy (Squid for example) where Scrappey.com requests will be redirected to.
The script has only been tested with Prowlarr, with an average of one request every 2 hours (which is the cf_clearance cookie lifespan).
Feel free to test it with Jackett or any other tool and give your feedback.
└── scrappey_proxy/
├── Dockerfile
├── poetry.lock
├── pyproject.toml
└── scrappey_proxy
├── flaresolverr.py
├── main.py
├── scrappey.py
└── utils.pyAn amd64 docker image is available for Docker & Kubernetes installation.
You will need to provide the following environment variables :
PROXY_USERNAME: Username of your forward proxyPROXY_PASSWORD: Password of your forward proxyPROXY_INTERNAL_IP: Internal IP address of your forward proxyPROXY_EXTERNAL_IP: External IP address of your forward proxyPROXY_INTERNAL_PORT: Internal port of your forward proxyPROXY_EXTERNAL_PORT: External port of your forward proxySCRAPPEY_API_KEY: API Key of your scrappey.com account
Add two indexers proxies in "Settings" -> "Indexers" :
- A flaresolverr proxy with the IP address of the machine the script is running on. You do not need to change the default port (8191).
- An HTTP proxy, using
PROXY_INTERNAL_IPas host,PROXY_INTERNAL_PORTas port, andPROXY_USERNAME&PROXY_PASSWORDas credentials.
For each indexer proxies, set a tag and add it to the list of tags in your indexer configuration.
This project is protected under the GPL3-0 License. For more details, refer to the LICENSE file.