How to avoid incomplete NZBs
Short answer
To avoid incomplete NZBs, grab recent posts from an indexer that keeps up, keep one main account with long retention such as Newshosting or Eweka, and add a second server on a different backbone once failures keep repeating, for example a ViperNews 500 GB block for $13.99. Let SABnzbd abort jobs that cannot be repaired so Sonarr can grab a replacement.
An incomplete download almost always comes down to one of three things. A takedown removed part of the post, the NZB points at a post older than your provider keeps, or the upload was broken to begin with. Most of that goes away if you grab from an indexer that tracks fresh posts, keep one main account with long retention, and add a second server on another backbone once the failures keep coming back. For the rest, let SABnzbd drop hopeless jobs early so you lose minutes instead of hours.
Start with the error message
Open the failed job in the History tab of SABnzbd. What it says there tells you which fix to use.
| What SABnzbd reports | What it means | What to do |
|---|---|---|
| Missing articles, repair failed | Parts are missing on every server you use, and there is not enough par2 repair data to cover the gap | Try another NZB for the same release. If this happens a lot, add a second backbone. |
| Aborted, cannot be completed | SABnzbd noticed early on that too much was missing | Same as above. The abort saved you the download time. |
| Unpack failed or password needed | The archive is damaged or locked | Your provider is not to blame. Pick another NZB and check your free disk space. |
| Login or connection error | Wrong username, password, port or SSL setting | Fix the server entry. Port 563 needs SSL switched on. |
When the error is about the archive rather than missing parts, how to open RAR and PAR files explains what those files are for.
Before you grab
- Compare the post age with the retention. Retention is how long a provider keeps posts. In our data, checked 2026-11-07, Newshosting keeps 6,658 days, Eweka 6,654, the Base IP brands 1,600 to 6,000 depending on the brand, ViperNews more than 4,500, XS News 4,000 and Usenet.Farm 3,000. Anything older is gone from that server.
- Use an indexer that keeps up. A good indexer removes or flags posts once they go incomplete. See best NZB indexers.
- Prefer NZBs that come with par2 files. Without repair data, a single missing part ruins the whole job.
- If one release has several NZBs, try the newest repost first. It has had less time to pick up takedowns.
Settings that save you time
- In SABnzbd, go to Config, Switches and turn on Abort jobs that cannot be completed. SABnzbd then stops the moment it knows a repair cannot work.
- In the same section, set the action for encrypted RAR files to abort, so a locked archive does not clog your queue.
- In Sonarr and Radarr, leave failed download handling on with redownload enabled. A failed job then sets off a search for another copy.
When a second server is worth it
Add one when recent posts keep failing and other NZBs for the same release fail as well. It has to run on a different backbone from your main account, or it will be missing the same parts. These prices come from our data:
- ViperNews 500 GB block: $13.99, never expires.
- Usenet.Farm 500 GB block: €15.
- NewsDemon on UsenetExpress: $0.50 a month for three months, then $30 every 15 months.
Give it priority 1 and keep your main server at priority 0. Do you need multiple providers? lists the pairs that work.
What does not help
- More connections. They affect speed, not which articles exist.
- A VPN. It changes the route your traffic takes, not the files on the server.
- A second account on the same backbone. Newshosting plus UsenetServer is missing the same parts twice.
If a job has already failed, fix incomplete Usenet downloads takes you through it step by step.
FAQ
- Is it the indexer or the provider?
- Try two NZBs for the same release. If both fail on missing articles, the post is damaged on your provider. If one of them works, the first NZB was the problem.
- Do old posts fail more often?
- Yes. They may have passed the retention limit, and they have also had more time to pick up takedowns.