Prowlarr is a centralized indexer management tool, also called an API synchronization hub, that lets you configure all your Usenet indexers and search sources in one place and automatically push them to every app in your arr stack without repeating that setup manually.
If you have ever spent an afternoon entering the same API key into Sonarr, Radarr, Lidarr, and Readarr one by one, you already understand the problem Prowlarr solves. It sits at the center of your home lab’s media automation pipeline, syncing indexer configurations outward to every connected app.
This guide walks you through every stage of a complete Prowlarr setup, from prerequisites and installation to indexer configuration, download client wiring, and ongoing maintenance.
We cover both Docker-based and native installs, Usenet indexer specifics, sync profiles, and how the whole workflow connects into a reliable automation pipeline for archival data, open-source software archives, Linux distributions, and large datasets.
What Prowlarr Does In An Arr Stack
Prowlarr acts as the single source of truth for indexer configuration across your entire arr ecosystem. Instead of managing Newznab and Torznab sources inside each individual app, you define them once in Prowlarr and let automatic sync handle distribution.
Why Centralized Indexer Management Matters
Every app in an arr stack, Sonarr, Radarr, Lidarr, and Readarr, needs to know where to search for content. Without a centralized indexer management tool, you configure the same sources repeatedly in each app, and any change to an API key or URL requires multiple manual edits.
Prowlarr eliminates that. Add an indexer once, and every connected app inherits it automatically. When a Usenet indexer changes its API endpoint, you fix it in one place.
This matters most in active home labs where indexers rotate or credentials expire. The time savings compound quickly as your stack grows.
How Prowlarr Differs From Sonarr, Radarr, And Download Clients
Sonarr and Radarr are collection managers focused on monitoring, renaming, and organizing digital assets after a download completes. They do not manage indexer configuration at scale.
Download clients like SABnzbd handle the actual file transfer. They receive job instructions but have no awareness of where search queries come from.
Prowlarr occupies the layer between search sources and collection managers. It handles the API synchronization hub role exclusively, routing search requests and keeping indexer lists consistent across all downstream apps without touching file organization or download execution.
Usenet Indexers And The Newznab API
Usenet indexers are the actual services that index binary posts on Usenet newsgroups. Prowlarr communicates with them using the Newznab API protocol, a standardized interface that makes querying consistent regardless of the specific provider.
For a home lab focused on archival data and legitimate preservation work, Usenet indexers paired with a Newznab-compatible API represent the most complete and reliable search path available in Prowlarr.
Prowlarr supports generic Newznab entries for any indexer not listed by default, giving you flexibility even with niche or private sources.
Prowlarr Setup Guide Prerequisites
Before the first launch, a few decisions and pieces of information need to be in place. Getting your API keys, privacy setup, and access model sorted in advance prevents having to backtrack through the configuration after install.
What You Need Before You Start
At minimum, you need:
- An active account with at least one Usenet indexer that provides a Newznab API key
- A running instance of at least one arr app (Sonarr or Radarr) with its API key accessible under Settings > General
- A machine, VPS, or NAS capable of running Docker or a native .NET-based application
- Basic familiarity with editing a compose file or running commands in a terminal
If your arr apps are not yet installed, set those up first. Prowlarr’s sync functions require live API endpoints to connect to on initial configuration.
Choosing The Right Usenet Indexers For Your Stack
For home labs focused on preserving archival data, public domain archives, and large datasets, Usenet indexers provide strong retention rates, SSL-encrypted transfers, and reliable completion rates that hold up for long-term archival work.
Private Usenet indexers typically require an account and often an invitation. Public sources have no barrier to entry but typically deliver lower reliability. Plan your indexer mix based on what you actually archive.
Privacy, Authentication, And Access Basics
Run Prowlarr behind a reverse proxy with HTTPS if it is accessible on any interface beyond localhost. The web UI has no SSL termination of its own.
Enable authentication in Settings > General immediately after first launch. Without it, anyone on your local network can add or remove indexers. If you access your home lab remotely, a VPN tunnel to your network is a practical safeguard before exposing Prowlarr to any external address.
Installing Prowlarr On Docker Or Native Systems
Docker is the recommended deployment path for most home lab setups because it isolates Prowlarr from the host system and makes updates predictable. Two well-maintained images exist, and native installation is a practical alternative for users who prefer direct system integration.
Docker Compose With linuxserver/prowlarr
The linuxserver/prowlarr image is the most widely used. A minimal compose block looks like this:
services:
prowlarr:
image: lscr.io/linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000
- PGID=1000
- TZ=America/New_York
volumes:
- /your/config/path:/config
ports:
- 9696:9696
restart: unless-stopped
Set PUID and PGID to match the user that owns your media and config directories. Mismatched permissions are the most common cause of startup failures.
Using hotio/prowlarr
The hotio/prowlarr image uses slightly different environment variable conventions and is preferred by users who already use other hotio containers for consistency across their stack.
services:
prowlarr:
image: ghcr.io/hotio/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000
- PGID=1000
- UMASK=002
- TZ=America/New_York
volumes:
- /your/config/path:/config
ports:
- 9696:9696
restart: unless-stopped
Both images are functionally equivalent for day-to-day operation. The choice usually comes down to which image family the rest of your stack already uses.
Native Installation And First Launch
For Arch Linux, the AUR package prowlarr-bin installs cleanly via an AUR helper:
yay -S prowlarr-bin
sudo systemctl daemon-reload
sudo systemctl enable --now prowlarr
On Debian or Ubuntu-based systems, the official Servarr install script handles dependency management and service registration. After install, enable and start the service with systemctl. Check journalctl -u prowlarr if it does not start as expected.
Accessing The Web UI At localhost:9696
Once the container or service is running, open http://localhost:9696 in a browser. The interface loads immediately with no initial wizard. Your first task is setting authentication under Settings > General before adding any indexers.
If you are accessing Prowlarr from another machine on the network, replace localhost with the host machine’s local IP address.
Adding Indexers And Configuring Sync
The Prowlarr setup workflow follows a clear sequence: add indexers, configure sync profiles, then connect your arr apps. These steps are tightly related, and sync profiles in particular affect how much control Prowlarr takes over each downstream app.
Adding A Usenet Indexer And Entering The API Key
Navigate to Indexers and click the + button. A full list of supported indexers loads. Type to filter by name. If your provider is not listed, select Generic Newznab.
Fill in the required fields:
- Name: A label used across all synced apps (Prowlarr appends
(Prowlarr)automatically) - URL: Your indexer’s base URL; leave blank to use the default
- API Key: Found in your indexer account under Profile or Security settings
- Enable: Checked by default; uncheck to pause without deleting
Click Test before saving. A green checkmark confirms the API key and URL are valid. A failure here almost always means a wrong API key or an incorrect URL.
Tags, Sync Profiles, And Indexer Configuration
Tags let you route specific indexers to specific apps. If you add a tag called usenet-only to a Usenet indexer and apply the same tag in a Sonarr app entry, only tagged indexers sync to that app.
Sync profiles define how aggressively Prowlarr controls downstream apps:
| Sync Level | Behavior |
|---|---|
| Add and Remove Only | Pushes additions and deletions only |
| Full Sync | Prowlarr overrides all indexer settings in the app |
| Disabled | No sync occurs |
Full Sync is the most powerful and the least forgiving. Any manual edits made inside Sonarr or Radarr for a Prowlarr-managed indexer will be overwritten on the next sync.
Connecting Sonarr, Radarr, Lidarr, And Readarr
Go to Settings > Apps and click + to add each app. You need:
- The app’s local URL including port (for example
http://localhost:8989for Sonarr) - The app’s API key from its own Settings > General page
- The Prowlarr server URL as the app would reach it (critical if using a reverse proxy)
Prowlarr immediately attempts a sync after saving. Check the app’s indexer list for entries marked (Prowlarr) to confirm success. Disable the old manually entered versions of those indexers in each app once the synced versions are verified.
Full Sync, Automatic Search, And Interactive Search
Sync profiles also control three search modes per app:
- Enable RSS: Allows Prowlarr-managed indexers to respond to RSS feed polling
- Enable Automatic Search: Permits the app to trigger searches automatically when monitoring criteria are met
- Enable Interactive Search: Allows manual search queries from within the app’s UI
All three are typically enabled in a standard home lab setup. If an indexer has API rate limits, create a custom sync profile with automatic search disabled to reduce query volume.
Connecting Download Clients And Verifying The Workflow
Download clients in Prowlarr serve a specific and limited purpose. Prowlarr does not sync download client settings to Sonarr or Radarr. Those apps manage their own download client connections independently.
SABnzbd For Usenet Downloads
Add SABnzbd to Prowlarr only if you want Prowlarr’s own Search tab Grab button to send NZBs directly to your Usenet download client. This is useful for manual one-off grabs without involving Sonarr or Radarr.
Go to Settings > Download Clients > + and select SABnzbd. Enter the host, port, and API key. Test the connection before saving.
For automated pipeline use, configure SABnzbd as a download client inside Sonarr and Radarr directly. Prowlarr’s own download client entry is supplemental.
Testing Indexer Access And App Connectivity
Under Indexers, use the Test All function periodically to verify every indexer remains reachable. A red X indicates an API failure, an expired subscription, or a changed endpoint.
In each connected arr app, confirm that synced indexers appear under Settings > Indexers and that test queries return results. If an indexer supports only specific content categories, it will only sync to apps that search within those categories.
How Prowlarr Feeds A Media Automation Pipeline
The full workflow moves in one direction: Prowlarr holds the indexer config, arr apps hold the collection logic, download clients hold the transfer queue, and a media server like Jellyfin or Plex reads the organized output.
Prowlarr never touches files directly. Its role is purely API synchronization hub and search routing. That clean separation is what makes the stack maintainable as it grows.
Troubleshooting, Security, And Ongoing Maintenance
Most Prowlarr problems fall into a small number of repeatable categories: bad API keys, misconfigured URLs, sync conflicts, and expired indexer credentials. Systematic checks resolve the majority of issues quickly.
Common API Key And Sync Errors
The most frequent error after adding an app is a URL mismatch. If Prowlarr is behind a reverse proxy with a URL base such as /prowlarr, the Prowlarr server URL entered in each app entry must include that base path. Omitting it causes sync failures that are not always obvious from the error message alone.
API key errors in Sonarr or Radarr connections usually mean the key was copied with a leading or trailing space. Paste into a plain text editor first to verify there is no whitespace.
Indexer Proxies, HTTPS, And Reverse Proxy Considerations
Prowlarr supports indexer proxies (HTTP, SOCKS4, SOCKS5) on a per-indexer basis. These are configured under Settings > Indexers on the specific indexer entry, not globally. They are useful for indexers that block certain IP ranges.
For HTTPS, terminate SSL at your reverse proxy (Nginx, Caddy, or Traefik are common choices). Pass traffic to Prowlarr on port 9696 internally. Set the URL base in Prowlarr’s Settings > General to match the proxy path.
When Searches Fail Or Results Look Incomplete
If an arr app returns no results despite indexers appearing connected, check the category mapping. Prowlarr only syncs an indexer to an app if that indexer supports at least one category the app queries.
Review the Prowlarr logs under System > Logs for specific query failures. The log entries include the exact URL and response, making it straightforward to identify whether the problem is the indexer, the API key, or a category mismatch.
Keeping Prowlarr Reliable Over Time
Schedule periodic checks for:
- VIP expiration dates on paid indexers (Prowlarr can notify you one week before expiry if you enter the date)
- API query and grab limits on indexers with daily caps
- Docker image updates (pull the latest tag on a regular schedule and test in a staging compose if your stack is complex)
- Authentication settings after any reverse proxy change
A healthy Prowlarr instance requires minimal active attention once it is correctly configured, but a brief monthly review prevents slow degradation from accumulating unnoticed.
Frequently Asked Questions
How do I install and access the web interface for the first time?
Deploy Prowlarr using Docker Compose with either the lscr.io/linuxserver/prowlarr or ghcr.io/hotio/prowlarr image, mapping port 9696 on the host. Once the container is running, open http://localhost:9696 in a browser to reach the web UI. Set authentication immediately under Settings > General before proceeding with any indexer configuration.
How do I configure the server URL, port, and base URL correctly?
Prowlarr runs on port 9696 by default. If you add a URL base (such as /prowlarr) in Settings > General for use with a reverse proxy, that full path must be included in every app entry that connects to Prowlarr. Using only the bare IP and port when a base URL is set is the most common cause of broken syncs.
How do I add and test indexers, and what settings are required for each?
Navigate to Indexers, click +, and search for your provider by name or select Generic Newznab for unlisted Usenet sources. Enter the indexer URL and API key, then click Test before saving. A green checkmark confirms a working connection; failures indicate a wrong API key, incorrect URL, or a network issue.
Which indexers are recommended and how do I choose between public and private ones?
For a home lab focused on archival data preservation, private Usenet indexers with Newznab API support offer better retention and reliability than public options. Providers such as Newshosting and Easynews operate their own indexing infrastructure with strong completion rates. Get Newshosting
How do I connect it to Sonarr and Radarr using API keys and sync settings?
In Prowlarr, go to Settings > Apps and add each arr app separately. Enter the app’s local URL, its API key from Settings > General within that app, and choose a sync level. Full Sync gives Prowlarr complete authority over indexer settings in the connected app; Add and Remove Only is more conservative. Save and confirm that indexers tagged (Prowlarr) appear in the app’s indexer list.