Refreshing Ignition OPC UA Client certificate

Hi,

one of the OPC connections I have set up in my gateway went to Faulted status and from the logs I see loads of this errors starting from November 10:

INFO   | jvm 1    | 2026/11/10 10:31:38 | E [o.e.m.o.s.c.t.u.UascClientAcknowledgeHandler] [10:31:38.561]: [remote=<opc server details>:4840] Received error message: ErrorMessage{error=StatusCode{name=Bad_CertificateTimeInvalid, value=0x80140000, quality=bad}, reason=Certificate has is expired or not yet valid. NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

I then checked the certificates on the gateway and found out that the client certificate expired just 1 day before the first error, what a coincidence! So I'm guessing that's the issue.

Do you confirm this is the root cause?

I currently have other 16 active OPC connections working fine: could refreshing the Ignition OPC UA client certificate cause problems to all these other connections?

Than you

I would expect all the connections to be affected at some point, though it might depend on the server implementation.

Best would be to edit/save each (or just restart Gateway if that's an option) to force a reconnect with the new certificate. It may need to be trusted again on the servers.

So, are you saying that all connections could fail, or that nothing might happen at all? In the moment when I refresh the client certificate, I mean.

Then, sooner or later, all OPC servers might lose their connections, and someone might need to manually trust the new certificate on each server.

I've never dealt with this kind of issue before, so I'd like to understand what to expect and how to minimize the impact on the shop floor.

Thank you

What should happen is that the next time a secure channel renewed, the server realizes the certificate expired, closes the connection, and the client reconnects with the new certificate. The new certificate might not be trusted any more if you're using self-signed certs, so you would have to approve it on the server.

If you want to minimize disruption, deal with this all now by forcing the reconnects and finding out what connections won't work until you trust the certificate on the other end.

Ok, it is all clear now. Thank you for the support!