As noted here I am trying to use a service provided by Ubiquity for managing their devices called UNMS.
I've set it up on my NAS, but have been blocked from connecting to the router from UNMS, and Ubiquity support seemed to think that using non-standard ports (required to avoid conflicting w/Synology services) could be the issue.
I have already set non-starndard HTTP/HTTPS ports on the NAS, but when I try to set UNMS container settings to map to 443/80 for its connections it tells me that the setting conflicts with other ports used by other services.
Is there a way to configure DSM so that it uses alternate ports to 443/80 for it's "other services" (and things won't blow up/get too complicated) so I can use those default ports w/the UNMS instance to see if that solves my connection problem? If the change is feasible but creates a messy management issue I don't want to go that way.
I am not using much in the way of services at the moment, UNMS in Docker, HyperBackup to a second NAS, CloudSync.
Appreciate info and advice.
I've set it up on my NAS, but have been blocked from connecting to the router from UNMS, and Ubiquity support seemed to think that using non-standard ports (required to avoid conflicting w/Synology services) could be the issue.
I have already set non-starndard HTTP/HTTPS ports on the NAS, but when I try to set UNMS container settings to map to 443/80 for its connections it tells me that the setting conflicts with other ports used by other services.
Is there a way to configure DSM so that it uses alternate ports to 443/80 for it's "other services" (and things won't blow up/get too complicated) so I can use those default ports w/the UNMS instance to see if that solves my connection problem? If the change is feasible but creates a messy management issue I don't want to go that way.
I am not using much in the way of services at the moment, UNMS in Docker, HyperBackup to a second NAS, CloudSync.
Appreciate info and advice.