Support Forum

I am able to modify the container startup to pass 127.0.0.1:8080 to the --server parameter (I cannot use 0.0.0.0 with any port).

I have started the container and published the port, yet using curl from the container host, there is no response?

Does anyone have any suggestions?

Actually, further research into this reveals I have the same issue as github linuxserver/docker-sabnzbd #82

ipv6 is disabled on my host (and that won't change).

It looks like there is a facility to alter the containers runtime behavior that I am looking into now.

I am trying to run 4.2.1 from the linuxserver/sabnzbd container using podman in Alma Linux. When I start the container I get the following error: Fatal error: Unable to bind to port 8080 on localhost. Some other software uses the port or SABnzbd is already running. I don't have anything running on p...

How does one apply a configuration file directive to the service? Are there facilities to force sabnzbd to look for a global config file for example?

Thanks.