FlareSolverr Standby
Pricing
from $0.01 / actor start
FlareSolverr Standby
Runs FlareSolverr (Cloudflare/DDoS-Guard bypass proxy) as an always-on Apify Standby Actor, with optional Apify Proxy.
Pricing
from $0.01 / actor start
Rating
0.0
(0)
Developer
R.L.
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
9 days ago
Last modified
Categories
Share
FlareSolverr Standby
Runs FlareSolverr — a proxy server that bypasses Cloudflare and DDoS-Guard protection using a real, undetected Chromium browser — as an always-on Apify Standby Actor. No local Docker, browser, or infrastructure to run: start the Actor once and call it like a hosted API.
Why use this?
Running FlareSolverr yourself means managing a Chromium container, xvfb, and uptime. This Actor puts FlareSolverr behind an Apify Standby URL so it stays warm and reachable over HTTPS, with Apify Proxy wired in for IP rotation without touching FlareSolverr's own proxy config.
Use a residential proxy group. Apify's datacenter IPs are widely fingerprinted and get outright IP-banned by Cloudflare on a lot of sites — in testing, requests to Yellow Pages and Truth Social failed instantly with "Cloudflare has blocked this request. Probably your IP is banned," and other sites (Redbubble, SearchPeopleFree) hung until timeout instead of ever getting a challenge page to solve. Switching to the RESIDENTIAL proxy group fixed every one of those cases — same URLs, same FlareSolverr call, 200 OK. Datacenter IPs may work fine for less aggressively protected sites, but residential is the reliable default for real Cloudflare/DDoS-Guard challenges.
How to use it
- Proxy configuration defaults to Apify Proxy with the Residential group — no setup needed. Only change it in the Actor's Input tab if you know the target site doesn't IP-ban datacenter ranges, or want to disable proxying entirely.
- Start the Actor (or just call its Standby URL — Apify starts it for you on first request).
- Send requests to the Standby URL exactly as you would to a local FlareSolverr instance, using your Apify API token as a bearer token:
The /v1 endpoint accepts the same commands and fields as upstream FlareSolverr (request.get, request.post, sessions, cookies, maxTimeout, etc.) — see the FlareSolverr API docs for the full request/response shape. You can still pass a per-request "proxy": {"url": "..."} field in the body to override the Actor's proxy configuration for that call, e.g. to use your own residential proxy:
Input
- Proxy configuration (
proxyConfiguration) — Apify Proxy setup, applied to every FlareSolverr request that doesn't specify its ownproxyfield. Defaults to theRESIDENTIALgroup — datacenter proxies (and no proxy at all) get IP-banned or stall on many Cloudflare-protected sites. Turn off "Use Apify Proxy" only if you know the target doesn't need it. - Log level (
logLevel) — FlareSolverr log verbosity (info,debug,warning,error). Defaultinfo. - Headless browser (
headless) — keep enabled unless debugging. Defaulttrue.
Output
This Actor has no dataset output — it's a live HTTP service. Every request to the Standby URL gets FlareSolverr's normal JSON response synchronously:
The cf_clearance cookie plus the returned userAgent is what you replay on subsequent plain HTTP requests to the same site — you don't need to solve the challenge again for every call.
Pricing
Billed on Apify's Standby Actor compute-time model — you pay for the time the container is up and serving requests, not per call. Add Apify Proxy usage cost if you enable the recommended residential proxy. Solving a Cloudflare challenge typically takes a few seconds of browser time.
FAQ
- Do I need Apify Proxy? Not strictly, but datacenter IPs (the default without proxy) get flagged and either IP-banned outright or left hanging until timeout on many real-world sites. Residential proxy is the recommended, tested-working default.
- Does this store any scraped data? No, responses are returned directly over HTTP and nothing is written to a dataset.
- Can I use my own proxy instead of Apify Proxy? Yes — pass
"proxy": {"url": "..."}in the request body per FlareSolverr's own API; it takes priority over the Actor's proxy configuration. - Only use this Actor against sites you're authorized to access; you're responsible for complying with target sites' Terms of Service.
