If you’ve added FlareSolverr to Prowlarr, tested it successfully, and it still shows a Disabled badge - you’re not alone. Even worse, your indexers will still throw the: "Unable to access [site], blocked by Cloudflare Protection" Meanwhile:
  • FlareSolverr container is running
  • The test inside Settings -> Indexers -> FlareSolverr passes
  • You’re pointing to the right path, in this case (in Docker): http://flaresolverr:8191
And yet... Nothing works.

The "Disabled" Badge Does NOT Mean FlareSolverr Is Broken

I spent quite a while trying to find out how to enable. In newer Prowlarr versions, FlareSolverr is added as an Indexer Proxy. That proxy only activates if at least one indexer is assigned to it via Tags. If no indexers use that proxy, Prowlarr shows it as: Disabled That does NOT mean:
  • The container is down
  • The host URL is wrong
  • FlareSolverr isn’t working
It simply means: No indexers are assigned to use it.

Why Your Indexers Still Fail Cloudflare

Even if FlareSolverr tests successfully in: Settings -> Indexers -> FlareSolverr It does not mean your indexers are actually using it - that test only checks if Prowlarr can reach FlareSolverr If you never assign a tag, your indexers continue connecting directly to the website - which gets blocked by Cloudflare.

The Fix: Use Tags

Here’s the simple fix that actually enables it.
  1. Go to Settings -> Indexers -> FlareSolverr
  2. Add a tag. For example: cf
  3. Save
  4. Now open your affected indexer
  5. Go to the indexer settings and find Tags
  6. Add the same tag from before: cf
  7. Save

What Happens After Adding the Tag

Now the indexer is explicitly linked to the FlareSolverr proxy. The “Disabled” badge disappears and Cloudflare errors should stop.