Important or Recent Updates
| Update | Date |
|---|---|
| New guide update for DSM7.2 and Container Manager | 06/05/2023 |
| Moved from UI setup to Project Setup which is more flexible and easier to maintain. | 21/10/2023 |
| Added an addition element to the compose to restrict the container from gaining additional privileges and also umask environment variable | 25/10/2023 |
What is SABnzbd?
SABnzbd is a binary newsreader, it is used to download files from Usenet, and where required will also repair and extract releases. It works on its own or in conjunction with other tools such as Lidarr and Radarr.
Let’s Begin
In this guide I will take you through the steps to get Sabnzbd up and running in Container Manager. We will be using the new Projects (Docker Compose) feature to get this running as it will save you time vs manual setup using the normal UI
In order for you to successfully use this guide please complete the three preceding guides
- Docker, Memory Recommendations and Limitations
- Step 1: Directory Setup Guide
- Step 2: Setting up a restricted Docker user
- Step 3: Setting up a Docker Bridge Network
Folder Setup
Let’s start by getting some folders set up for the containers to use. Open up File Station create the following.
/docker/projects/sabnzbd-compose
/docker/sabnzbd
Container Manager
Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project then on the right-hand side click ‘Create’.
In the next screen we will set up our General Settings, enter the following:
| Section | Setting |
|---|---|
| Project Name: | sabnzbd |
| Path: | /docker/projects/sabnzbd-compose |
| Source: | Create docker-compose.yml |
Next we are going to drop in our docker compose configuration, copy all the code in the box below and paste it into line ‘1’ just like the screenshot.
services:
sabnzbd:
image: linuxserver/sabnzbd:latest
container_name: sabnzbd
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
volumes:
- /volume1/docker/sabnzbd:/config
- /volume1/data/usenet:/data/usenet
ports:
- 8080:8080/tcp
network_mode: synobridge
security_opt:
- no-new-privileges:true
restart: alwaysEnvironment Variables
We are now going to amend some key variables to make sure the container has access to our folders and also knows where we are in the world. Don’t change any other settings other than those I mention.
| Variable | Value |
|---|---|
| PUID | (required) The UID you obtained in the user setup guide |
| PGID | (required) The GID you obtained in the user setup guide |
| TZ | (required) Your timezone wikipedia.org/wiki/List_of_tz_database_time_zones |
Once you have made the edits you can click ‘Next’
You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.
On the final screen click ‘Done’ which will begin the download of the container images and once downloaded they will be launched!
The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.
Firewall Exceptions
(Skip if you don’t have the Firewall configured)
If you have enabled and configured the Synology Firewall you will need to create exceptions for any containers that have a Web UI or have any incoming or outgoing connections. This section covers the basics of how to add these. (Please note this is a generic section and will not show the specific ports used in this guide however it applies in the same way)
Also, I would like to refer people to the great guide on getting the Firewall correctly configured over on WunderTechs site.
Head into the Control Panel> Security > Firewall, from here click Edit Rules for the profile you set up when you enabled the Firewall.
Next click on Create and you will see the screen below. Source IP and Action will be automatically selected to All and Allow, I will leave it up to you as to your own preference on whether you want to lock down specific Source IPs from having access. In this example we will leave as All.
You will now choose ‘Custom‘ and then the Custom button
Now select Destination from the drop-down menu, most web based containers require TCP access but check the guide as it will show the port and protocol. Then add comma separated ports. Then press OK.
Click OK a couple of times to get back to the main screen. You will see by default the new rule is added to the bottom of the list. You must always have your Block All rule last in the list as the rules are applied top down so move your container up.
You have now completed the Firewall changes and can continue with the guide.
Some final steps
SABnzbd will now be running on port 8080 you can connect to it by going to the IP address of your NAS with that port
e.g. 192.168.0.40:8080
Once you have completed the setup wizard, go into the settings and amend your folders to the following
| Setting | Path |
|---|---|
| Temporary Download Folder | /data/usenet/intermediate |
| Completed Download Folder | /data/usenet/completed |
| Watched Folder | /data/usenet/nzb |
If you are using SABnzbd for your download client in the Arrs you will want to add some categories and paths as shown below. When adding SABnzbd to each of the Arrs match up the category in the download client settings, like the example below in Sonarr.
You are now configured to get downloads working, there are quite a few options in the configuration sections of the app that can both improve and hinder performance. These really depend on the capability of your NAS so keep this in mind.
Looking for some help, join our Discord community
If you are struggling with any steps in the guides or looking to branch out into other containers join our Discord community!
Buy me a beverage!
If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me stay hydrated. Plus 10% goes to the devs of the apps I do guides for every year.
Could you include your Sabnzbd sorting methods to automatically move completed movies to /volume1/data/media/movies and tv shows to /volume1/data/media/TV Shows ?
Yes sure thing – I will get the categories into the basic setup section at the end, give me 30 mins.
Hey is your guide explaining this correctly? In your screenshot for categories at the end it says “Relative folders are based on: /mnt/usenet/completed”, so your relative path “movies” then resolves to “/data/usenet/completed/movies”. Maybe you wanted to specify the absolute path “/data/media/movies”?
Hey, the screenshot shows /data/usenet/completed?
https://drfrankenstein.co.uk/wp-content/uploads/2024/06/image-1024×524.png
This is correct
This I’m slightly confused. Is your Jellyfin/Plex library not located in /data/media/movies? If it is, shouldn’t you want any completed downloads (torrent and usenet alike) to be moved to that location? What is the purpose of the path /data/usenet/completed?
Hey, yes the guide is written working on the basis you would also be using it in conjunction with Radarr/Sonarr to manage the organisation and final file moves. If you don’t have them in the mix then yes you can adjust the final paths. Keep in mind you will also need to adjust the mount up a folder level, so Sab has access across into the media folder.
e.g from /volume1/data/usenet:/data/usenet to /volume1/data:/data
This should cover your next comment as well 🙂
Okay. I think I understand what confused me now. Is it the job of sonarr/radarr/prowlarr to move the downloads to the correct folders in /data/media? That wasn’t working on my setup for some reason. It probably has to do with permissions… But this led me to believe that SABnzbd should be configured to put the downloads where Jellyfin/Plex can find them.
I followed your guide for setting up Gluetun and added this and prowlarr underneath. I am able use prowlarr no problem but now radarr wont connect to sabnzbd (hostname). any advice how what i am doing wrong?
Try adjusting Radarr to use the ‘synobridge’ gateway IP of 172.20.0.1 sometimes I find some apps have problems with looking up the container name.
that worked for me thank you. I did have another question / request. do you have any experience adding a jdownloader container to the gluetun stack? I keep getting a hostname and network mode conflict error. when I deleted the hostname entry I got a port publishing error.
Can you share the container you are using I can tweak the compose for you.
I posted on the discord as i think that might be a better spot for discussion.
(: