Hope to find some support or be pointed in the right direction with the following issue.
In SABZBD settings, I set the port to 8888. I can access SABNZBD when I go to 192.168.1.8:8888
For some reason, after the SABNZBD update I ran today, when I want to open SABNZBD from DSM, it refers to port 8443. This is the port for my unifi controller, I run through Docker.
How do I change the reference port in DSM from 8443 to 8888?
Again, in SABNZBD the port is already set to 8888 (unchanged for years)
Thanks!
Synology refers to incorrect port for SABNZBD
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.
Re: Synology refers to incorrect port for SABNZBD
You can't, it's hardcoded in the Synology package. Synology / DSM doesn't allow changing that.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Synology refers to incorrect port for SABNZBD
Thanks for your support.
It used to work well. The SABNZBD button in DSM used to open SABNZBD, so it referred to port 8888.
But since I updated SABNZBD earlier this week, the SABNZBD button in DSM now refers to port 8443 all of a sudden.
So I understand that it is hardcoded in the Synology package, but a SABNZBD update changed it for some reason
Anyone else experiences the same issue?
It used to work well. The SABNZBD button in DSM used to open SABNZBD, so it referred to port 8888.
But since I updated SABNZBD earlier this week, the SABNZBD button in DSM now refers to port 8443 all of a sudden.
So I understand that it is hardcoded in the Synology package, but a SABNZBD update changed it for some reason
Anyone else experiences the same issue?