I've noticed that since the 5.1 release, the ability to set the controller to port 443 using the user interface has been removed:

I'm curious what the reasoning is behind that change.  I package up a Docker image and one of the use cases is to change the ports for the controller's admin ports to 80 & 443 as I am able to control the privileged ports through a sysctl applied to the Docker container.  While I can manually have the ports changed in the container through some other methods, the problem really comes when editing settings in the UI.  A user reported an issue (https://github.com/mbentley/docker-omada-controller/issues/217) where they were not able to save any settings on this screen due to the setting validation getting triggered by the use of port 443.

It would be ideal if the controller was either able to detect the sysctl setting to determine if it is allowed to set privileged ports as a non-root user and set the range accordingly in the UI or just return the ability to set it back to 443.