Quick setup steps
- Install SABnzbd and open the web UI.
- Add your unlimited provider on Priority 0 with SSL port 563.
- Add an optional fill on Priority 1 if you have a block on another backbone.
- Import a small NZB and confirm Priority 0 does the work.
Before you start
Have one unlimited provider account ready (Newshosting or Eweka are the usual primaries). Optional: a never-expire block on another backbone from the block hub. Install SABnzbd from the official project builds for your OS.
Primary + fill servers
Add your unlimited host as Priority 0 with SSL enabled and port 563. Add the fill host as Priority 1 and enable Optional so SABnzbd only spends fill GB on missing articles. Connections: start around 20-40; raise only if your line and provider plan allow it. Full priority theory: block vs unlimited.
SSL on 563
Never leave production servers on plaintext 119. If 563 is blocked on a network, try 443 where the provider documents it. Privacy primer: SSL port 563.
Priorities and Direct Unpack
Keep fills optional. Enable Direct Unpack when your CPU/disk can handle it so completed jobs extract faster. Categories map download folders for Sonarr/Radarr later - see automation stack.
First test download
Grab a small NZB from an indexer you trust, or use SABnzbd's test download if available. Confirm the Priority 0 server performs the work. Then fail-test a known incomplete NZB to watch the optional fill engage without becoming the default path.
After the first successful grab
Export a miss log for a week before annual prepay or fill blocks. Keep incomplete folders on fast local disk. Confirm optional flags stay optional so fill GB are not burned on articles the primary already completed.
FAQ
- Why is my block draining too fast?
- It is probably not optional, or it shares Priority 0. Fix priorities before buying more GB.
- Can I run NZBGet instead?
- Yes - same server model. Comparison: NZBGet vs SABnzbd.
- Do I need VPN inside SABnzbd?
- No. Use SSL for NNTP. VPN is for other device traffic if you want it.