Trying to set the default port to 80 on a gateway but getting the following error message:
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
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
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.
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 name>.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 @kcollins1…
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.
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.).