Connecting Two Ignition Gateways via Gateway Network on the Same Machine – Certificate Issue

Hi everyone,

I’m trying to connect an Ignition Edge gateway and a Platform gateway via Gateway Network, both installed on the same machine.

Here’s my situation:

  • Platform gateway is running on port 8060
  • Edge gateway is configured to use port 8070 for Gateway Network
  • Everything seems fine in the configuration, but the connection status shows “Faulted”

The problem appears to be related to the SSL certificate: (or no)

  • The Edge gateway still shows a certificate with Common Name DESKTOP-**:8061, which seems to be from a previous port setup.
  • Even after deleting old certificates in the Platform and resetting ports in gateway.xml, the Edge doesn’t generate a new certificate with the correct port.

My question:
Is it even possible to connect two Ignition gateways via Gateway Network on the same machine?
If yes, how can I force the Edge to generate a new certificate so that the connection works correctly?

Any insights or workarounds would be appreciated!

Thanks in advance.

You can definitely connect two gateways on the same physical machine. Like you mentioned, you just have to make sure that the http, https, and gateway network ports in gateway.xml are different between the two gateways. Based on your screenshot, you are using 8.1, so my information will be based on that.

First off, make sure that the data/.uuid files are not identical on both gateways. This contents of this file is used as a global gateway network identifier, so identical files will cause all sorts of problems.

If you need to regenerate the local certificate, you would stop the gateway, delete webserver/metro-keystore , and start the gateway again. This should generate a new self-signed certificate from scratch. That being said, your issue may not be the certificate itself. You may need to accept the certificate on the other gateway’s incoming connections tab, and you may also need to approve the incoming connection. If there is any error on the gateway where the connection is configured (the outgoing connection), we can give some insight on what is going on.

2 Likes