# \[BUG-5735\] Upgrade Bug with AmbientCapabilities **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [March 18, 2022, 5:05pm UTC](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368 "2022-03-18T17:05:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [March 18, 2022, 5:05pm UTC](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368/1 "2022-03-18T17:05:11Z")
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. ---
**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\ **Post date:** [March 18, 2022, 5:23pm UTC](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368/2 "2022-03-18T17:23:08Z")
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 ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [March 18, 2022, 5:52pm UTC](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368/3 "2022-03-18T17:52:28Z")
> [@jcoffman](#): > > Are you able to set the correct ports in the webserver config pages? Did not try, sorry. I just used `gwcmd` once I got past commissioning. ---
**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\ **Post date:** [March 18, 2022, 5:54pm UTC](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368/4 "2022-03-18T17:54:22Z")
Alright, thanks Phil. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 1, 2022, 5:11pm UTC](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368/5 "2022-04-01T17:11:13Z")
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). ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 1, 2022, 5:25pm UTC](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368/6 "2022-04-01T17:25:39Z")
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. (: