SABnzbd is the Usenet downloader in the Smithflix media stack. It handles queued downloads and post-processing for any workflows routed through Usenet instead of the DelugeVPN torrent path.
This page documents the sabnzbd service. It does not replace the Arr pages that may use SABnzbd as a download client.
- Container:
sabnzbd
- Image:
lscr.io/linuxserver/sabnzbd:latest
- Stack: Smithflix Stack
- Compose path:
/opt/stacks/smithflix/docker-compose.yml
- Docker network:
smithflix_default
- Restart policy:
unless-stopped
- Runtime env keys verified live:
PUID, PGID, TZ
- Health state: healthy on
2026-04-07
- Public hostname:
sabnzbd.better-than.tv
¶ Config and Data Paths
- Config root:
/srv/docker/sabnzbd/config
- Primary config file:
/srv/docker/sabnzbd/config/sabnzbd.ini
- App log directory:
/srv/docker/sabnzbd/config/logs
- Completed downloads mount:
/media/downloads mounted as /media/downloads
- Incomplete downloads mount:
/media/incomplete-downloads mounted as /media/incomplete-downloads
- LAN URL:
http://192.168.0.113:8080
- Public URL:
https://sabnzbd.better-than.tv
- Host port mapping:
8080 -> 8080
¶ Authentication and Secret Locations
- SABnzbd auth, API keys, and server definitions are stored inside
/srv/docker/sabnzbd/config
- Do not store SABnzbd API keys or server credentials in wiki page content
- Public access should remain restricted to trusted users because it is an admin surface with downloader control
- Validate local access on
:8080 before debugging the proxy
- Keep complete and incomplete download paths aligned with the Arr clients that consume them
- If SABnzbd is used by Arr apps, confirm category and path expectations after any storage change
- Treat queue-finished notifications and archive movement as signs of healthy post-processing, not just raw download throughput
¶ Monitoring and Logs
- Docker logging driver is
json-file
- The container healthcheck was healthy on
2026-04-07
- Recent logs showed normal post-processing, queue saves, and archive movement
- App-level logs live under
/srv/docker/sabnzbd/config/logs
¶ Backup and Restore
/srv/docker/sabnzbd/config is inside the documented Duplicati scope- Download payloads under
/media/downloads and /media/incomplete-downloads are operational data, not assumed full backups
- After restore, validate server definitions, API access, and a sample queue item
¶ Failure Modes and Recovery
- Path or permission drift on the complete and incomplete roots will break post-processing or Arr imports
- Public proxy issues can make the UI inaccessible while the LAN port still works
- A healthy container does not guarantee the configured Usenet servers or credentials are valid