Deploy FlareSolverr | (Just Updated) Cloudflare Solver API, Key-Locked From Boot

Deploy and Host FlareSolverr on Railway

FlareSolverr is a proxy server that drives a real Chromium browser to get past Cloudflare and similar browser challenges, then hands back the page, cookies and user agent over a small JSON API. Scrapers, Prowlarr, Sonarr, Radarr and AI agents call it when a plain HTTP request is blocked.

This template runs FlareSolverr 3.5.2 as one service from a wrapper image built on the official one, with a public Railway domain and an API key generated for every deploy.

About Hosting FlareSolverr

• The API is locked from the first request. A stock FlareSolverr container has no authentication: an anonymous POST /v1 returned 200 and a rendered page, so anyone who finds the URL can make your container browse any site they name. Here the upstream server listens on loopback only, and a small proxy on Railway's PORT answers 401 unless the request carries the key.
• Three ways to send the key. Authorization: Bearer , an X-API-Key header, or the key as the first path segment (https:////v1) for tools such as Prowlarr that only accept a base URL.
• It has a public URL and an open health check. GET /health returns FlareSolverr's own readiness reply without a key, so Railway can check the service.
• Nothing to configure. No volume is needed: sessions live in memory and a redeploy starts clean. Chromium needs memory, so give the service at least 1 GB.

Common Use Cases

• A shared Cloudflare-solving endpoint for scrapers and crawlers
• The FlareSolverr proxy that Prowlarr, Sonarr and Radarr indexers ask for
• A browser-backed fetch tool for AI agents and RAG pipelines
• Reading pages that return a challenge to plain HTTP clients

Dependencies for FlareSolverr Hosting

• None. A single service, no database and no volume.

Deployment Dependencies

• FlareSolverr project: https://github.com/FlareSolverr/FlareSolverr
• Wrapper image source: https://github.com/bon5co/flaresolverr-railway

Implementation Details

curl -X POST https:///v1 \
  -H "Authorization: Bearer " -H "Content-Type: application/json" \
  -d '{"cmd":"request.get","url":"https://example.com","maxTimeout":60000}'

Inside the same Railway project use http://flaresolverr.railway.internal:8080/v1 with the same key.

Why Deploy FlareSolverr on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying FlareSolverr on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.