I upgraded a system from v7.9 to v8.1.15 this morning and ran into an annoyance. The system runs on the default HTTP and HTTPS ports but with the standard “ignition” service user name. This is possible by adding AmbientCapabilities=CAP_NET_BIND_SERVICE to the [Service] section of the SystemD unit file.
After upgrade, instead of just running as expected, I was diverted to the ports page of Commissioning. That page was served up from the standard ports, pre-filled with the running values (standard ports), but would not accept them. It insisted that it wasn’t allowed, even though it was already working.
I had to change to the typical 8088/8443 port pair to get past that. Then I could change them back with gwcmd.sh.
It was annoying.
Not running as root is highly recommended, and using the standard ports makes everyone’s life a little easier. The combination is not forbidden. Please fix this.
Hey Phil,
Im opening a ticket for this. It definitely should be supported, Are you able to set the correct ports in the webserver config pages?
Also, as a workaround for those that find this thread: the ports could be suppled as env properties (GATEWAY_HTTP_PORT, GATEWAY_HTTPS_PORT, and GATEWAY_GAN_PORT). The default GAN port is 8060
1 Like
Did not try, sorry. I just used gwcmd once I got past commissioning.
This is fixed for 8.1.17 (we no longer try to ‘disallow’ ports, and instead let you set whatever, with a last-minute check if we can bind them from the server before committing any settings).
1 Like
FWIW, I did try setting via the gateway config page instead of using gwcmd on the second upgrade I did for that customer, and it worked fine. So, just the commissioning page. However, I like the idea of test-binding, even for the regular config page. I hope the test accounts for Ignition already being bound to those ports. (: