One Dashboard to Rule Them All
Managing a self-hosted media server means dealing with a lot of moving parts. Jellyfin handles playback beautifully, but getting content into your library in the first place requires a separate layer of tooling – indexers, search aggregators, and download clients that all need to talk to each other. Most setups end up with a messy tangle of individually configured indexers spread across Sonarr, Radarr, and Lidarr, each pointing to the same sources but maintained independently.
Prowlarr solves that by acting as a centralized indexer manager that syncs directly with your *arr applications. Add an indexer once, and Prowlarr pushes it to every connected app automatically. No more logging into five dashboards to update an API key.
This guide walks through integrating Prowlarr with a Jellyfin-centered media stack, connecting the two systems so your indexers, download clients, and library are all operating from a single source of truth.
Installing Prowlarr and Getting It Running
Prowlarr is best deployed via Docker, which keeps it isolated and easy to update. Pull the image from the official LinuxServer.io repository – it stays consistently maintained and works across most home server setups. A basic docker-compose configuration needs only a config volume, a port mapping (default is 9696), and a PUID/PGID set to match your host user to avoid permission headaches later.
Once the container is up, navigate to http://localhost:9696 in your browser. The first-run wizard asks you to set an authentication method – use Forms-based authentication rather than Basic if you plan to expose this on a local network, since it handles session management more cleanly. Set a strong username and password here even if the server sits behind a VPN, because security hygiene at the application layer is worth maintaining regardless of your network setup.
With Prowlarr running, head to Settings > General and copy your API key. You will need it shortly when connecting your *arr apps. Also take a moment to configure a download client under Settings > Download Clients – this is where you point Prowlarr at qBittorrent, Transmission, or whichever client you are using. Prowlarr can send searches directly for testing purposes without routing through Sonarr or Radarr, so having a download client attached early makes troubleshooting easier.
Adding Indexers and Connecting Your *arr Apps
Indexers live under the Indexers tab in Prowlarr. Click the plus icon and you get a searchable list of supported trackers and Usenet indexers. Public indexers like 1337x or EZTV require no credentials – just select and save. Private trackers will ask for an API key or login credentials depending on how that tracker authenticates. Add every indexer you plan to use here, in one place, and Prowlarr becomes the only application you ever need to update when an indexer changes its URL or rotates an API key.
Connecting Sonarr, Radarr, and Lidarr happens under Settings > Apps. Each app has its own entry type. Click the plus icon, select the correct application, and fill in the local URL and API key for that app. The Sync Level setting controls how aggressively Prowlarr pushes indexer configurations – “Full Sync” is the right choice for most setups because it means any indexer you add or remove in Prowlarr automatically updates in every connected app without manual intervention. After saving, hit the sync button to do an immediate push and verify the connection.
Test the integration by triggering a search inside Sonarr or Radarr. If Prowlarr is wired up correctly, the search results will pull from every indexer you configured, filtered through whatever quality profiles you have set. Failed searches are logged in Prowlarr under the History tab with enough detail to pinpoint whether the problem is a dead indexer, a credential issue, or a query that returned no results.
Wiring Jellyfin Into the Stack
Jellyfin does not connect to Prowlarr directly – its job is library management and playback, not acquisition. The link between Prowlarr and Jellyfin runs through the *arr apps and your download client. When Sonarr or Radarr grabs a file, it drops it into a watched folder that Jellyfin scans. Getting this path mapping right is where most people run into trouble, especially when running everything in Docker with different volume configurations per container.
The cleanest way to handle this is to define a shared media directory on the host and mount it consistently across all containers. Sonarr, Radarr, and Jellyfin should all see the same path inside their containers – something like /media mapped to /mnt/data/media on the host. If Sonarr writes to /media/tv and Jellyfin reads from /data/tv, Jellyfin will never see the new files, and library scans will return nothing. Consistent volume paths eliminate that class of problem entirely.
Inside Jellyfin, set your library directories to match wherever your arr apps deposit finished downloads. Enable automatic library scanning in the Scheduled Tasks section so new content appears without manual refreshes. For a tighter feedback loop, Sonarr and Radarr both support webhooks that can trigger a Jellyfin library scan the moment a download completes – configure this under Connect in each arr app using Jellyfin’s API endpoint and an API key generated from Jellyfin’s Dashboard > Advanced > API Keys.
Keeping the Stack Healthy Over Time
Prowlarr includes a built-in indexer health check system that flags trackers returning errors, timing out, or consistently failing queries. Check this regularly – a dead indexer that stays configured just adds noise to every search without contributing results. Removing it from Prowlarr removes it everywhere simultaneously, which is the entire point of the centralized approach.
Update cadence matters more than most people expect with this stack. Prowlarr, Sonarr, Radarr, and Jellyfin all release updates that sometimes change API behavior or fix indexer parsing issues. Running mismatched versions can cause sync failures that are difficult to diagnose without reading changelogs. If you are using Docker, setting up a tool like Watchtower to auto-pull updated images on a weekly schedule removes most of the manual maintenance burden – though pulling blindly without reading release notes occasionally introduces breaking changes, so a quick weekly check is worth the two minutes it takes.
The real test of whether this setup is working properly is what happens six months in when an indexer goes offline, rotates an API key, or gets replaced by a successor tracker – if you update one record in Prowlarr and every connected application reflects the change within minutes without touching Sonarr, Radarr, or Lidarr individually, the architecture is doing exactly what it was designed to do.
