I'm having an issue with something that just started all of a sudden, and I'm the only one of my coworkers with the issue. From searching around on the forums I do know that I am getting this error because the IP address of the backup gateway is not listed in our company's issued certificate.
It originally started as not being able to open up a new designer session which prompted me to re-add the gateway to my designer launcher. I was then asked to trust the main gateway and backup gateways' certificates by hostname with no issue. Then it asks to trust the 'third' certificate that's invalid. As originally stated, I am the only one of my coworkers having the issue connecting to this gateway, and this is the only SSL gateway that I'm having an issue with (coincidentally it's also the only one with a backup gateway).
On both the primary and backup Gateways, navigate to the Config > Web Server Settings > Public HTTP Address section.
(Web Server Settings | Ignition User Manual)
Make sure the Public Address is configured correctly for each.
Sooooo after a lot of trial error, and help from another coworker...it looks like a bug in the 1.1.44 version of the designer launcher. Downgrading mine to 1.1.38 works, and my coworker without the issue is using 1.1.37. I forgot while adding a new gateway install a few days back it asked to upgrade and I did.
I don't see how it's a bug to reject a self-admitted invalid certificate. If anything, it's a bug that the older version allows it, which we've evidently since fixed. You are only buying time by downgrading.
The bug isn't that it's trusting it. The bug was that it was asking to trust then asking to trust again via the IP address instead of the hostname. 1.1.38 didn't have trouble trusting the backup gateways certificate. The short of it is that it's probably something with the gateway being older than my designer launcher version. The gateway I couldn't get access to isn't exactly easy to take down for an upgrade.
