# Ignition-Gateway.service failed **URL:** \ **Category:** Ignition\ **Created:** [January 1, 2024, 12:58pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-service-failed/83652 "2024-01-01T12:58:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Shivam\_Mathur](https://avatars.discourse-cdn.com/v4/letter/s/f6c823/32.png) [@Shivam\_Mathur](https://forum.inductiveautomation.com/u/Shivam_Mathur)\ **Post date:** [January 1, 2024, 12:58pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-service-failed/83652/1 "2024-01-01T12:58:02Z")
I tried to use this gwcmd to change port from 8088 to 80 as [described here](https://docs.inductiveautomation.com/display/DOC79/Gateway+Control+Utility#GatewayControlUtility-LaunchingGCU) --- "gwcmd --port 80" But after, this command "gwcmd --info" gives me "No response from Gateway", and the server can no longer start. Here are the logs: ```auto ubuntu@ip-172-31-xx-xxx:~$ systemctl status Ignition-Gateway.service × Ignition-Gateway.service - Ignition-Gateway Loaded: loaded (/etc/systemd/system/Ignition-Gateway.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2024-01-01 12:24:47 UTC; 30min ago Process: 2325 ExecStart=/usr/local/bin/ignition/ignition.sh start sysd (code=exited, status=1/FAILURE) CPU: 3.740s Jan 01 12:24:42 ip-172-31-xx-xxx systemd[1]: Starting Ignition-Gateway... Jan 01 12:24:42 ip-172-31-xx-xxx ignition.sh[2325]: Starting Ignition-Gateway... Jan 01 12:24:47 ip-172-31-xx-xxx ignition.sh[2325]: Waiting for Ignition-Gateway....... Jan 01 12:24:47 ip-172-31-xx-xxx ignition.sh[2325]: WARNING: Ignition-Gateway may have failed to start. Jan 01 12:24:47 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Control process exited, code=exited, status=1/FAILURE Jan 01 12:24:47 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Failed with result 'exit-code'. Jan 01 12:24:47 ip-172-31-xx-xxx systemd[1]: Failed to start Ignition-Gateway. Jan 01 12:24:47 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Consumed 3.740s CPU time. ubuntu@ip-172-31-xx-xxx:~$ journalctl -xeu Ignition-Gateway.service ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit Ignition-Gateway.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jan 01 12:24:47 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit Ignition-Gateway.service has entered the 'failed' state with result 'exit-code'. Jan 01 12:24:47 ip-172-31-xx-xxx systemd[1]: Failed to start Ignition-Gateway. ░░ Subject: A start job for unit Ignition-Gateway.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit Ignition-Gateway.service has finished with a failure. ░░ ░░ The job identifier is 1061 and the job result is failed. Jan 01 12:24:47 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Consumed 3.740s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit Ignition-Gateway.service completed and consumed the indicated resources. ``` ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [January 1, 2024, 1:21pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-service-failed/83652/2 "2024-01-01T13:21:27Z")
Any port under 1024 on Linux is reserved for root. Some suggestions to overcome this, in this thread: > [@Runas different user? Only get ignition working as root](https://forum.inductiveautomation.com/t/runas-different-user-only-get-ignition-working-as-root/11396): > > I have 7.8.2 install on RedHat/Oracle 7.2 with Oracle java 1.8.0\_73 I created user account and group 'ignition' and set the ignition.sh to "RUN\_AS\_USER=ignition", everything worked fine. But we won't use the default SSL port of 8043, so I used the guc command to change the SSL port (./gwcmd --sslport 443). Now ignition will NOT run at all without changing the runasuser to "root". In the log I get netstat -tulpn shows me that no, port 443 is not in use. I did come across this - [support.indu…](https://support.inductiveautomation.com/index.php?/Knowledgebase/Article/View/96/0/running-ignition-on-port-80-in-linux) ---
**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:** [January 1, 2024, 4:15pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-service-failed/83652/3 "2024-01-01T16:15:08Z")
That topic is very old. The modern approach is to include a SystemD override with `AmbientCapabilities=CAP_NET_BIND_SERVICE`. Or similar for Docker. See these topics: > [@Change the user running the Ignition Gateway service](https://forum.inductiveautomation.com/t/change-the-user-running-the-ignition-gateway-service/68564/6): > > Also, consider using a systemd override file instead of editing the main file, e.g.: systemctl edit Ignition-Gateway.service This will create an override file at /etc/systemd/system/Ignition-Gateway.service.d/override.conf that will persist through an Ignition upgrade (that may reset/revert that base configuration file). > [@Docker image now defaults to non-root user](https://forum.inductiveautomation.com/t/docker-image-now-defaults-to-non-root-user/69784): > > Greetings! I wanted to announce that the container image for the next nightly (which will eventually end up in the 8.1.26 release) contains changes to the default user/group that is used to launch Ignition. The default user is now ignition with UID/GID of 2003. You'll have to perform a migration in order to successfully transition your existing data volumes, otherwise you may encounter an error such as this one below: init | 2023/02/13 11:50:21 | Creating init.properties file init | … ---
**Author:** ![Shivam\_Mathur](https://avatars.discourse-cdn.com/v4/letter/s/f6c823/32.png) [@Shivam\_Mathur](https://forum.inductiveautomation.com/u/Shivam_Mathur)\ **Post date:** [January 2, 2024, 4:06am UTC](https://forum.inductiveautomation.com/t/ignition-gateway-service-failed/83652/4 "2024-01-02T04:06:52Z")
For now, I am just trying to run ignition as root, after I changed the `gwcmd --port 80`. In ignition.sh, I updated RUN\_AS\_USER=root, but still not able to run ignition. ```auto root@ip-172-31-xx-xxx:~# systemctl status Ignition-Gateway.service × Ignition-Gateway.service - Ignition-Gateway Loaded: loaded (/etc/systemd/system/Ignition-Gateway.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2024-01-02 04:05:43 UTC; 18s ago Process: 2136 ExecStart=/usr/local/bin/ignition/ignition.sh start sysd (code=exited, status=1/FAILURE) CPU: 89ms Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Starting Ignition-Gateway... Jan 02 04:05:43 ip-172-31-xx-xxx ignition.sh[2210]: runuser: may not be used by non-root users Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Control process exited, code=exited, status=1/FAILURE Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Failed with result 'exit-code'. Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Unit process 2211 (runuser) remains running after unit stopped. Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Failed to start Ignition-Gateway. root@ip-172-31-xx-xxx:~# journalctl -xeu Ignition-Gateway.service ░░ ░░ The job identifier is 1398. Jan 02 04:05:43 ip-172-31-xx-xxx ignition.sh[2210]: runuser: may not be used by non-root users Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Control process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit Ignition-Gateway.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Failed with result 'exit-code'. ░�� Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit Ignition-Gateway.service has entered the 'failed' state with result 'exit-code'. Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Ignition-Gateway.service: Unit process 2211 (runuser) remains running after unit stopped. Jan 02 04:05:43 ip-172-31-xx-xxx systemd[1]: Failed to start Ignition-Gateway. ░░ Subject: A start job for unit Ignition-Gateway.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit Ignition-Gateway.service has finished with a failure. ░░ ░░ The job identifier is 1398 and the job result is failed. ``` ---
**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:** [January 2, 2024, 12:53pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-service-failed/83652/5 "2024-01-02T12:53:44Z")
You cannot do it from `ignition.sh`. The user for the process must be specified in SystemD. Which is done for you if you use the installer option to set up your gateway user. You will have to do this yourself, in an override, similar to the override needed to specify ambient capabilities.