How to run SABnzbd on a seedbox you own

Downloads from Usenet, with a first-run wizard for your provider details. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

This is Cresdock's suggested starting point in its category — the one to pick if you have no reason to prefer another.

What Cresdock does for you with SABnzbd

Its configuration is written before the container ever starts — including the web address it lives at, so SABnzbd generates correct links from the first page load instead of half-working behind a prefix.
Reached through your panel login. There is no second password to invent for SABnzbd and no port to open on your firewall.
Your Downloads and Media folders are already mounted, and they are the SAME folders your other apps see — so files land where the rest of your setup expects them, with no path mapping to work out.
Because it can fill a disk, it is metered against your storage limit and paused if you run out — instead of silently filling the server.
Sonarr, Radarr, Lidarr and Prowlarr hand work to SABnzbd automatically once both are installed, in either order — nothing to add by hand at either end.
Sending something you picked out of NZBHydra2's own search straight to SABnzbd is set up inside NZBHydra2 — that pairing isn't made for you.

Why run SABnzbd yourself

An always-on server downloads on its own schedule rather than yours, and finishes whether or not you are at the machine.

What kind of server SABnzbd needs

Usenet downloads fast enough that the disk and the unpacking are the bottleneck, not the network. Give it room for a download and its unpacked copy at the same time — briefly, both exist.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run SABnzbd

SABnzbd runs wherever Cresdock runs, and the choice is about the machine, not the app:

At home, on hardware you already own. A mini PC, an old desktop or a NAS that can run Debian. Cresdock works behind a home router with no port forwarding and no domain, so SABnzbd is reachable on your own network first and from outside only if you choose.
On a rented server. A small VPS is enough for most apps and is the usual answer when SABnzbd should be reachable from anywhere. The setup guide covers the specs and the one-command install.
Through a provider that runs Cresdock. Hosting companies deploy Cresdock workspaces for their customers, so SABnzbd can come with a server you rent rather than one you set up — ask your provider, or see how providers offer it.

Installing SABnzbd

Put Cresdock on a server
One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.
Pick SABnzbd from the catalogue
Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.
Open it from your dashboard
Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What's left for you to do

Cresdock does not pretend to do the parts that are genuinely yours to decide. After it's running:

Open SABnzbd and enter your Usenet provider's details in its wizard

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  sabnzbd:
    image: lscr.io/linuxserver/sabnzbd:4.5.5-ls250
    restart: unless-stopped
    ports:
      - "8080:8080"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./sabnzbd/config:/config
      - ./downloads:/downloads
      - ./media:/media

And that is the easy half. Still to do:

Install a reverse proxy and write a server block for it
Get a TLS certificate and set up automatic renewal
Create the folders above with the right ownership, or it will not start
Decide what happens when the disk fills, because nothing here will stop it
Repeat all of it for the next app, and again on every server rebuild

On Cresdock, SABnzbd is one click and none of the above exists.

Common questions

Do I need to know Docker to run SABnzbd?

No. Cresdock installs SABnzbd in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. SABnzbd's configuration is written before it first starts, so it opens already set up.

What happens to my files when SABnzbd updates?

Cresdock changes SABnzbd's own configuration only. Your downloads and your media are never touched by an update, a rebuild or a reinstall — that is a rule the software enforces, not a promise in a document.

What happens if I run out of space?

Downloading pauses instead of the disk filling up. You keep your files, your other apps keep running, and you get told what happened in plain words.

Can other people on my server see my SABnzbd downloads?

No. Each account's apps run on that account's own private network, and downloads land in that account's own folders — another user's apps cannot reach your SABnzbd, and nobody's files are mixed with anybody else's.

Can I run SABnzbd at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and SABnzbd is reachable on your own network first. A rented server is only needed when SABnzbd must be reachable from anywhere without a VPN.

Can I remove SABnzbd later?

Yes. Cresdock removes SABnzbd in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what SABnzbd itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: NZBHydra2 · NZBHydra2 · SFTPGo · how SABnzbd connects to your other apps

Before you start: where to rent a server · what it needs to run · Cresdock vs QuickBox · the seedbox panel in full · sell workspaces to your customers