Hey guys,
so I installed sabnzbd via a guide from rapidseedbox using docker on a Pi (cannot post the link because I am new).
My problem is that i have also an unifi controller installed on the PI and I cannot use port 8080 because Unifi is using it. When I try to get to the web interface via localhost:8080 I always get redirected to the Unifi controller web interface.
Also there was no sabnzbd.ini file created so I cannot change the port.
My questions are:
1) How can I change the port?
2) Why was there no sabnzbd.ini file created?
Thank you for your help.
No access to webinterface - no config.ini after installation [Docker]
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
- Newbie
- Posts: 2
- Joined: February 11th, 2024, 11:28 pm
Re: No access to webinterface - no config.ini after installation
If you run in Docker, you can just change the port map from the Docker command line. I know for sure that linuxserver.io image and the hotio ones have that option. You can just map the internal 8080 to external 8081 for example.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 2
- Joined: February 11th, 2024, 11:28 pm
Re: No access to webinterface - no config.ini after installation [Docker]
Hey there,
thank you very much. I already kind of suspected that I've messed up the port mappings while doing the configuration of the docker container. It's working now
Thank you and have a good day.
thank you very much. I already kind of suspected that I've messed up the port mappings while doing the configuration of the docker container. It's working now
Thank you and have a good day.