Hello Forum,
we are using the ignition opc ua server (the loopback) and we are using it for modbus assets, and the certificate expired but connection is still working.
I want to regenerate a certificate but I want to know if this will kill our connection to the modbus assets or for the loopback server it's just internal and we will do all configuration inside ignition (because we do not have direct access to the assets!!)
I want to know how ignition uses the loopback server when using modbus!
Please Help .
Have a good day.
Thank you for your response, so I will just need to regenerate it? and I don't need to put it in another part to be trusted? it will be directly configured because it's internal to ignition right.
also I m doing the tests on our dev and I see that our modbus cannot reconnect it says reconnecting after that it disconnects, please where can I see the logs of the modbus connection. [I m seeing the logs (status -> connections -> devices) ]
Pretty sure you will. (Also, with modern Ignition, you can set a long expiration on your regenerated certificate.)
That is directly related to your problem with the OPC certificate. It could be that your devices disconnect when idle (commonly ten seconds on many devices), and they are idle because your OPC problem is preventing any subscriptions from being set up. So it mix fix itself when the OPC connection is fixed.
No, entirely within Ignition. (Sorry, I don't normally run my own Ignition instances long enough for the OPC cert to expire, and my clients have all navigated it without my help.)
thank you, I really want to know what is the flow of the certificates when using the loopback server of ignition.
basically client and server share the certificate and they check each other identity right?