I’m having difficulty getting the Designer on an AWS gateway to launch properly.
Looking at the log for the launch error I noticed the problem is what’s in screenshot below. The launcher is attempting to download Python modules via SSL on the 8043 port but the server doesn’t have an SSL certificate/domain configured yet so the connection is being refused by the gateway
Is there a way to edit the launch manifest to change that setting to false so it uses the 8088 port instead until we’re ready to enable the SSL?
1 Like
That setting is grayed out currently, so I can’t toggle it, but is showing a check in the box.
The description says It should be disabled by default though right?
It looks like SSL is enabled (possibly deliberately, via the gateway.xml file in the data/ directory) but you don’t have any actual SSL certificate, which is why the setting is greyed-out.
If you go through the SSL setup wizard (select ‘I don’t have all these items’):
And then check the ‘Advanced’ options at the bottom, you can have the system generate a ‘self-signed’ certificate. Browsers will still (justifiably) complain about it, but you should be able to remove the ‘Force Secure Redirect’ option at that point.
That said, it’s extremely unwise to disable SSL on a publicly accessible Ignition instance.
okay it looks like the gateway was just originally restored from a backup of one where SSL was properly set up and the force was enabled so that setting just carried over on us.
Thanks
