FlareSolverr

Bypass Cloudflare and DDoS-GUARD protection for automation tools

FlareSolverr - Cloudflare & DDoS-GUARD Bypass Proxy

FlareSolverr is a proxy server designed to bypass Cloudflare and DDoS-GUARD protection mechanisms. It acts as a middleware between your automation tools (like Prowlarr, Jackett, or custom scripts) and protected websites, solving challenges and returning clean responses.

What is FlareSolverr?

FlareSolverr solves the problem of accessing websites protected by anti-bot services:

• Cloudflare Bypass - Automatically solve Cloudflare challenges
• DDoS-GUARD Support - Handle DDoS-GUARD protection mechanisms
• API-Based - Simple REST API for easy integration
• Browser Emulation - Uses real browser engines to appear legitimate
• Challenge Solving - Handles JavaScript challenges, CAPTCHAs, and cookies
• Session Management - Maintains sessions for repeated access

Installation

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find FlareSolverr in the catalog (browse the Automation category or search), and click Install. The dashboard streams the install log live and FlareSolverr appears in your Application Control panel when it finishes. Reinstall, Update, and Remove are available from the same panel.

What you see is gated by your account: admins manage any user’s apps; regular users manage their own. See App Management for the full flow.

The installer sets up an isolated Python 3.11 virtual environment, installs the Chromium browser FlareSolverr uses to solve challenges (pulled from the Chromium PPA on Ubuntu Jammy), installs the Python dependencies, and registers a systemd service bound to 127.0.0.1:8191.

Install from the CLI (automation)

The CLI runs the same scripts as the Dashboard and is suited to automation and scripting:

qb install flaresolverr -u username
qb reinstall flaresolverr -u username
qb update flaresolverr -u username
qb remove flaresolverr -u username

Full flag reference: CLI Reference.

Enhanced Features

FlareSolverr on QuickBox Pro includes several production-ready features:

Service Management

FlareSolverr runs as a systemd service for reliable operation:

Check Service Status

systemctl status flaresolverr@username

Restart Service

systemctl restart flaresolverr@username

Stop Service

systemctl stop flaresolverr@username

View Live Logs

journalctl -u flaresolverr@username -f

Check Service Health

Verify FlareSolverr is responding:

curl http://localhost:8191

You should see: FlareSolverr is ready!

Supported Integrations

FlareSolverr integrates seamlessly with your automation stack:

Configuration

Directory Structure

FlareSolverr files are organized as follows:

Default Configuration

FlareSolverr is configured with sensible defaults:

• Port: 8191 (localhost only)
• Host: localhost (not exposed externally for security)
• CAPTCHA Solver: hcaptcha-solver enabled
• Working Directory: /opt/username/FlareSolverr
• Python Environment: /opt/username/lib/python/FlareSolverr/.venv
• Temporary Directory: /home/username/tmp/FlareSolverr

Advanced Configuration

To modify FlareSolverr settings, edit the systemd service:

sudo nano /etc/systemd/system/flaresolverr@username.service

Available environment variables:

# CAPTCHA solver backend (hcaptcha-solver)
Environment="CAPTCHA_SOLVER=hcaptcha-solver"
 
# Port for the proxy server
Environment="PORT=8191"
 
# Host binding (localhost for security)
Environment="HOST=localhost"
 
# Temporary directory for browser profiles
Environment="TMPDIR=/home/%i/tmp/FlareSolverr"

After editing, reload and restart:

sudo systemctl daemon-reload
sudo systemctl restart flaresolverr@username

Integration with Automation Tools

Prowlarr Integration

Configure FlareSolverr in Prowlarr:

1. Navigate to Settings → Indexers → FlareSolverr
2. Add new FlareSolverr instance
3. Enter URL: http://localhost:8191
4. Save and test connection

Per-Indexer Configuration:

• Edit indexer settings
• Enable FlareSolverr for specific indexers
• Set FlareSolverr tags if needed

Jackett Integration

Configure FlareSolverr in Jackett:

1. Open Jackett web interface
2. Click FlareSolverr API URL at top
3. Enter: http://localhost:8191
4. Save configuration

For specific indexers:

• Edit indexer
• Enable “FlareSolverr” option
• Save changes

API Usage

FlareSolverr provides a REST API for custom integrations:

Basic request:

curl -X POST http://localhost:8191/v1 \
  -H "Content-Type: application/json" \
  -d '{
    "cmd": "request.get",
    "url": "https://protected-site.com",
    "maxTimeout": 60000
  }'

Available commands:

• request.get - GET request to protected URL
• request.post - POST request to protected URL
• sessions.create - Create a persistent session
• sessions.list - List active sessions
• sessions.destroy - Destroy a session

Accessing FlareSolverr

After installation, verify access:

curl http://localhost:8191

Expected response:

FlareSolverr is ready!

Testing with a Protected Site

curl -X POST http://localhost:8191/v1 \
  -H "Content-Type: application/json" \
  -d '{
    "cmd": "request.get",
    "url": "https://example-protected-site.com"
  }'

Troubleshooting

Common Issues

FlareSolverr not starting:

# Check service status
systemctl status flaresolverr@username
 
# View recent logs
journalctl -u flaresolverr@username -n 50
 
# Check Python environment
ls -la /opt/username/lib/python/FlareSolverr/.venv/bin/python3.11

Chromium browser errors:

# Verify Chromium installation (Ubuntu Jammy)
which chromium-browser
 
# Check for missing dependencies
ldd /usr/bin/chromium-browser | grep "not found"
 
# Reinstall FlareSolverr
qb reinstall flaresolverr -u username

Connection timeout errors:

# Increase timeout in service file
sudo nano /etc/systemd/system/flaresolverr@username.service
# Add: Environment="TIMEOUT=120000"
 
# Reload and restart
sudo systemctl daemon-reload
sudo systemctl restart flaresolverr@username

Python version issues:

# Verify Python 3.11
/usr/bin/python3.11 --version
 
# Reinstall Python 3.11 if needed
qb fix python
 
# Reinstall FlareSolverr
qb reinstall flaresolverr -u username

Permission errors:

# Check ownership
ls -la /opt/username/FlareSolverr
ls -la /opt/username/lib/python/FlareSolverr
 
# Fix permissions
sudo chown -R username:username /opt/username/FlareSolverr
sudo chown -R username:username /opt/username/lib/python/FlareSolverr
sudo chown -R username:username /home/username/.config/chromium
 
# Restart service
systemctl restart flaresolverr@username

Performance Optimization

Resource Usage

FlareSolverr uses moderate resources:

• RAM: ~200-500 MB per instance (includes Chromium)
• CPU: Low usage when idle, moderate during challenge solving
• Disk: ~500 MB for application and dependencies

Optimization Tips

Reduce memory usage:

• Limit concurrent requests in automation tools
• Set reasonable timeouts (30-60 seconds)
• Use session management for repeated access

Improve response time:

• Keep service running (avoid cold starts)
• Use persistent sessions for same domain
• Monitor logs for bottlenecks

Security Best Practices

Hardening

For additional security:

# Check that service is localhost-bound
sudo netstat -tlnp | grep 8191
 
# Verify user isolation
ps aux | grep flaresolverr
 
# Monitor for errors
journalctl -u flaresolverr@username --since "1 hour ago"

Resources

Related Applications

FlareSolverr works seamlessly with these automation tools: