# Prowlarr Indexer Manager

> Prowlarr indexer manager and proxy for Sonarr, Radarr, Lidarr, and more.

- Category: Media & Entertainment
- Difficulty: intermediate
- Components: prowlarr, flaresolverr
- Tags: prowlarr, indexer, torrent, usenet, arr-stack
- Source: https://docker.recipes/media/prowlarr-indexer

## Overview

Prowlarr is an indexer manager that serves as a centralized hub for managing torrent trackers and Usenet indexers across the entire *arr stack ecosystem. Originally developed to solve the problem of maintaining indexers separately across Sonarr, Radarr, Lidarr, and other automation tools, Prowlarr supports over 500 indexers and provides automatic synchronization capabilities that eliminate the need for manual configuration across multiple applications.

This stack combines Prowlarr with FlareSolverr, a proxy server that solves Cloudflare and DDoS-GUARD challenges automatically. Many modern indexers and torrent sites protect themselves with these anti-bot measures, which can block automated requests from Prowlarr. FlareSolverr acts as an intermediary, using a headless browser to bypass these protections and ensure reliable access to protected indexers.

Media automation enthusiasts and self-hosted media server operators will find this combination essential for maintaining a robust download automation pipeline. Rather than configuring indexers individually in each *arr application and dealing with Cloudflare blocks manually, this stack provides centralized management with automatic bypass capabilities, making it ideal for users running comprehensive media automation setups with multiple *arr applications.

## Features

- Support for 500+ torrent trackers and Usenet indexers with automatic updates
- Native synchronization with Sonarr, Radarr, Lidarr, Readarr, and Whisparr applications
- Cardigann definition support for adding custom indexers not included in the default list
- Automatic Cloudflare and DDoS-GUARD challenge solving through FlareSolverr integration
- Built-in search testing and indexer health monitoring with detailed statistics
- Historical tracking of search requests and indexer performance metrics
- Automatic indexer propagation to connected *arr applications when new ones are added
- Proxy support for indexers requiring VPN or geographic restrictions

## Use cases

- Centralizing indexer management across multiple *arr applications in a home media server
- Automating access to private torrent trackers that use Cloudflare protection
- Managing indexer credentials and API keys from a single interface
- Setting up media automation for users in regions with restricted torrent site access
- Monitoring indexer performance and identifying failing or slow trackers
- Streamlining indexer configuration for users running Sonarr, Radarr, and Lidarr simultaneously
- Bypassing geographic restrictions on indexers through proxy configuration

## Prerequisites

- Minimum 384MB RAM available (128MB for Prowlarr, 256MB for FlareSolverr headless browser)
- Ports 9696 and 8191 available and accessible from *arr applications
- Understanding of indexer types (public/private torrents, Usenet providers)
- Valid indexer accounts and API keys for private trackers or Usenet providers
- Basic knowledge of *arr stack applications and their indexer requirements
- Sufficient storage for indexer definitions and search history logs

## docker-compose.yml

```yaml
services:
  prowlarr:
    image: linuxserver/prowlarr:latest
    container_name: prowlarr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=${TZ}
    volumes:
      - prowlarr_config:/config
    ports:
      - "9696:9696"
    restart: unless-stopped
    networks:
      - prowlarr-network

  flaresolverr:
    image: ghcr.io/flaresolverr/flaresolverr:latest
    container_name: flaresolverr
    environment:
      - LOG_LEVEL=info
      - LOG_HTML=false
      - CAPTCHA_SOLVER=none
      - TZ=${TZ}
    ports:
      - "8191:8191"
    networks:
      - prowlarr-network

volumes:
  prowlarr_config:

networks:
  prowlarr-network:
    driver: bridge
```

## .env

```bash
# Prowlarr
TZ=UTC
```

## Usage notes

- Prowlarr at http://localhost:9696
- FlareSolverr at http://localhost:8191
- Add FlareSolverr as indexer proxy
- Syncs indexers to *arr apps
- Manages all indexers centrally

## Troubleshooting

- FlareSolverr timeout errors: Increase CAPTCHA_SOLVER timeout or switch to 'hcaptcha-solver' if encountering complex challenges
- Prowlarr cannot connect to FlareSolverr: Verify both containers are on the same Docker network and FlareSolverr is accessible at http://flaresolverr:8191
- Indexer sync failing to *arr apps: Check that Applications are properly configured in Prowlarr settings with correct API keys and URLs
- High memory usage by FlareSolverr: Set LOG_HTML=false and reduce concurrent sessions by limiting indexer test frequency
- Private tracker login failures: Ensure indexer credentials are current and account hasn't been disabled for inactivity
- Search results not appearing in *arr apps: Verify indexer categories are properly mapped and indexers are enabled in both Prowlarr and target applications

