# Certificate thumbprint does not match **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [October 29, 2018, 1:53am UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421 "2018-10-29T01:53:50Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![DavidWisely](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/davidwisely/32/10482_2.png) [@DavidWisely](https://forum.inductiveautomation.com/u/DavidWisely)\ **Post date:** [October 29, 2018, 1:53am UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/1 "2018-10-29T01:53:50Z")
I’m having trouble with the warning message shown below. It started when I change the name of the default Realtime Tag Provider. It occurs about every 20 seconds, and I’m not sure where to start. I’ve rebooted the gateway a few times with no improvements Anyone know where to start? Thanks, David ```auto TcpServerChannel 29Oct2018 12:45:41 Channel error, closing connection. Certificate thumbprint does not match com.inductiveautomation.opcua.UAException: Certificate thumbprint does not match at com.inductiveautomation.xopc.common.stack.UAChannel.processAsymmetricChunk(UAChannel.java:1149) at com.inductiveautomation.xopc.common.stack.UAChannel.processChunk(UAChannel.java:760) at com.inductiveautomation.xopc.common.stack.UAChannel.access$000(UAChannel.java:63) at com.inductiveautomation.xopc.common.stack.UAChannel$ProcessChunk.run(UAChannel.java:1570) at com.inductiveautomation.xopc.client.stack.SerialExecutionQueue$RunnableExecutor.execute(SerialExecutionQueue.java:96) at com.inductiveautomation.xopc.client.stack.SerialExecutionQueue$RunnableExecutor.execute(SerialExecutionQueue.java:93) at com.inductiveautomation.xopc.client.stack.SerialExecutionQueue$PollAndExecute.run(SerialExecutionQueue.java:71) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) ``` ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/07665c36936be9f8eefb1f40ced05dbe12cdbffb.png) ---
**Author:** ![GreggCavazos](https://avatars.discourse-cdn.com/v4/letter/g/90db22/32.png) [@GreggCavazos](https://forum.inductiveautomation.com/u/GreggCavazos)\ **Post date:** [October 29, 2018, 8:25pm UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/2 "2018-10-29T20:25:42Z")
We had a similar issue before, we solved by “Regenerating” Certificates and re-establishing the OPC Server connection. ---
**Author:** ![DavidWisely](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/davidwisely/32/10482_2.png) [@DavidWisely](https://forum.inductiveautomation.com/u/DavidWisely)\ **Post date:** [October 29, 2018, 11:35pm UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/3 "2018-10-29T23:35:58Z")
Thanks Gregg, I’ve tried regenerating the certificates. It didn’t work by itself. I’ll try recreating the OPC server connection and see how it goes. ---
**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:** [October 29, 2018, 11:36pm UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/4 "2018-10-29T23:36:48Z")
> [@DavidWisely](#): > > I'll try recreating the OPC server connection and see how it goes. If that doesn't work you probably have some other inbound OPC UA connection from either another Ignition or a 3rd party. ---
**Author:** ![GreggCavazos](https://avatars.discourse-cdn.com/v4/letter/g/90db22/32.png) [@GreggCavazos](https://forum.inductiveautomation.com/u/GreggCavazos)\ **Post date:** [October 30, 2018, 12:42am UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/5 "2018-10-30T00:42:27Z")
> I've tried regenerating the certificates. It didn't work by itself. I'll try recreating the OPC server connection and see how it goes. We had to do both steps to fix the issue, first regenerate certificates and then recreate the OPC connection. ---
**Author:** ![DavidWisely](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/davidwisely/32/10482_2.png) [@DavidWisely](https://forum.inductiveautomation.com/u/DavidWisely)\ **Post date:** [October 30, 2018, 1:07am UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/6 "2018-10-30T01:07:30Z")
Hi Kevin, Is there any way to narrow down which connection is causing the warning? I’ve tried restarting all the connections without any luck. The next step is to delete the connections and recreate them, but this is going to cause a bit of disruption. It would be good to narrow it down first. Thanks, David ---
**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:** [October 30, 2018, 1:11am UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/7 "2018-10-30T01:11:36Z")
I think the easiest / only way would be to run Wireshark on the server and watch for an incoming connection on port 4096 every ~10s. You’ll be able to see the IP address it’s coming from and hopefully that’s enough to track it down. ---
**Author:** ![DavidWisely](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/davidwisely/32/10482_2.png) [@DavidWisely](https://forum.inductiveautomation.com/u/DavidWisely)\ **Post date:** [November 12, 2018, 2:03am UTC](https://forum.inductiveautomation.com/t/certificate-thumbprint-does-not-match/20421/8 "2018-11-12T02:03:02Z")
I finally got rid of this error by restarting the remote ignition gateway.