Ignition OPC is installed on one server.
UaExpert is installed on other server. Both the servers are in same office.
Now when I am trying to connect Ignition from UaExpert I am getting an error message. Please find the attached image for your reference.
Please help me to resolve this problem.
When making a secure connection to Ignition’s OPC Server, standard certificate validation aspects apply. If you’re getting a hostname mismatch, it is possible that you’re trying to access the endpoint by a different DNS name than is configured in the server certificate. You can take a look here to download your Ignition OPC Server certificate for inspection or regenerate it with new IP/DNS Subject Alternative Name (SAN) entries.
You’ll want to look at the details of that cert, specifically the Subject Alternative Name (SAN) details:
openssl x509 -inform DER -in ignition-server.der -text -noout
Thank you so much for your swift response.
I have regenerated the certificate with suggested way & attached snap for your reference.
Same certificate I have installed on other server i.e. on which UaExpert is installed. Did all the required activities & still the problem is same.
Please let me know if any other checks need to be done to solve this case.
I need a help on priority. Requesting you to please help me ASAP…
I already tried to add entries in HOST file, but still there is a same error.
This forum is not support. If you have an urgent need, call support.
On recent versions of Ignition you should get prompted to explicitly add IP or DNS names to the certificate when regenerating:
Otherwise you can:
- ignore the UaExpert warning. It’s just a warning, you can connect anyway.
- connect using the IP address listed in the certificate instead.
- connect using the hostname listed in the certificate instead.
You do need to restart Ignition after regenerating certificates.