# Unable to set port 80 on Ubuntu 20.04 **URL:** \ **Category:** Ignition\ **Created:** [November 20, 2021, 5:48pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307 "2021-11-20T17:48:06Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\ **Post date:** [November 20, 2021, 5:48pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/1 "2021-11-20T17:48:06Z")
Trying to set the default port to 80 on a gateway but getting the following error message: ```auto The Entered http port 1-1023 is not allowed by the system. Please enter a different one ``` I am fairly certain its just a linux issue, but I cannot seem to find the command to fix it! I found the following command referenced, but I can’t figure out what the path to ignitions executable is, I tried `/usr/local/bin/ignition/ignition-gateway` but no luck ```auto setcap cap_net_bind_service=ep /path/to/server/executable ``` Any ideas? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 20, 2021, 6:07pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/2 "2021-11-20T18:07:55Z")
Try this instead [Change port in gateway(webserver ) port failed - #5 by pturmel](https://forum.inductiveautomation.com/t/change-port-in-gateway-webserver-port-failed/41559/5) ---
**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\ **Post date:** [November 20, 2021, 6:18pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/4 "2021-11-20T18:18:29Z")
Actually already tried that and no luck ```auto [Unit] Description=Ignition-Gateway After=syslog.target [Service] Type=forking ExecStart=/usr/local/bin/ignition/ignition.sh start sysd ExecStop=/usr/local/bin/ignition/ignition.sh stop sysd User=kgamble KillMode=process AmbientCapabilities=CAP_NET_BIND_SERVICE [Install] WantedBy=multi-user.target ``` Somehow I accidentally deleted the original response? So here is a different piece of text so that the forum will let me post it ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 20, 2021, 6:25pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/5 "2021-11-20T18:25:01Z")
Try setting the port in gateway.xml instead of the commissioning? interface? ---
**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\ **Post date:** [November 20, 2021, 6:28pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/6 "2021-11-20T18:28:27Z")
It then causes the gateway to not be able to start, my assumption is that its failing trying to bind to that port ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/8/a8f3e89a2a9840ca83356e7a08946f3437b94f96.png) If I change it back to 8088 in the .xml then it starts up perfectly fine again. I changed this in another system once by running the gateway as `root`, but I knew it was a horrible temp solution, I would prefer to not have to do the same here ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 20, 2021, 6:31pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/7 "2021-11-20T18:31:02Z")
What’s the error in the wrapper.log when it fails to start? ---
**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\ **Post date:** [November 20, 2021, 6:34pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/8 "2021-11-20T18:34:36Z")
On the bright side I was right! On the down-side, I was right and don’t know how to fix it lol 🙁 ```auto INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp: INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: Encountered an error running main: INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:80 INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.server.Server.doStart(Server.java:401) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at com.inductiveautomation.catapult.IgnitionServer.start(IgnitionServer.java:1180) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at com.inductiveautomation.ignition.gateway.web.WebResourceManagerImpl.start(WebResourceManagerImpl.java:325) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at com.inductiveautomation.ignition.gateway.IgnitionGateway.start(IgnitionGateway.java:560) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at com.inductiveautomation.ignition.gateway.IgnitionGateway.main(IgnitionGateway.java:294) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at com.inductiveautomation.catapult.Catapult.main(Catapult.java:8) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/java.lang.reflect.Method.invoke(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:349) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/java.lang.Thread.run(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: Caused by: java.net.SocketException: Permission denied INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/sun.nio.ch.Net.bind0(Native Method) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/sun.nio.ch.Net.bind(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/sun.nio.ch.Net.bind(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at java.base/sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344) INFO | jvm 1 | 2021/11/20 18:31:40 | WrapperSimpleApp Error: ... 17 more INFO | jvm 1 | 2021/11/20 18:31:40 | I [g.ModuleManager] [18:31:40]: Loading modules.... STATUS | wrapper | 2021/11/20 18:31:42 | <-- Wrapper Stopped ``` ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 20, 2021, 6:36pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/9 "2021-11-20T18:36:14Z")
Hmm. You’ve already done all the things I can think of aside from running as root… You don’t already have something running on 80 do you? Is this hardware, a VM, or Docker? ---
**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\ **Post date:** [November 20, 2021, 6:36pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/10 "2021-11-20T18:36:53Z")
Ubuntu 20.04 VM in Google Cloud with a clean install of Ignition right after creating the VM ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 20, 2021, 6:38pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/11 "2021-11-20T18:38:16Z")
I don’t know then 😕 Maybe this is a sign you should the “right thing” and run on 8088 with your security group or firewall or whatever the equivalent in Google Cloud is forwarding from 80 outside to 8088 on your instance. ---
**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\ **Post date:** [November 20, 2021, 6:41pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/12 "2021-11-20T18:41:10Z")
> [@Kevin.Herron](#): > > Maybe this is a sign you should the “right thing” and run on 8088 with your security group or firewall or whatever the equivalent in Google Cloud is forwarding from 80 outside to 8088 on your instance. Interesting, I didn't know this would be considered a better practice, I can dig into how to forward ports through the Google Cloud console. This is so much easier in docker! But for some reason, the `inductiveautomation/ignition` image would never actually start up in a container on Google Cloud. It would get stuck in "starting" forever so I had to go the manual install route. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 20, 2021, 6:43pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/13 "2021-11-20T18:43:28Z")
> [@kgamble](#): > > But for some reason, the `inductiveautomation/ignition` image would never actually start up in a container on Google Cloud. It would get stuck in “starting” forever so I had to go the manual install route. Maybe @kcollins/@kcollins has some idea? 🤷‍♂️ ---
**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\ **Post date:** [November 20, 2021, 7:42pm UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/14 "2021-11-20T19:42:42Z")
iptables in linux saved part of this, though its not what I would have preferred to do ```auto iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8088 iptables -t nat -I OUTPUT -p tcp -d 127.0.0.1 --dport 80 -j REDIRECT --to-ports 8088 ``` ---
**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\ **Post date:** [November 21, 2021, 2:57am UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/15 "2021-11-21T02:57:30Z")
I’m assuming that after making the changes to the service definition, you can `systemctl daemon-reload` to load in the changes (followed by a `systemctl restart .service`)? I’ll have a go at spinning this up to make sure it still works. With respect to Google Cloud and running as a container, can you provide more details on how you’re launching the container? I’ve not used any of the Google container services before but would be happy to give it a go to help ensure a baseline capability. Feel free to PM me with the details on that, or even start a new post and ping me or @kcollins… ---
**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\ **Post date:** [November 21, 2021, 5:29am UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/16 "2021-11-21T05:29:00Z")
EDIT: Updated on 2023-09-09, you can use the environment variables nowadays! Regarding the port 80 situation, I was able to get it going using the following sequence: 1. Assuming fresh install of Ubuntu 20.04 (I used a [Multipass](https://multipass.run) VM for this test). 2. Run the Ignition installer with defaults including starting the service. 3. Commission the gateway using the standard ports 8088/8043/8060. 4. Edit the systemd service (to add an override file to augment base service config): 5. Add the capabilities addition and drive the port configurations via env vars. 6. Ensure systemd updates are loaded 7. Restart Ignition Gateway service. At this point, you should have the gateway coming online on port 80 (if that is what you picked) even with the gateway running as a non-root user. Hope this helps... ---
**Author:** ![Hermann\_Vos](https://avatars.discourse-cdn.com/v4/letter/h/b782af/32.png) [@Hermann\_Vos](https://forum.inductiveautomation.com/u/Hermann_Vos)\ **Post date:** [September 4, 2023, 6:54am UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/17 "2023-09-04T06:54:00Z")
Good day Kevin, Please can you let me know if the method you describe here is still the correct method to allow a public facing Linux Server (Ubuntu 22.04 LTS) with Ignition 8.1.31 LTS to use port 80 and specifically port 443 to be used. I have tried this method below and does not allow the gateway to start when set to run as root, and had to reverse the change as the ignition is already in production and could not leave it offline for too long. > **[Running Ignition on port 80 in Linux](https://support.inductiveautomation.com/hc/en-us/articles/360047615371-Running-Ignition-on-port-80-in-Linux)** > > Intro > This Knowledge Base Article will walk you through the steps necessary to configure Ignition to run on port 80 on a Linux operating system.  Linux by default will not allow you to run anything... Thank you. ---
**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\ **Post date:** [September 10, 2023, 1:20am UTC](https://forum.inductiveautomation.com/t/unable-to-set-port-80-on-ubuntu-20-04/53307/18 "2023-09-10T01:20:02Z")
Yes, the above strategy should work overall (I've updated it as well, those environment variables work nowadays). I've also update the above to recommend putting the updated settings in a systemd override file instead (to stay independent of the base file which may get updated with upgrades, etc.).