-
Notifications
You must be signed in to change notification settings - Fork 19
FlareSolverr Prowlarr Integration Guide
If you found this guide helpful and are feeling extra appreciative, consider supporting the channel:
- Donate me a KO-FI: https://www.ko-fi.com/kltechvideos
- Follow on X (Twitter): https://x.com/kltechvideos (Help me beat the algorithm! 😂)
- Subscribe on YT (YouTube): https://www.youtube.com/@kltechvideos
- Checkout the Blog for more cool projects!: https://blog.kltechvideos.co.uk
- Don't forget to let me know what content you are watching or reading on my socials!
This guide explains how to deploy FlareSolverr using Docker and integrate it with Prowlarr to bypass Cloudflare security challenges and captchas.
Images below.
FlareSolverr acts as a proxy server to navigate Cloudflare "Waiting Room" screens. It is best run as a background container.
Add the following to your docker-compose.yml file:
services:
flaresolverr:
image: ghcr.io/flaresolverr/flaresolverr:latest
container_name: flaresolverr
environment:
- LOG_LEVEL=info
- TZ=UTC # Change to your local timezone
ports:
- 8191:8191
restart: unless-stopped
Run this command in your terminal to pull and start the container:
docker run -d \
--name=flaresolverr \
-p 8191:8191 \
-e LOG_LEVEL=info \
--restart unless-stopped \
ghcr.io/flaresolverr/flaresolverr:latest
Once the container is running, you must link it to Prowlarr as an Indexer Proxy.
- Open Prowlarr and go to Settings > Indexers. (Note this is different from the primary list of torrent/usenet indexers. Different screen altogether.
- Click the + (Plus) button to add a new proxy.
- Select FlareSolverr from the list.
- Fill in the following details:
-
Name:
FlareSolverr -
Host:
http://flaresolverr:8191(if using Docker DNS) orhttp://[YOUR-SERVER-IP]:8191 -
Tags: Type
flareand press Enter. 🏷️
- Click Test (you should see a green checkmark) and then Save.
FlareSolverr will only be used for indexers that you specifically tag. This prevents unnecessary overhead for sites that don't use Cloudflare.
- In Prowlarr, go to the Indexers page.
- Find an indexer that frequently triggers Cloudflare blocks (e.g., 1337x or TorrentGalaxy).
- Click the Wrench Icon (Edit).
- Scroll down to the Tags field.
- Add the tag:
flare.
Note: This must match the tag you created in Step 2 exactly.
- Click Save.
-
Logs: Check the FlareSolverr Docker logs. You should see messages like
Browser checking...followed byChallenge solved!when a search is performed. -
Prowlarr: Go to History in Prowlarr. If a search previously failed with a
403 ForbiddenorCloudflareerror and now succeeds, the setup is working perfectly. ✅
Tip
If you are running multiple instances of FlareSolverr for different locations, you can use unique tags like flare-uk or flare-us to route specific indexers to specific proxies.
Images below: