![]() So for example if you want sabnzb to be connectable from the outside on port 12345 just start the docker container with -p 12345:8080. ![]() To: linuxserver/docker-sabnzbd PaPaTheGMan Mention Re: Forced port 8080 ( if you want sabnzb to be connectable on a different port, you need to change the way how you launch the docker container. Sonarr still complains that it can't find SABnzbd. Thanks for responding, but that's exactly how I have it set. Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented. As if you're using docker networking, you could just reference sabnzbd as the address then port 8080 and it'll work. I'm not entirely sure how forcing the port to 8080 is breaking Sonarr. To: linuxserver/docker-sabnzbd PaPaTheGMan Comment Re: Forced port 8080 ( #90) This is even though I can directly attach to SABnzbd through the newly assigned port. When I tell Sonarr to find SABnzbd on the new port I attempted to assign, SABnzbd refuses the connection. That server already as an unmovable process taking up 8080. My SABnzbd server is on a different machine than Sonarr. If the forced port 8080 needs to stay, is it possible to add a note in the README explicitly stating that the default port can't be changed? Wouldn't -server 0.0.0.0 also work for binding to all interfaces ( and ), and then if someone wants to change the port they'll be able to do so? I don't see any HEALTHCHECK or something like that configured so I am wondering what would break if you don't use 8080 :). I am curious as to what exactly is the reason the container needs to be forced to use port 8080? That unfortunately is never explained in #2 or #40. So because of the -server 0.0.0.0:8080 argument the default port is always forced to 8080 and you can't change it in the configuration (or rather you can change it, but it'll reverted back to 8080 as soon as you try to apply the change and restart the container). S6-setuidgid abc python3 /app/sabnzbd/SABnzbd.py \
0 Comments
Leave a Reply. |