Skip to content

NZBGet 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

In the guide I will be taking you through the steps to download and setup NZBGet in Docker on a Synology NAS, this makes some assumptions that you know your way around the DSM interface.

On to the Guide

The first step is to download the NZBGet container, we will be using the one provided by Linuxserver.io and can be found within the Docker interface on the registry tab.

You will just need to enter NZBGet as the search term and the top result should be the Linuxserver image.

nzbget01
Searching for the container

Right click on the image and click Download, you can track the progress in the image tab

nzbget02
Downloading the container

Setting up a Docker User for NZBGet 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.

Setting up the NZBget container

Back in the image menu highlight the NZBGet container and click on Launch. This will open up the setup wizard.

newnzbget01

Tick the ‘Enable Auto Restart’ this will ensure the container starts up automatically if you reboot.

newnzbget02

Volumes / Mounts

We are now going to set up the folders or shares we want to mount to NZBget

Under the ‘Docker’ share create a folder called ‘NZBGet’ 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.

It should look like the screenshot below.

Port Settings

Next click on Port Settings, we can now setup which port we want to use for NZBGet, by default the local port will say ‘Auto’ we need to change this to our own value otherwise the port will change every time you restart. I recommend keeping the same port numbers as the original container.

You do not need to change any settings in Network or Links

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 the environment tab enter the details as shown in the screenshot, but change them to whatever yours were noted as.

You can find a list of timezones here https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

PGID, PUID and TimeZone

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

You can now launch the Docker image as it is ready to roll. Open up a new tab and go to the IP of your NAS and the port number you chose.

The default login details are:
Username = nzbget
Password = tegbzn6789

nzbget09

Also as a few comments have requested this is the PATHS setup within NZBGet itself, you will notice the only path you will need to change is the MainDir to ‘media/downloads’

Docker Compose

You can use the below code saved as nzbget.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-nzbget:
    image: linuxserver/nzbget:latest
    container_name: nzbget
    environment:
      - PUID=YOURPUID
      - PGID=YOURPGID
      - TZ=Europe/London
    volumes:
      - /volume1/docker/nzbget:/config
      - /volume1/downloads:/media/downloads
    ports:
      - 6789:6789/tcp
    restart: unless-stopped
sudo docker-compose -f /volume1/docker/nzbget.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

66 Comments

    • Dr_Frankenstein Dr_Frankenstein

      Hey

      I am using an 1815+ with 16GB RAM and have gone the opposite way, it looks like the 1520+ should also have plenty of horse power to actually increase some of the values they suggest, they are more for the lower end Arm based series, you should not have any performance issues.

      Here are the items I changed to make more use of the hardware.

      Download Queue
      – Article Cache = 500MB
      – Direct Write = On
      – Write Buffer = 2048
      – PostStrategy = Balanced

      Check and Repair
      – ParCheck = Auto
      – ParScan = Full (I did this as found sometime this fixed files that failed at first)
      – ParQuick = Yes
      – ParBuffer = 2000 (I have lots of RAM so may as well use it)

      • ranova ranova

        thank you, your comments and guides are so helpful to me, a synology/linux noob!

  1. Ray Ray

    thanks, but how do you allocate more shared memory in the docker container?

    • Dr_Frankenstein Dr_Frankenstein

      It will just use whatever it needs unless you specify a limit

Leave a Reply

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