SABnzbd Forums

Hey guys,

Putting my hair out on this one. I had a really old version of SAB running in docker (3.2 maybe?). I connect to from sonarr and radarr using the container name. For the sake of being brief, I upgraded to 4.1 and it appears that my listening host is forever locked to "::" rather than 0.0.0.0 and now sonarr and radarr are getting 403 errors.

Sab logs show the same, that its denying the request.

If I roll back to 3.2, using host 0.0.0.0, everything works as it should, except id have to reconfigure all of my settings.

what can I do here?

The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.

So ... do you access via Sab or IP?

It probably also reports an error text, which one is it?

sander wrote: ↑October 21st, 2023, 12:57 pm The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.

So ... do you access via Sab or IP?

I can access it yes. Looks like in the parameters of SAB are being controlled by a Python script. Is this expected?
Parameters: "/" "--config-file" "/config" "--server" "0000"

I see this in the Web UI of SAB. I wonder if the new version id defaulting to ::

safihre wrote: ↑October 21st, 2023, 1:26 pm It probably also reports an error text, which one is it?

WARNING a minute ago Refused connection with hostname "sabnzbd" from: ::ffff:172.18.0.2 [Radarr/3.0.0.3891 (ubuntu 20.04)]

Which Docker image do you use?
In any case, it's a safety feature and somewhere it should have shown you this link (or if you Google the error message) where you can find the solution
https://sabnzbd.org/wiki/extra/hostname-check.html

safihre wrote: ↑October 21st, 2023, 2:25 pm Which Docker image do you use?
In any case, it's a safety feature and somewhere it should have shown you this link (or if you Google the error message) where you can find the solution
https://sabnzbd.org/wiki/extra/hostname-check.html

Im using linuxserver's image.

I did google the error message and the wiki says this has been present since 2.3. My current settings work with 3.2, so I assumed that hostname validation was not my issue. In any case, I added 'sabnzbd' hostname which was listed in the error message, and its working now using version 4.1

I found it odd that Radarr and Sonarr would be presenting 'their' hostname as 'sabnzbd' so it just added to the confusion

Thanks a bunch.

I think what changed is probably something in the networking of the Docker image, since they changed quite a lot in the Linuxserver base image over all those years. The hostname check hasn't changed indeed.