SABnzbd Forums

I'm sorry but I can't be of much help.. We have used that port for ages, it only conflicts if you have a manual package installed that also uses that port. Despite the manual text, for all other users it seems to work.
Maybe indeed try to see which other package is on port 8080 by just navigating to http://your-nas:8080

Just bumping this as I have the same problem. Can I grab the spk from somewhere and modify it somehow? I just need to change the default service port. The makefile has it specified as 8080 but I'm not sure how to manually install with this change.

https://github.com/SynoCommunity/spksrc ... d/Makefile

Unifi won't play nice on another port. And running sabnzbd in docker seems to be bugged in that I keep getting a "datadir" instead of the requested mount locations.

Maybe easiest to just ditch the Synology Community version of SABnzbd and opt for the Docker version where I can control the ports directly to employee monitoring software and transparently. It seems like there is some configuration w/ the Synology Community package that 'holds / reserves' 8080 even if the app doesn't eventually use it (which is also why it wouldn't let me install the package until I had turned off my Docker that was using it.

Yes, the DSM package system requires you to reserve the port. It's hardcoded so can't be changed after the package is compiled and signed.