Prices checked 11 Nov 2026 15 providers · 9 backbones

Guide

Usenet automation setup

Indexers, Prowlarr and Sonarr/Radarr, and how NZB files end up in SABnzbd.

Short answer

First get one manual download working in SABnzbd with a single Priority 0 provider. Then add one indexer, then Sonarr or Radarr, and Prowlarr only once several apps need the same indexer keys. Automation can only repeat what your provider is able to complete. Failed downloads point to the provider or the backup server, while failed imports point to categories, paths or permissions.

An automation setup, often called the automation stack, sends NZBs to your newsreader for you. It cannot put articles back on a server that has lost them. Sonarr, Radarr, Lidarr and Prowlarr simply repeat whatever your provider setup already does, at scale. So if your Priority 0 server is missing a Message-ID because of a takedown or retention, every automatic attempt at that post fails until an optional backup on a different backbone can supply it. Get one manual download working before you switch on monitoring for a whole library.

Components

  • Indexers are Newznab-style sites that publish NZBs. They do not store the articles themselves.
  • Prowlarr or NZBHydra2 gives you one place for indexer keys, caching and rate limits.
  • Sonarr, Radarr and Lidarr watch for the titles you asked for, grab an NZB, then rename and file the result.
  • SABnzbd or NZBGet does the actual downloading, talking NNTP to your providers.

Most people put this together back to front. They connect five indexers to a single Highwinds account and then read the red rows as a search problem, when the provider should have been checked first. Choose your main account from the provider comparison table, and leave the block comparison for later, when you know you need a backup.

Recommended wiring

  1. Set up your providers in SABnzbd, a main account plus any optional backups, using the SABnzbd guide.
  2. Add your indexers in Prowlarr and sync the apps from there, so the keys live in one place.
  3. Point Sonarr or Radarr at SABnzbd's API using its host, port and API key.
  4. Use categories so finished downloads land in the root folder each app expects.
  5. Complete one manual grab before you set a dozen series to monitored.

If your hardware cannot handle SABnzbd, NZBGet works with the same setup, and NZBGet versus SABnzbd compares the two. Whichever you use, the category names must match on both sides. When a download finishes in SABnzbd's default folder while Radarr watches a movies category, it looks like a failed grab, but the only problem is the folder.

Indexers versus providers

When a release is older than your provider's retention, how long it keeps files, no indexer can rescue the download. That is why the backbone and the backup come before quality profiles. A 6,600-day Highwinds or Eweka main account covers a different archive from a 1,600-day budget tier or a 3,000-day Dutch block, and the backbone map shows which is which. Adding indexers without adding a second network just gives you more pointers to articles you already cannot download.

To start, one or two indexers you are happy to keep paying for are enough. A third one helps when a title never shows up at all. It does nothing when an NZB starts and then dies on missing articles. Those two problems appear as different lines in the history, and each one calls for spending money in a different place.

What the failure text is asking you to fix

When Sonarr or Radarr keeps reporting a failure, read the exact wording. "Download failed", or a queue full of missing articles, points to the provider, the NZB, or a backup that is either not optional or not on another backbone. "Unable to import" after a finished download points to paths, permissions or a category. A different indexer will not fix a permissions error, and a new folder layout will not bring back a Message-ID.

Check that SSL is on port 563 and that the backup is optional and on a different backbone. If your DMCA main account keeps losing new posts, a backup under NTD takedown rules can help, and DMCA versus NTD explains why. Two Highwinds brands in your server list do not count. Easynews next to Newshosting will not complete anything Newshosting already missed.

Quality profiles that insist on the biggest release from day one turn every miss into a chain of failures. Start with a narrower profile and widen it once three manual grabs have imported cleanly. The time to buy a backup is after a week of SABnzbd history, not on the day you install Prowlarr.

A minimum setup, in order

You do not need every app on day one. Begin with a working SABnzbd download on Priority 0, add one indexer, then Sonarr or Radarr, and bring in Prowlarr once more than one app needs the same keys. If you would rather skip automation entirely, a web reader works too, as described in best for beginners. That web reader is still just a client on one network, though, so you still have to make the backbone decision.

Prowlarr does not need to be installed before Sonarr, which can hold an indexer key on its own. Prowlarr becomes worth it when Sonarr and Radarr would otherwise each keep a copy of the same list. One trap to avoid: syncing Prowlarr into a SABnzbd that has no categories yet sends everything to the default folder and breaks importing. Create the category first.

First Sonarr connection, without a library import

  1. In SABnzbd, create a category called tv and point it at the folder Sonarr will use.
  2. In Sonarr, add SABnzbd as the download client with its base URL, API key and that category.
  3. Add a single series by hand and run a search, then wait for the download to finish.
  4. Check the import path and file permissions before you add anything else.
  5. Switch monitoring on only after three manual grabs have ended up in the right folder.

Radarr works the same way with a movies category. Avoid pointing two apps at one category unless you want them fighting over the same files. Lidarr can wait, since you do not need a music library to prove your Usenet setup works.

FAQ

Can automation fix a bad provider choice?
No. Automation repeats a good setup more often. It cannot create articles a backbone has already deleted.
How many indexers do I need?
Start with one or two you trust. Only add more once you have counted titles that never appear, not articles that fail halfway through a download.
SABnzbd or NZBGet for this stack?
Either one works. Most desktop and NAS users choose SABnzbd for its interface. Use NZBGet when memory is tight.
Does Prowlarr have to come before Sonarr?
No. Sonarr can store an indexer key by itself. Prowlarr is useful when several apps should share the same keys.
When do I add fill to an automated setup?
Once a week of SABnzbd history shows regular misses on Priority 0. The backup should be an optional block on another backbone, not a second unlimited account on the same one.