🟡 Setup SABnzbd — Automated Usenet Downloader
Deploy SABnzbd on Ubuntu — the classic Usenet download automation tool that fetches NZBs, downloads, verifies, repairs, and unpacks completely hands-free.
📦 Resources & Setup Scripts
Grab the automated bash script from GitHub to follow along with the video.
Quick Install:
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/downloads/sabnzbd/sabnzbd-ubuntu.sh
chmod +x sabnzbd-ubuntu.sh
sudo bash sabnzbd-ubuntu.shTutorial Steps
1 Download the Script
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/downloads/sabnzbd/sabnzbd-ubuntu.sh2 Make it Executable
chmod +x sabnzbd-ubuntu.sh3 Run the Installer
The script installs Docker if needed, then starts the linuxserver/sabnzbd container with config, downloads, and incomplete-downloads volumes under /root/docker/sabnzbd.
sudo bash sabnzbd-ubuntu.sh4 Access the Web UI
Open your browser and complete the first-run wizard (choose a language and add your Usenet provider):
http://<your-server-ip>:8117Ports Used
| Port | Purpose |
|---|---|
| 8117 | Web UI (container port 8080) |
Overview
SABnzbd is the longest-running open-source Usenet download client, built in Python and controlled entirely through a web UI — here published on port 8117 (container port 8080). You feed it NZB files (indexes of Usenet articles) and it does everything else: downloads from your provider over SSL, verifies the parts, repairs damaged archives with par2, unpacks RAR/ZIP sets, and moves the result into /downloads. Incomplete jobs live in a separate /incomplete-downloads volume so half-finished data never pollutes your library. Its API is the glue of the *arr world — Sonarr, Radarr, and Lidarr all drive SABnzbd natively.
Why Use It
Usenet downloads come from your provider's servers at full line speed over an encrypted connection — no peers, no seeding, no ratio to maintain. SABnzbd turns that into a zero-touch pipeline: an NZB goes in, a verified and unpacked folder comes out. Compared to NZBGet (now community-maintained), SABnzbd has the friendlier UI, first-class Sonarr/Radarr integration, and a scheduler, category system, and scripting hooks that have been refined for over 15 years.
When You Need It
Who Should Use It
Real Use Cases
Main Features
How to Use After Installation
Security Best Practices
Ports and Firewall Notes
The web UI is published on host port 8117, mapping to port 8080 inside the container — restrict it to your LAN or VPN and use a reverse proxy for anything public. Unlike BitTorrent clients, SABnzbd needs no inbound peer ports at all: it only makes outgoing SSL connections to your Usenet provider (typically port 563 or 443). That makes it firewall-friendly — nothing to forward on your router.
Backup and Maintenance
Common Mistakes
Troubleshooting
Alternatives
NZBGet is the classic lightweight alternative, written in C++ and now community-maintained — a good fit for very low-power hardware. For BitTorrent instead of Usenet, qBittorrent and Transmission (both in this Academy) fill the same download-client slot. Prowlarr manages your indexers across all of them, and tools like Jellyseerr sit on top for request management.
When Not to Use It
Without a paid Usenet provider subscription (and usually an indexer account), SABnzbd has nothing to download — if you only use BitTorrent, use qBittorrent or Transmission instead. On severely RAM-starved devices NZBGet's C++ footprint may fit better than SABnzbd's Python runtime. And for plain HTTP/FTP file fetching, Aria2 is the right tool, not a Usenet client.
PrismaTechWork Professional Help
PrismaTechWork provides end-to-end infrastructure services — from initial deployment and security hardening to ongoing monitoring, automated backups, and dedicated support.
Frequently Asked Questions
What do I need before SABnzbd is useful?
Two subscriptions: a Usenet provider (server access, e.g. Newshosting, Eweka, UsenetExpress) and usually an NZB indexer that supplies the .nzb files. SABnzbd is the machinery between them — it downloads what the NZB describes from your provider's servers.
Where do I find the SABnzbd API key?
Config → General → Security section shows both the full API key and a restricted NZB key. Sonarr, Radarr, and mobile apps use the full API key together with the server IP and port 8117.
Why does SABnzbd use two download folders?
Jobs in progress live in /incomplete-downloads; only after verification, repair, and unpacking does the result move to /downloads. This keeps partial data away from importers like Sonarr, and it is why the incomplete volume needs generous free space.
Is Usenet downloading faster than torrents?
Usually, yes. Downloads come straight from your provider's servers over SSL and typically saturate your line with enough connections, regardless of how many peers a torrent would have. There is also no seeding phase — when a job finishes, you are done.
How do I connect SABnzbd to Sonarr and Radarr?
In each app: Settings → Download Clients → + → SABnzbd. Enter the server IP, port 8117, the API key from Config → General, and a category (tv or movies). Create the same categories in SABnzbd under Config → Categories first.