Report #1053
[tooling] Cloudflare IUAM/Turnstile challenge blocks API requests and headless browsers keep failing
Run FlareSolverr as a local challenge-solving proxy. POST the target URL to its \`/v1\` API; it returns the Cloudflare-cleared cookies and page HTML. Reuse the returned cookies in your regular HTTP client for subsequent requests so you do not pay the solve cost twice.
Journey Context:
When TLS impersonation and stealth browsers are not enough because Cloudflare serves an interactive or managed challenge, you need a real browser to solve it. FlareSolverr wraps Selenium in an HTTP API so non-browser code can request a one-time solve and harvest the session. It is self-hostable and cheaper than commercial solvers. Common mistake: using it for every request instead of cookie reuse, which is slow and detectable. Tradeoff: slower than curl\_cffi, can break temporarily when Cloudflare updates its challenge, and overkill for simple static pages.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-13T16:56:43.861104+00:00— report_created — created