# Cannot start gateway after upgrade to 8.1.16 **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [April 26, 2022, 9:06am UTC](https://forum.inductiveautomation.com/t/cannot-start-gateway-after-upgrade-to-8-1-16/58855 "2022-04-26T09:06:12Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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 26, 2022, 12:27pm UTC](https://forum.inductiveautomation.com/t/cannot-start-gateway-after-upgrade-to-8-1-16/58855/2 "2022-04-26T12:27:23Z")
Looks like you are trying to use the standard HTTP & HTTPS ports with a non-root user. It can be done, but only by adding a clause to your service file. See this topic: > [@\[BUG-5735\] Upgrade Bug with AmbientCapabilities](https://forum.inductiveautomation.com/t/bug-5735-upgrade-bug-with-ambientcapabilities/57368): > > 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 (stan… --- _[View the full topic](https://forum.inductiveautomation.com/t/cannot-start-gateway-after-upgrade-to-8-1-16/58855)._