Loading page
Loading page

Developer tools
A proxy server that opens pages in Chrome, waits out Cloudflare and DDoS-GUARD challenges, and returns the HTML and cookies.
FlareSolverr is a small proxy server. When a request arrives, it starts a Chrome browser with Selenium and undetected-chromedriver, opens the URL and waits until the Cloudflare or DDoS-GUARD challenge clears or a timeout is reached. It then sends back the HTML and the cookies. Your other tools can reuse those cookies to make normal HTTP requests.
Between requests it sits idle and uses few resources. You can also keep a permanent session open, but the README asks you to close sessions as soon as you are done.
It is a helper service for other apps, not something you use on its own. You run it next to the tool that calls it, and that tool sends its page requests through FlareSolverr. Developers also use it for personal scrapers.
FlareSolverr needs to sit close to the apps that call it. Running it on the same plan as your other services keeps the setup in one place.
The trade-offs are real. It uses a full browser per request, so memory use spikes under load. The README warns not to expose it to the internet, so keep it on a private address. Respect the terms of the sites you access. You also keep the image updated, since challenge methods change often.
Containers: ghcr.io/flaresolverr/flaresolverr:latest
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose FlareSolverr, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the FlareSolverr setup screen.