Managing Media Indexers Without the Chaos
Running a self-hosted media server like Jellyfin is satisfying right up until indexer management becomes a second job. By default, apps like Sonarr, Radarr, and Lidarr each maintain their own separate indexer lists – meaning if you add a new tracker or update credentials, you repeat that process across every single app. Prowlarr solves this by acting as a single indexer hub that syncs automatically to all your *arr apps and, with a bit of configuration, makes Jellyfin’s automated library refreshes part of the same workflow.
The setup requires Docker or a direct install, a working Jellyfin instance, and a basic comfort level with editing config files or web UIs. Nothing here demands advanced Linux knowledge, but you do need to know where your apps are running and how to reach their web interfaces.
This guide walks through connecting Prowlarr to your *arr apps, configuring it to notify Jellyfin on new content, and keeping the whole stack synchronized without manual intervention.
Installing Prowlarr and Getting It Running
If you are already running Jellyfin through Docker Compose, Prowlarr slots in cleanly alongside it. Add the following service block to your existing docker-compose.yml file. Use the lscr.io/linuxserver/prowlarr:latest image, map port 9696 on the host to 9696 in the container, and mount a config volume so settings persist across restarts. Set PUID and PGID to match the user running your other media containers – mismatched permissions are the most common reason Prowlarr cannot write its own config or communicate with sibling containers.
Once the container starts, navigate to http://your-server-ip:9696 in a browser. Prowlarr will prompt you to set an authentication method on first launch – use a username and password rather than leaving it open, even on a local network. After logging in, head to Settings > General and copy the API key shown there. You will need this key later when linking Prowlarr to your other apps. The interface itself is minimal by design: the real value comes from the indexers you add and the apps you connect, not from anything Prowlarr does on its own screen.
Adding indexers works through Indexers > Add Indexer. Prowlarr supports both Torznab and Newznab protocol indexers, along with a built-in catalog of pre-configured public and private trackers. Search for the tracker you want, enter your credentials if it is a private site, and test the connection before saving. For public indexers, no credentials are needed – just select and save. Each indexer you add here will later be pushed automatically to every connected *arr app, which is the entire point of the exercise.
Connecting Prowlarr to Sonarr, Radarr, and Jellyfin
With indexers in place, the next step is telling Prowlarr which apps should receive them. Go to Settings > Apps and click the plus button. You will see a list of supported applications including Sonarr, Radarr, Lidarr, Readarr, and Whisparr. Select the app you want to connect, then enter its local URL – typically something like http://sonarr:8989 if you are using Docker networking with named services, or the IP and port if not. Paste in that app’s own API key, which you will find under that app’s Settings > General page. Set the sync level to Full Sync so Prowlarr pushes all current and future indexers automatically, then save and trigger a manual sync to confirm it works. Repeat this for each *arr app in your stack.
Connecting Jellyfin itself is handled differently because Jellyfin is a media player and library server, not a download manager. Prowlarr does not send indexers to Jellyfin – instead, you configure a notification connection so that when Sonarr or Radarr finishes processing a download, Jellyfin gets triggered to scan and update its library without waiting for its scheduled refresh interval. In Prowlarr, go to Settings > Connect, add a new connection, and select Webhook. Point the URL to Jellyfin’s library scan endpoint: http://your-jellyfin-ip:8096/Library/Refresh?api_key=YOUR_JELLYFIN_API_KEY. Set the trigger to fire on download or import events. Jellyfin’s API key is found under Dashboard > API Keys in the Jellyfin admin panel.
A cleaner alternative is setting this webhook at the Sonarr or Radarr level rather than through Prowlarr, since those apps know exactly when a file has been moved to its final location. Go to Settings > Connect in Sonarr or Radarr, add a Jellyfin connection using the same API key method, and choose the On Import and On Upgrade events. This way Jellyfin rescans only when there is actually new content to show, rather than on every Prowlarr event. Both approaches work – the Sonarr and Radarr method is more precise. If your Jellyfin library occasionally shows missing content or stale metadata even after downloads complete, a misconfigured or missing webhook here is almost always the reason.
Keeping Everything in Sync Long-Term
Once the initial configuration is done, Prowlarr handles indexer propagation automatically. Add a new tracker in Prowlarr and it appears in Sonarr and Radarr within minutes, no manual entry required. Remove a dead indexer and it disappears from all connected apps on the next sync cycle. This is where the setup pays for itself over time – tracker availability is inconsistent, and maintaining identical lists across four or five apps manually is how configuration drift starts.
One thing worth building into your routine: check Prowlarr’s indexer health status periodically under System > Status. Prowlarr runs automated tests against each indexer and flags ones returning errors, returning no results, or timing out. A tracker that was working six months ago may have changed its URL structure, rotated its API key requirement, or simply gone offline. Prowlarr surfaces these failures clearly, so you can replace or update indexers before your *arr apps start failing silently on searches. Pair this with a self-hosted monitoring tool – Uptime Kuma works well for watching whether Prowlarr’s port is even responding – and you have visibility into the stack without logging into each service individually.
On the Jellyfin side, set your library scan interval to something reasonable like every 24 hours as a fallback, relying on the webhook for real-time updates. Over-frequent automated scans put unnecessary load on the metadata providers Jellyfin contacts for artwork and descriptions – TheMovieDB and TheTVDB both rate-limit aggressive scrapers. If you run a large library with multiple users, this matters more than it seems at first.
The full stack – Prowlarr feeding Sonarr and Radarr, those apps pushing completed downloads to your media folders, and the webhook firing a Jellyfin rescan the moment a file lands – runs entirely without manual input once configured. The only ongoing decision is which indexers to trust and how aggressively to search, and that is a question no amount of automation can answer for you.
