FlareSolverr supplies Cloudflare challenge solving for Arr and search automation. On Smithflix it is primarily a helper for Prowlarr and related download automation.
This page documents the flaresolverr service. It does not cover every Arr integration that may call it.
- Container:
flaresolverr
- Image:
ghcr.io/flaresolverr/flaresolverr:latest
- Stack: Smithflix Stack
- Docker network:
smithflix_default
- Restart policy:
unless-stopped
- Host port mapping:
8191 -> 8191
- Container health: healthy on
2026-04-07
¶ Config and Data Paths
- Persistent data lives inside the Docker volume mounted at
/var/lib/docker/volumes/.../_data (see /srv/docker/flaresolverr/README-flaresolverr.txt for guidance)
- There is no additional host config directory exposed
- LAN URL:
http://192.168.0.113:8191
- No public proxy hostname is configured on
2026-04-07
- Container also exposes
8192/tcp internally but it is not published
¶ Authentication and Secret Locations
- FlareSolverr uses the default token baked into the LinuxServer image; no separate secret file is mounted
- Authentication is handled via the image configuration, so no host secret leak is expected
- Keep the container running whenever Arr services with Cloudflare-facing indexers need to look up releases
- Check
docker logs flaresolverr after a Prowlarr rate limit or solver failure
- If the JWS tokens expire, restart the container so it can regenerate solver keys
¶ Monitoring and Logs
- Docker logging driver is
json-file
- Health was reported as healthy on
2026-04-07
- Logs appear under the container's stdout; use
docker logs for troubleshooting
¶ Backup and Restore
- There is no state besides the container image and the small volume described in the README
- Restore is essentially a redeploy of the same image; keep the volume intact if you add custom
config.json
¶ Failure Modes and Recovery
- If FlareSolverr is missing, Arr services will see repeated Cloudflare challenges and fail to index content
- The container is light on disk so it's faster to redeploy than to debug deep configuration mistakes