Back to all templates
FlareSolverr logo

FlareSolverr

Infrastructure512MB+ RAM

Proxy server that bypasses Cloudflare and DDoS-Guard challenges, used by *arr apps and scrapers

infrastructurenetworkingflaresolverropen-sourceself-hosteddocker

Deploy FlareSolverr in 3 Steps

1

Connect Your VPS

Add your server credentials to Server Compass

2

Select FlareSolverr

Choose from our template library

3

Deploy & Configure

Fill in settings and click Deploy

No Docker knowledge required
Step-by-step deployment guide

Deploy FlareSolverr on a VPS with Server Compass

Use the FlareSolverr template in Server Compass to deploy a self-hosted Cloudflare challenge solver API on your VPS, then verify the service response.

About 10 minutesBrowser verified
1
Step 1

Open the server Apps tab

Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.

Server Compass Apps tab before creating a FlareSolverr app
2
Step 2

Choose an app template

Click New App and choose the template deployment path so Server Compass can load the built-in catalog.

Choosing to deploy an app from a Server Compass template
3
Step 3

Search for FlareSolverr

Use the template picker search to find FlareSolverr in the Server Compass template catalog.

Searching for FlareSolverr in the Server Compass template picker
4
Step 4

Select the FlareSolverr template

Choose the FlareSolverr template. Server Compass fills the single-container API service, log level, captcha solver setting, timezone, and public API port.

FlareSolverr template selected in Server Compass
5
Step 5

Review the FlareSolverr settings

Confirm the app name and compose service. In this run, the app was named flaresolverr-demo and used host port 4144.

Reviewing FlareSolverr project settings and compose service
6
Step 6

Deploy FlareSolverr

Review the generated compose settings, confirm the FlareSolverr API port is available, and click Deploy.

Reviewing FlareSolverr web port before deployment
7
Step 7

Watch the deployment progress

Keep the deployment modal open while Server Compass uploads the compose file, pulls the FlareSolverr image, starts the container, and verifies the stack.

Server Compass deploying the FlareSolverr template on the VPS
8
Step 8

Confirm FlareSolverr is running

After deployment finishes, return to the Apps tab and confirm the FlareSolverr app is marked Running with its published API port available.

FlareSolverr template running in the Server Compass Apps tab
9
Step 9

Verify FlareSolverr with the API response

Call the FlareSolverr API endpoint and inspect recent logs to confirm the Chromium-backed solver service is responding.

FlareSolverr service verification output from logs

After FlareSolverr Opens

  • Never expose FlareSolverr directly to the public internet without network restrictions.
  • Keep the published API port reachable only from trusted scraper or indexer services.
  • Monitor CPU and memory because each request can launch Chromium work.
  • Test with harmless public URLs before routing real indexer traffic.
  • Use conservative retry and timeout settings in connected applications.
  • Watch container logs the first time you proxy a challenged request.
  • Keep the FlareSolverr image updated for Chromium and dependency security fixes.

Verified Result

FlareSolverr returned an API response and logs showed startup activity.

FlareSolverr deployment questions

What does the FlareSolverr template deploy?

It deploys FlareSolverr as a single-container JSON API for solving browser challenges for trusted scraper or indexer clients.

Which port did the tutorial use?

The tutorial used host port 4144, which maps to the FlareSolverr API on container port 3002.

Does FlareSolverr need setup after deployment?

No account setup is required. Verify the API response, then connect trusted clients such as Prowlarr or private scraper jobs.

Should this become a blog post?

No. The deployment guide should live on the FlareSolverr template detail page and be linked from the reusable template deployment docs page.

After Deployment

After deploying FlareSolverr with Server Compass, complete these steps to finish setup

1

Verify the service is up: `curl http://YOUR_SERVER_IP:{{PORT}}/`

2

Configure Prowlarr/FlareSolverr indexer integration with URL http://flaresolverr:8191 (if on same network) or http://YOUR_SERVER_IP:{{PORT}}

3

Watch container logs the first time you proxy a challenged request

Need help? Check out our documentation for detailed guides.

FlareSolverr FAQ

Common questions about self-hosting FlareSolverr

How do I deploy FlareSolverr with Server Compass?

Simply download Server Compass, connect to your VPS, and select FlareSolverr from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.

What are the system requirements for FlareSolverr?

FlareSolverr requires a minimum of 512MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.

Can I migrate my existing FlareSolverr data?

Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard FlareSolverr backup and restore procedures.

How do I update FlareSolverr to the latest version?

Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest FlareSolverr image will be pulled and deployed with zero downtime.

Is FlareSolverr free to self-host?

FlareSolverr is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.

Ready to Self-Host FlareSolverr?

Download Server Compass and deploy FlareSolverr to your VPS in under 3 minutes. No Docker expertise required.

Download Server Compass