Skip to content

Setting up SABnzbd in Docker on a Synology NAS

UpdateDate
Added Docker Compose details
Added new folder mappings to ensure atomic moves and Hard-linking
03/05/2021

This is the first part of a series showing you how to setup Usenet Automation using Docker on a Synology NAS.

Setting up a Docker User and Obtaining the PGID and PUID

In previous versions of this guide we used your default admin account for each container, this is not very secure so please now follow the separate setup guide and then head back here

Downloading the Container

In the majority of my guides I use the containers made by Linux|Server, these have very good documentation and are very well maintained so should any issues arise there is a group of people to ask, plus these work really well on Synology.

Open up Docker within DSM and navigate to the ‘Registry’ section and search for sabnzbd in the search box. Right click and download the Linux|Server version.

When it asks which version number you want to use just choose latest

Setting up SABnzbd 

Head into the Image tab of the left of the window, select the Sabnzbd image and  click on ‘Launch’ in the section at the top of the window.

The initial screen you are greeted with allows you to change the container name and resource restrictions, In this case I am leaving this all at its default.

Click on Advanced Settings, on the first screen you see enable auto restart as this will mean SABNZBD will automatically start up if you ever reboot your NAS.

Volumes / Mounts

We are now going to set up the shares we want to mount. SABNzbd only needs access to two folders.

Under the ‘Docker’ share on your Diskstation create a folder called ‘sabnzbd’ this is important as your configuration files will be stored here.

You will notice there is a consistent mount path for each of the folders across all my guides this is important as Docker will see all of your individual folders as one consistent filesystem rather than separate volumes. This will mean you should see much faster file moves (aka Atomic Moves) and also if you are using torrents it means you can enable hard-links

Port Settings

The port settings are extremely important, do not leave them to Auto as you will have to look up the port number every single time the container is restarted and it will screw with all your other containers as they will not be able to talk to each other.

Local Port = 8080
Container Port = 8080 (SAB’s Non SSL Port)

Local Port = 9090
Container Port = 9090 (SAB’s SSL Port)

Press Next..

Environment Variables (PGID, PUID and Timezone)

Next we are going to setup a couple of Environment variables this is the user details we took note of earlier in the guide, this allows the Docker image to have the right access to the shares we just added. In addition we are also required to set the timezone for the container you can find a list of zones on wikipedia https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

In the environment tab enter the details as shown in the screenshot, but change them to whatever yours were noted as.

PGID, PUID and TimeZone

Click OK and this will take you back to the summary screen we saw earlier.

Almost done

Now the container has started head to you NAS IP address and port you provided earlier in the guide, in this case 8080. You will need to start the config of SAB.

After entering your service providers details you must change the completed and temporary download folders the following.

If you skip this step your downloads will end up being stored within the container rather than your downloads directory we mounted to /media/downloads.

Docker Compose

You can use the below code saved as sabnzbd.yml to do the entire process above in one quick command via SSH. Ensuring you change the variables to your own media paths.

version: "3.2"
services:
  linuxserver-sabnzbd:
    image: linuxserver/sabnzbd:latest
    container_name: sabnzbd
    environment:
      - PUID=YOURPUID
      - PGID=YOURPGID
      - TZ=Europe/London
    volumes:
      - /volume1/docker/sabnzbd:/config
      - /volume1/downloads:/media/downloads
    ports:
      - 8080:8080/tcp
      - 9090:9090/tcp
    restart: unless-stopped
sudo docker-compose -f /volume1/docker/sabnzbd.yml up -d --remove-orphans

Throw me some bits

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running the site, it could even buy me a beer 🙂

  • Bitcoin
  • Ethereum
  • Tether
  • Xrp
  • Polkadot
  • Binance coin
  • Litecoin
  • Bitcoin cash
  • Dogecoin
  • Tron
  • Monero
  • Omisego
Scan to Donate Bitcoin to bc1qfznx5kxad9k9z5t9y79mkm9ukfexan9a6wrzl0

Donate Bitcoin to this address

Scan the QR code or copy the address below into your wallet to send some Bitcoin

Scan to Donate Ethereum to 0x162fc7781D3C6c6f27197A3A92567b5DAF258f19

Donate Ethereum to this address

Scan the QR code or copy the address below into your wallet to send some Ethereum

Scan to Donate Tether to 0x162fc7781D3C6c6f27197A3A92567b5DAF258f19

Donate Tether to this address

Scan the QR code or copy the address below into your wallet to send some Tether

