13-flaresolverr.md

kstack: book: Centerpoint Home Lab chapter: Media Management page: FlareSolverr (Offline) tags: [flaresolverr, cloudflare, prowlarr, offline, media-management]

Overview

~~empty~~Status: OFFLINE — The FlareSolverr container is present but currently not running (exited 8 weeks ago). It can be restarted when Cloudflare-protected indexers need to be accessed via Prowlarr.

FlareSolverr is a proxy server that bypasses Cloudflare's anti-bot protection for web-based indexers. Prowlarr routes requests for Cloudflare-protected indexers through FlareSolverr, which uses a headless browser session to solve the challenge and return the page content.

Access

FlareSolverr has no web UI. It is accessed internally by Prowlarr via its HTTP API at http://flaresolverr:8191.

Configuration

Image: ghcr.io/flaresolverr/flaresolverr:latest Status: exited

Prowlarr Integration

Once running, configure in Prowlarr:

Settings → Indexers → Add Proxy Type: FlareSolverr Host: http://flaresolverr:8191 Tag: Apply the tag to any Cloudflare-protected indexer

Volumes / Bind Mounts

Host Path Container Path Purpose /home/jeeves/docker/flaresolver /config FlareSolverr config

Notes / Gotchas

FlareSolverr uses a headless Chromium browser. It consumes significant CPU and RAM during challenge solving — resource spikes are normal. Cloudflare regularly updates its bot detection. FlareSolverr may stop working after Cloudflare updates and require an image update. When FlareSolverr is offline, any Prowlarr indexer tagged with the FlareSolverr proxy will fail silently on search — no error surfaced in Sonarr/Radarr. Check Prowlarr indexer status if searches return no results. To restart: docker start flaresolverr or redeploy via Portainer.

Last Updated: 2026-06-16