# OPC Connection Faulted for The Certificate has expired or is not yet valid

**URL:** <https://forum.inductiveautomation.com/t/opc-connection-faulted-for-the-certificate-has-expired-or-is-not-yet-valid/106901>\
**Category:** Ignition\
**Created:** [June 2, 2025, 2:43pm UTC](https://forum.inductiveautomation.com/t/opc-connection-faulted-for-the-certificate-has-expired-or-is-not-yet-valid/106901 "2025-06-02T14:43:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Speck](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@Mike\_Speck](https://forum.inductiveautomation.com/u/Mike_Speck)\
**Post date:** [June 2, 2025, 2:43pm UTC](https://forum.inductiveautomation.com/t/opc-connection-faulted-for-the-certificate-has-expired-or-is-not-yet-valid/106901/1 "2025-06-02T14:43:44Z")

</div>

Good morning all,

I walked into the office this morning with my Kepware OPC Connection Faulted for The Certificate has expired or is not yet valid. This connection had been working well for the past 6 months or so with no issues,  
After reading the post [KEPServer Certificate Expired](https://forum.inductiveautomation.com/t/kepserver-certificate-expired/74782)

I regenerated it, and now have a Fault that states, An error occurred verifying security.  
Referring to that post I'm not understanding where to trust the new cert on the Kepware "OPC UA Configuration Manager" --\> "Trusted Clients" tab.

Any help would be greatly appreciated

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [June 2, 2025, 3:12pm UTC](https://forum.inductiveautomation.com/t/opc-connection-faulted-for-the-certificate-has-expired-or-is-not-yet-valid/106901/2 "2025-06-02T15:12:47Z")

</div>

What version of Ignition are you on and which certificate(s) did you regenerate?

And if you regenerated the Ignition Client certificate, did you restart Ignition afterwards?

---

<div class="post-metadata">

**Author:** ![Mike\_Speck](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@Mike\_Speck](https://forum.inductiveautomation.com/u/Mike_Speck)\
**Post date:** [June 2, 2025, 3:16pm UTC](https://forum.inductiveautomation.com/t/opc-connection-faulted-for-the-certificate-has-expired-or-is-not-yet-valid/106901/3 "2025-06-02T15:16:15Z")

</div>

Hello Kevin,  
Running Ignition 8.1.26  
And yes I regenerated the Ignition Client Certificate but did not restart Ignition.  
I'm believe you are telling me to do so ?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [June 2, 2025, 3:17pm UTC](https://forum.inductiveautomation.com/t/opc-connection-faulted-for-the-certificate-has-expired-or-is-not-yet-valid/106901/4 "2025-06-02T15:17:19Z")

</div>

> [@Mike\_Speck](#):
>
> I'm believe you are telling me to do so ?

Yeah, I think you need to restart at least the OPC UA module, but I always recommend the full restart.

After that, you'll have to trust the new client certificate in Kepware. I think there's a hidden way to refresh that dialog if you aren't seeing the new certificate (Ctrl+R or some F-key maybe)?

---

<div class="post-metadata">

**Author:** ![Mike\_Speck](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@Mike\_Speck](https://forum.inductiveautomation.com/u/Mike_Speck)\
**Post date:** [June 2, 2025, 5:26pm UTC](https://forum.inductiveautomation.com/t/opc-connection-faulted-for-the-certificate-has-expired-or-is-not-yet-valid/106901/5 "2025-06-02T17:26:06Z")

</div>

thank you, that is fixed now and is working, i just needed to trust the client from the opc ua manager