Unable to configure SABnzbd within Sonarr, Radarr etc

[enigmatic]

Have YAMS setup in Proxmox LXC, Debian 12. Privileged container. Not using ROOT account.

VPN is setup and working fine.

Within apps like Sonarr and Radarr I've been able to setup QBitorrent. The problem is I cannot connect anything to SABnzbd.

I can browse to SABnzbd and that is configured. I've copied the API key.

When I'm in Sonarr and try and setup the connection as per the guide I just get a spinning wheel on the connection before getting:

Code: Select all

"Test was aborted due to an error: Unable to connect to SABnzbd, Operation timed out"

If I run

Code: Select all

docker ps | grep sabnzbd

I get this:

Code: Select all

c1012f705b45   lscr.io/linuxserver/sabnzbd:latest    "/init"                 42 minutes ago   Up 42 minutes                                                                                                                                                                                                                                                                   sabnzbd

Ports are missing.

Looking within Stacks details, SABnzbd does not have an IP address and is not connected to a network (although as above it's up and I can configure it).

SABnzbd logs show:

Code: Select all

2025-02-20 17:55:57,687::INFO::[SABnzbd:1404] Starting web-interface on :::8080
2025-02-20 17:55:57,687::INFO::[_cplogging:213] [20/Feb/2025:17:55:57] ENGINE Bus STARTING
2025-02-20 17:55:57,813::INFO::[_cplogging:213] [20/Feb/2025:17:55:57] ENGINE Serving on http://:::8080
2025-02-20 17:55:57,814::INFO::[_cplogging:213] [20/Feb/2025:17:55:57] ENGINE Bus STARTED
2025-02-20 17:55:57,814::INFO::[SABnzbd:1443] Starting SABnzbd.py-4.4.1
2025-02-20 17:55:57,829::INFO::[dirscanner:112] Dirscanner starting up
2025-02-20 17:55:57,830::INFO::[panic:239] Launching browser with http://127.0.0.1:8080
2025-02-20 17:55:57,831::INFO::[notifier:157] Sending notification: SABnzbd - SABnzbd 4.4.1 started (type=startup, job_cat=None)
2025-02-20 17:55:57,839::INFO::[zconfig:61] No bonjour/zeroconf support installed
2025-02-20 17:55:57,852::INFO::[ssdp:108] Serving SSDP on 10.23.110.4 as SABnzbd

Sonarr logs show:

Code: Select all

[Error] Sabnzbd: Unable to connect to SABnzbd, Http request timed out 

[v4.0.13.2932] NzbDrone.Core.Download.Clients.DownloadClientUnavailableException: Unable to connect to SABnzbd, Http request timed out
 ---> System.Net.WebException: Http request timed out
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponseAsync(HttpRequest request, CookieContainer cookies) in ./Sonarr.Common/Http/Dispatchers/ManagedHttpDispatcher.cs:line 144
   at NzbDrone.Common.Http.HttpClient.ExecuteRequestAsync(HttpRequest request, CookieContainer cookieContainer) in ./Sonarr.Common/Http/HttpClient.cs:line 157
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Sonarr.Common/Http/HttpClient.cs:line 70
   at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in ./Sonarr.Common/Http/HttpClient.cs:line 128
   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.ProcessRequest(HttpRequestBuilder requestBuilder, SabnzbdSettings settings) in ./Sonarr.Core/Download/Clients/Sabnzbd/SabnzbdProxy.cs:line 197
   --- End of inner exception stack trace ---
   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.ProcessRequest(HttpRequestBuilder requestBuilder, SabnzbdSettings settings) in ./Sonarr.Core/Download/Clients/Sabnzbd/SabnzbdProxy.cs:line 214
   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.GetVersion(SabnzbdSettings settings) in ./Sonarr.Core/Download/Clients/Sabnzbd/SabnzbdProxy.cs:line 89
   at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.TestConnectionAndVersion() in ./Sonarr.Core/Download/Clients/Sabnzbd/Sabnzbd.cs:line 372

Have searched and found other posts elsewhere and tried solutions. Have tried using 127.0.0.1 as address without success and have tried enabling SSL but again, no difference. SABnxbd has been configured as per guide and I've followed all steps as per documentation.

I'm still learning about Docker and Portainer so not sure on what needs doing to fix this or how to fix it.

[rogs]

Hey @enigmatic!

I'm assuming you can enter SABnzbd since you are copying the API key. I'm also assuming you have a VPN. How are you adding it to Sonarr/Radarr? What hostname are you using?

Cheers!

Roger.

[rogs]

I just remembered something! You might need to add your hostname to SABnzbd's Special/host_whitelist configuration, as shown here:

Let me know if that works for you!

[enigmatic]

Hey @enigmatic!

I'm assuming you can enter SABnzbd since you are copying the API key. I'm also assuming you have a VPN. How are you adding it to Sonarr/Radarr? What hostname are you using?

Cheers!

Roger.

Yes, 100% I can get into SABnzbd and go through all the settings and get the API key. Have also double checked that HTTPS is off to be sure it's not causing any issues.

I've tried all manner of ways of trying to configure the connection in Sonarr/Radarr without any success. I've tried the local network IP 1xx.1xx.1.22, I've tried the Local IPv4 address shown within SAZnzbd. Any numeric address times out.

If I try hostname "SABnzbd" I get:

Code: Select all

Test was aborted due to an error: Unable to connect to SABnzbd, Name does not resolve (sabnzbd:8080)

If I try and use gluetun as a last resort (I saw that port 8080 is bound to that), I get:

Code: Select all

Test was aborted due to an error: Unable to connect to SABnzbd, HTTP request failed: [403:Forbidden] [GET] at [http://gluetun:8080/api?mode=get_config&apikey=RANDOMKEYHERE&output=json]

To be honest I've given up now on SABnzbd but I can't for the life of me work out why this doesn't work. I can browse to SABnzbd but nothing else within the same Portainer stack appears to be able to see it.

[enigmatic]

I just remembered something! You might need to add your hostname to SABnzbd's Special/host_whitelist configuration, as shown here:

Let me know if that works for you!

I had a go at trying this but clearly did something wrong as I lost access to both QBittorrent and SABnzbd. Got it back again so will try again after coffee and something to eat

[enigmatic]

OK, looks like I have a working solution now.

Within SABnzbd I had to add the internal Portainer IP of each container I wanted to connect to SABnzbd. I then restarted SABnzbd.

Within Sonarr, add SABnzbd using the internal IP address and the IP and I very quickly have a connection at last.

[brandnewuser]

Hello, I'm having this same issue pretty. Pretty much same setup as well. I changed the address to the internal Portainer IP to connect to Sabnzbd. Issue is, that when either docker or the host PC restart; all internal Portainer IPs are changed. Breaking all my configs. Did you assign static IPs to the container or is there a setting within Portainer to keep address for hosts on the entire network?

[rogs]

@brandnewuser, Don't use docker IP, use the host IP address or the hostnames, like the docs suggest.

If you still want to use the docker IP, set it as static using this: https://stackoverflow.com/questions/394 ... er-compose

[brandnewuser]

I figured it out. I did what you said and changed to the hostname based connections. I had another issue that was enigmatic having of being unable to connect to SABnzbd from radarr or sonarr.

Within your earlier recommendation of adding to SABnzbd Special/Host_whitelist . I took this as putting your hostname for machines connecting to SABnzbd eg. Gluetan, Sonarr, Radarr. But this option is for setting the hostname SABnzbd wants to go by.

TLDR : add SABnzbd to the SABnzbd Special/Host_whitelist. Restart SABnzbd. Do a test connection from radarr to host "sabnzbd" it will connect.

[rogs]

Oh yeah, I forgot to mention that! Sorry. We even have an issue to fix that in the docs: https://gitlab.com/rogs/yams.media/-/issues/10

Well, I'm glad you were able to fix it! Again, sorry for missing that point.

Cheers!

Roger.