docker.recipes

Prowlarr Indexer Manager

intermediate

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

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.

Key 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

Common Use Cases

  • 1Centralizing indexer management across multiple *arr applications in a home media server
  • 2Automating access to private torrent trackers that use Cloudflare protection
  • 3Managing indexer credentials and API keys from a single interface
  • 4Setting up media automation for users in regions with restricted torrent site access
  • 5Monitoring indexer performance and identifying failing or slow trackers
  • 6Streamlining indexer configuration for users running Sonarr, Radarr, and Lidarr simultaneously
  • 7Bypassing 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

For development & testing. Review security settings, change default credentials, and test thoroughly before production use. See Terms

docker-compose.yml

docker-compose.yml
1services:
2 prowlarr:
3 image: linuxserver/prowlarr:latest
4 container_name: prowlarr
5 environment:
6 - PUID=1000
7 - PGID=1000
8 - TZ=${TZ}
9 volumes:
10 - prowlarr_config:/config
11 ports:
12 - "9696:9696"
13 restart: unless-stopped
14 networks:
15 - prowlarr-network
16
17 flaresolverr:
18 image: ghcr.io/flaresolverr/flaresolverr:latest
19 container_name: flaresolverr
20 environment:
21 - LOG_LEVEL=info
22 - LOG_HTML=false
23 - CAPTCHA_SOLVER=none
24 - TZ=${TZ}
25 ports:
26 - "8191:8191"
27 networks:
28 - prowlarr-network
29
30volumes:
31 prowlarr_config:
32
33networks:
34 prowlarr-network:
35 driver: bridge

.env Template

.env
1# Prowlarr
2TZ=UTC

Usage Notes

  1. 1Prowlarr at http://localhost:9696
  2. 2FlareSolverr at http://localhost:8191
  3. 3Add FlareSolverr as indexer proxy
  4. 4Syncs indexers to *arr apps
  5. 5Manages all indexers centrally

Individual Services(2 services)

Copy individual services to mix and match with your existing compose files.

prowlarr
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
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

Quick Start

terminal
1# 1. Create the compose file
2cat > docker-compose.yml << 'EOF'
3services:
4 prowlarr:
5 image: linuxserver/prowlarr:latest
6 container_name: prowlarr
7 environment:
8 - PUID=1000
9 - PGID=1000
10 - TZ=${TZ}
11 volumes:
12 - prowlarr_config:/config
13 ports:
14 - "9696:9696"
15 restart: unless-stopped
16 networks:
17 - prowlarr-network
18
19 flaresolverr:
20 image: ghcr.io/flaresolverr/flaresolverr:latest
21 container_name: flaresolverr
22 environment:
23 - LOG_LEVEL=info
24 - LOG_HTML=false
25 - CAPTCHA_SOLVER=none
26 - TZ=${TZ}
27 ports:
28 - "8191:8191"
29 networks:
30 - prowlarr-network
31
32volumes:
33 prowlarr_config:
34
35networks:
36 prowlarr-network:
37 driver: bridge
38EOF
39
40# 2. Create the .env file
41cat > .env << 'EOF'
42# Prowlarr
43TZ=UTC
44EOF
45
46# 3. Start the services
47docker compose up -d
48
49# 4. View logs
50docker compose logs -f

One-Liner

Run this command to download and set up the recipe in one step:

terminal
1curl -fsSL https://docker.recipes/api/recipes/prowlarr-indexer/run | bash

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

Community Notes

Loading...
Loading notes...

Download Recipe Kit

Get all files in a ready-to-deploy package

Includes docker-compose.yml, .env template, README, and license

Ad Space