Scan to Donate Xrp to rKGpNHetksTn4dgwgpiTkg8JM4uJ3J6pam

Donate Xrp to this address

Scan the QR code or copy the address below into your wallet to send some Xrp

Scan to Donate Polkadot to 153iRH61nXQZUXMveZxCmYyzjf1cWYVnxpHpfifoNchQuXbY

Donate Polkadot to this address

Scan the QR code or copy the address below into your wallet to send some Polkadot

Scan to Donate Binance coin to bnb14ye5rju74u5ythneaum2rjvp8eqep6wq8flghx

Donate Binance coin to this address

Scan the QR code or copy the address below into your wallet to send some Binance coin

Scan to Donate Litecoin to LfNfer3aSqLx4p8KfbbkT96ArXLXLDPxoD

Donate Litecoin to this address

Scan the QR code or copy the address below into your wallet to send some Litecoin

Scan to Donate Bitcoin cash to qrc7scd2drzsd7kywpsjfklvkmm26fqc2vd7uyvdx9

Donate Bitcoin cash to this address

Scan the QR code or copy the address below into your wallet to send some Bitcoin cash

Scan to Donate Dogecoin to DCwbNzfYHx22MDSyEVLWgfjxziYHtcgwAM

Donate Dogecoin to this address

Scan the QR code or copy the address below into your wallet to send some Dogecoin

Scan to Donate Tron to TL1Q3vY9mHnDMedHRyU8ERUAY8SzJ4FXiV

Donate Tron to this address

Scan the QR code or copy the address below into your wallet to send some Tron

Scan to Donate Monero to 45qwFr42XiA8egC5z2HdSQ2FzzP9VR1MvD5Sicg4EhGvdvTutx9GsF6DeU8DHAsTZy2ShBERjCB5rdy8iQ9CFnFu9Z6Adgw

Donate Monero to this address

Scan the QR code or copy the address below into your wallet to send some Monero

Scan to Donate Omisego to 0x162fc7781D3C6c6f27197A3A92567b5DAF258f19

Donate Omisego to this address

Scan the QR code or copy the address below into your wallet to send some Omisego

Published inDockerSynology

60 Comments

  1. HHawk HHawk

    Thank you for this tutorial. Very appreciated. Upgraded my XPEnology last weekend and redid the whole setup for everything (time consuming). Before, on the old NAS, I used software packages to install Sabnzbd, Sonarr, Radarr, etc. I always had some kind of permission warnings.

    Now with the new XPEnology NAS I also started to use Docker GUI in Synology to set things up. Working very good and easy so far (after a few mistakes).

    The only downside when running SABnzbd in Docker GUI is that you are forced to use port 8080. You cannot change it to something else. It always resets to 8080. This doesn’t happen with Sonarr or Radarr. With those applications you can change the port to something else and it sticks.

    I am guessing it’s because the way SABnzbd is started from the package: 2021-02-22 13:52:39,987::INFO::[SABnzbd:1162] Arguments = “/app/sabnzbd/SABnzbd.py” “–config-file” “/config” “–server” “0.0.0.0:8080”

    Is there a workaround for this by any chance? I don’t like using default ports to be honest.

    Thanks in advance.

    Regards,
    HHawk

    • Dr_Frankenstein Dr_Frankenstein

      Hey, looks like you comment was stuck in the Spam filter!

      You should be able to map any port you want via the docker interface (see the screenshot above), it’s been quite a long time since I used SAB (about 4 years now!) so just to be 100% I re-downloaded it to test it out

      I setup all the basics and used port 8000 > 8080 and 9000 > 9090 they seemed to stick just fine including in between restarts of the container.

  2. JayFlow JayFlow

    I managed to launch sabnzbd but only with the non SSL port. When I try to launch him using the SSL port, it just won’t start. Is it less secure to access nzb only via the SSL port ? Does sabnzbd use the SSL port (563) when it’s downloading even if I lauch it with the non SSL port ? The connection parameters in sabnzbd for my news host are correct and use the 563 SSL port.

    • Dr_Frankenstein Dr_Frankenstein

      This is purely the port for the front end Web interface, nothing to do with the actual connection to your provider. So if you are just accessing SAB from within your home network the non SSL port is fine.

      • JayFlow JayFlow

        Thank you.
        Everything worklike a charm.

  3. For some reason I’m unable to start the program in my browser. I tried both ports but it does not work. Strange because the steps are similar to the Sonarr guide but I was able to get that to work.

    Double check you did everything the same way as it’s easy to make a small error when you are doing these for the first time.

Leave a Reply to ZAch Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.