Skip to content

NZBHydra2 in Docker on a Synology NAS

In this guide I will be taking you through the steps to download and setup NZBHydra2 in Docker on a Synology NAS, this makes some assumptions that you know your way around the DSM interface and have already read one of my previous guides.

Added Docker Compose details03/05/2021

NZBHydra2 combines all your various indexers into a single search site, this can then be fed into Radarr, Sonarr etc. This means you only need to update the single application whenever you want to add a new indexer rather than each one individually.

Downloading the container

So first up we need to grab the container as per my other guides we are using the Linux|Server version as these work great.

Open up Docker within DSM and navigate to the ‘Registry’ section and search for Hydra in the keyword box. Right click and download the Linux|Server version. When it asks which version number you want to use just choose latest this will ensure the container updates to new versions when they are released.


If you now go to the ‘Image’ section you will see the container downloading.


Setting up a Docker User for Hydra 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 container

Back in the ‘Image’ menu highlight the NZBHydra container and click on Launch. This will open up the setup wizard.

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


On the ‘Volume’ tab you need to add the paths to where you want to keep the config files


Next is the ‘Port Settings’ tab you will need to change the Auto setting to either the identical port number 5075 or change it to a custom one if you want to. This is the port you will use to access the Hydra container.


Last up is the PGID and PUID that we made note of earlier in the guide.


Click on OK to get back to the main menu and then click on next, tick the ‘Run this container after the wizard has finished and hit ‘Apply’

The container should now start up, this can be seen in the ‘Container’ tab as the RAM and CPU usage should fluctuate as it starts, its worth giving it a minute or so on its first launch just in case it needs to download any updates during boot. You should then be able to access the interface via your Synology IP and the port number you chose earlier.

Docker Compose

You can use the below code saved as hydra.yml to do the entire process above in one quick command via SSH.

version: "3.2"
    image: linuxserver/nzbhydra2:latest
    container_name: nzbhydra
      - TZ=Europe/London
      - /volume1/docker/hydra:/config
      - 5076:5076/tcp
    restart: unless-stopped
sudo docker-compose -f /volume1/docker/hydra.yml up -d --remove-orphans
Published inDockerSynology


  1. Nathan Nathan

    I am getting stuck at the step “On the ‘Volume’ tab you need to add the paths to where you want to keep the config files” I made a docker/nzbhydra folder and can direct it there, but the \config says it’s an incorrect value…

    • Nathan Nathan

      After reinstalling Docker I was able to get past this step but I came across another issue. In the Environment tab there were already some things listed in there. I left them there and added the puid and pgid and after setup tried launching. Nothing. I deledet that setup and then I did the process over again but took out all the other things in the Environment tab, and added the puid and pgid again. Still nothing. What could be wrong?

      • Dr_Frankenstein Dr_Frankenstein

        Leave the other environment variable where they are as they are used. Would be good to get a screenshot of your settings to trouble shoot. Ping me an email

  2. en en

    Why are you creating new users for each application when Docker containers are already limited to the application running and its permissions?

    • Dr_Frankenstein Dr_Frankenstein

      Hey, while it may be overly cautious to have an individual user for each container you reduce the potential access of that container, so if someone manages to breach the application it is running even if they manage to escalate the permissions in the container they will not get any higher than the users permissions on the host.

      Number 2 on this blog post probably explains it better.

      I may tweak this post as in reality I created a single user with just the permissions required to access my media for Sonarr/Radarr etc

  3. Thomas Jespersen Thomas Jespersen

    I just want to mention that it seems you should install “nzbhydra2” now (also from linuxserver). There is also a “hydra2” image which linuxserver say is deprecated.

    • Dr_Frankenstein Dr_Frankenstein

      Thanks for pointing that out, I am still running the Hydra2 image. You tend to set these up and they just work. I will get this changed and on my personal setup


    Please, can you explain how to do this:
    “I always use the Docker folder and then a sub-directory for all configs.”

    • Dr_Frankenstein Dr_Frankenstein

      When you install Docker it will create a shared directory, I just make subfolders within this for each container. This makes backups super easy

  5. Chad Chad

    Sorry for the delay in getting this posted after we spoke on IRC. Here’s what information I gathered on it, and how to get around it.

    It would seem it’s an issue with the Synology Docker app not showing all of the updates that are available, talked about in link 1 below. When you try to download it prompts, 10 is the latest I see yet if you look here at link 2 below, you’ll see it’s not the latest. What you have to do is SSH into your Synology, and execute sudo docker pull linuxserver/hydra and it will automatically pull the latest and the problem I mentioned in the earlier post will be solved.



    • Dr_Frankenstein Dr_Frankenstein

      Thanks for getting back, this is great information. I am going to add this to the end of the guide.

  6. Chad Chad

    I’ve followed the guide and am unable to apply updates as they are released. The following is seen in the logs.

    error: Your local changes to the following files would be overwritten by merge:

    followed by the reference to quite a few files

    Please, commit your changes or stash them before you can merge.

    After some digging I’ve found that the only way to apply updates is to manually delete the files and running git pull from a terminal.


    • Dr_Frankenstein Dr_Frankenstein

      I actually have the same issue and have not tried to fix it as everything seems to be working as it should. I think this is a problem with the container. I am always in the Linux|Server IRC channel I will see if they can shed any more light

      • Chad Chad

        Thanks, that’d be great!

  7. chris chris

    Hi, I followed the guide and everything is working, except nzbhydra is only available on the local port, not the container port and the local port changes every time.. Any suggestions to get this to work on the container port?

    • Dr_Frankenstein Dr_Frankenstein

      For hydra I think I just set the both to the same ports

  8. kwartet kwartet

    Thank you for the guide. Although it’s mostly the same process every time, I still appreciate the guide(s)! Working out all the paths needed can be difficult by yourself. I have not heard of this application before, certainly gonna give it a try. Thank you and keep up the good work!

    • Dr_Frankenstein Dr_Frankenstein

      No problem they are pretty much the same each time but was thinking people would like to be following something specific to there needs.

  9. Sapan Parikh Sapan Parikh

    Gerat Post Dr, Frankenstein! Did you have a guide for Plex?

    • Dr_Frankenstein Dr_Frankenstein

      It’s in the works as I am just working out some issues with the install, as some of the ports clash with the default ones used by Audiostation.

      • Sapan Parikh Sapan Parikh

        nice! will keep an out for it..

      • Angelus Angelus

        PMS would be great, i want to use it as a database of course, i don’t think with transcoding it would be fast enough but with an player like infuse i think it will work great.

        Thx for all the hard work, your site helped me a lot how it works and understanding why it’s so much better.

Leave a Reply

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