Unable to connect to SABnzbd (Docker install)

Hi, I just bought a DS920+ and installed DSM 7 and Docker.
Then SABnzbd and Sonarr containers.
I’m new to Docker, but both SAB and Sonarr are running and can be reached in my browser.
However when in Sonarr I try to connect to SAB I get following error message:
Test was aborted due to an error: Unable to connect to SABnzbd, Error: ConnectFailure (Connection refused): ‘http://localhost:8080/api?mode=get_config&apikey=XXXXXXX&output=json
I setup the SAB container with:
docker run -d --name=sabnzbd
-p 8080:8080
-p 9090:9090
-e PUID=1026
-e PGID=100
-e TZ=Europe/Amsterdam
-v /volume1/docker/sabnzbd:/config
-v /volume1/data/complete:/downloads
-v /volume1/data/incomplete:/incomplete
–restart always
ghcr.io/linuxserver/sabnzbd
In Sonarr SSH has NOT been checked

Can anybody tell me what i did wrong? Thanks!

Localhost is just the docker container itself. Not the device

Also you’re paths are not great

See
https://wiki.servarr.com/docker-guide

Or trash’s guide linked within

containers cannot access other containers on the same host via the hosts ip address/name, or their host ports, they can only communicate via their docker network ip address/hostname and actual ports.

try using http://sabnzbd:8080 in sonarr (youve named the container so it should be able to find it that way, and the actual port is 8080)

I tried this address as host in Sonarr to connect to SABnzbd as Download Client. When testing it gave: must be valid Host without http://
So I tried as host: sabnzbd:8080, but this gave the same error.
SABnzbd Host says in General tab it listens to ::
But Sonarr doesn’t accept this either.
Now what?

tried as Host: sabnzbd and port 8080, gave following: Test was aborted due to an error: Unable to connect to SABnzbd, DNS Name Resolution Failure: 'sabnzbd’

WOW!
Guys, i found it! For Host I had to use the IP of my NAS.
Thanks for your help :slightly_smiling_face:

But now I have no Root Folder and cannot add any in in Media Management…
Any Idea?

Permissions and ownership - likely from following a poor guide

glad to see you didn’t even bother looking at the docker guide or trash’s guide.

Sorry Bakerboy, but I did and will again re permissions and ownership…

@bakerboy448
Thanks for pointing me to https://trash-guides.info/How-to-setup-for/Synology/
I deleted all the crap I had from other guides and started all over with a clean Docker and File Station.
It’s amazing how great it all works now!
This guide should be at the top of Google Search and I can recommend it to everybody who’s new to Docker.
thanks again!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.