That’s the thing I forgot to mention. When I go into the Incoming Connections tab, I don’t see the connection request from the Backup Gateway. I’ve tried changing the Connection Policy to Unrestricted and SpecifiedList but that didn’t make any difference. I’ve included some screenshots of the settings and status. Is there any other crucial settings I might be missing?
I created the Backup Gateway VM by making a copy of the Master Gateway VM. First thing I do is changing the MAC address of the virtual network card on the Backup Gwy VM.
In the Backup Gwy VM, I then change the following:
PC Name
IP Address and make sure I can ping each other and brows each other’s gateway
Gateway name, and make sure the it’s pointing to the Master Gateway IP in the Redundancy setting
I then change the Redundancy role to Backup
I went through the same process using Ignition 7.9.10 and no issues with getting the redundancy to work.
I’ve just installed Ignition 8.0.1 and went through the same process but still no luck…
The Backup gateway is definitely trying to make connection to the Master Gateway but it’s keeps on faulting on this OutgoingConnect(): web socket connection could not be established error.
Could it be some Windows or SSL thing in the background that’s blocking the connections?
I did a fresh install of Ignition 8.0.1 for the Backup Gateway on a different VM and a new certificate with a different serial number popped in Master Gateway’s Incoming Connections tab and now the peer connection is good on both gateways. It looks like the problem was because I duplicated the Master Gateway’s VM and both VMs had the same self certificate…
Is there a way to create a new certificate on the backup? I have a similar situation, but I have two physical Linux machines that were setup with a Master ISO (not sure if that’s the correct term) and they both have the same certificate. I regenerated the opc-ua certificates, but those don’t seem to be the certificates that are being used for redundancy.