Install on Unraid

nzbfast is in Community Applications, so on Unraid there is no compose file to write and no folders to create by hand. The template fills in the port, the three paths and the user IDs for you, using the Unraid defaults.

Two registries, one image. The identical image lives on Docker Hub as nzbfast/nzbfast and on GitHub as ghcr.io/nzbfast/nzbfast. The template uses the Docker Hub name. The image is multi-arch, so it also runs on ARM boxes, though Unraid itself is 64-bit Intel and AMD only.

Install it recommended

You need the Community Applications plugin. If your Unraid has an Apps tab, you already have it.

Find it

Apps tab, search nzbfast, then Install. Unraid opens its normal Add Container form with everything already filled in from the template.

Glance over the values

The defaults work as they are. What they mean:

Setting	Default	What it is
Web UI Port	`6789`	Dashboard and the SABnzbd-compatible API. Change the host side only if something already uses 6789.
Config	`/mnt/user/appdata/nzbfast`	Settings and the index database. Keep this on appdata.
Downloads	`/mnt/user/downloads/nzbfast`	Finished files land here. Point it wherever you keep downloads.
Watch	`/mnt/user/downloads/nzbfast/watch`	Drop an `.nzb` in here and it downloads by itself.
PUID / PGID	`99` / `100`	The Unraid defaults, `nobody` and `users`, so downloaded files belong to you and not to root.
TZ	`Etc/UTC`	Your timezone, for example `Europe/London`. Under Show more settings.
API Key	empty	Only needed for Sonarr, Radarr and friends. Also under Show more settings, and you can set it later in the dashboard instead.

Apply

Unraid pulls the image and starts the container. Then carry on to First run below.

Not in Apps yet? The Community Applications catalogue is rebuilt on a schedule rather than the moment a template lands, so a brand-new entry can take a little while to show up. You do not have to wait: add https://github.com/nzbfast/unraid-templates under Docker → Template repositories (bottom of the page) and nzbfast appears in the template dropdown on Add Container straight away, with the same pre-filled values.

First run: add your provider

There is no config file to edit. Open http://YOUR_SERVER_IP:6789, or just click the nzbfast icon on the Docker tab and choose WebUI. A Welcome panel asks for your Usenet server. Enter the host, username, password and connection count from your provider's welcome email and save. It applies immediately, with no restart. Drop an .nzb on the dashboard, or into the watch folder, and it downloads.

Connecting Sonarr / Radarr

nzbfast speaks the SABnzbd API. In your *arr app, add a SABnzbd download client: Host = your server's IP, Port = 6789, API Key = the key from the container's API Key variable, or from the dashboard's Settings page if you set it there. It also exposes the NZBGet JSON-RPC API, so nzb360 and LunaSea connect the same way.

One thing that catches people out. If you left the API Key empty at install time, set one in the dashboard under Settings before you point an *arr app at it. An *arr client with no key, or the wrong key, simply reports that it cannot connect.

Updating

The image is the update channel: nzbfast in a container never swaps its own binary, you move it forward by pulling a newer image. Your settings, queue and downloads live in the folders you mapped, so they survive the swap.

By hand: Docker tab → Check for Updates at the bottom of the page. When nzbfast shows update ready, click its icon and choose Apply Update. Unraid recreates the container with the same settings.
Automatically: Community Applications adds an Auto Update Applications page under Settings, where you can tick nzbfast and let it update on a schedule. You do not need Watchtower or anything else on Unraid.

Check your image tag first. Both of the above assume your container is on nzbfast/nzbfast:latest, which is what the template sets. If you pinned it to a version, say :1.0.3, nothing will ever move it, because a re-pull fetches the tag the container was created with. The Docker tab shows the tag next to the container.

Troubleshooting

It won't start, or stops again right away: the container prints the reason and exits, so it is in the container's own log. Docker tab → click the nzbfast icon → Logs. Over SSH that is docker logs --tail 50 nzbfast. A container that quits a second or two after starting, repeatedly, is usually refusing on purpose rather than crashing, and the log says which case it is.
"Permission denied" or files owned by root: check PUID is 99 and PGID is 100, and that the share you pointed /downloads at is writable by nobody. This is the most common issue, and on Unraid it usually means the defaults were changed.
Can't reach the dashboard: confirm the container is running, and that the host side of the port is what you are browsing to. If something else already uses 6789, change the host side to something free, for example 6889, and browse to that instead.
Downloads are slow, or the array is busy: point /downloads at a cache pool or an unassigned SSD rather than a parity-protected array share. This is a general Unraid write-speed point and is not specific to nzbfast, but it is the single biggest difference you will feel.
Nothing downloads: open the dashboard. If the Welcome panel is still showing, the provider has not been saved yet.
Auto-update never fires: check the container is on the latest tag rather than a pinned version, and that nzbfast is actually ticked on the Auto Update Applications page.

What you need. Any Unraid release with the Community Applications plugin, on 64-bit Intel or AMD. The same image also runs on Synology (guide), TrueNAS SCALE and QNAP Container Station.

nzbfast on Unraid

Install it recommended

Find it

Glance over the values

Apply

First run: add your provider

Connecting Sonarr / Radarr

Updating

Troubleshooting