You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After restarting the gateway, the OPC-UA Connector refuses the connection.
If I disable and enable the connector manually in the Connectors View, the connection to the OPC-UA server works.
However, I expect the gateway to attempt to re-establish the connection after a certain amount of time without me having to intervene manually.
Connector name (If bug in the some connector):
OPC-UA Connector
Error traceback (If available):
Versions (please complete the following information):
OS: Ubuntu 18.04
Thingsboard IoT Gateway version: 3.4.3.1
The text was updated successfully, but these errors were encountered:
SamuelHelbling
changed the title
[BUG] OPC-UA Connector refusing Connection after restart
[BUG] OPC-UA Connector refuses Connection after restart
Dec 18, 2023
If I physically disconnect the connection between the OPC-UA server and the gateway, the connection is refused. But after I have re-established the connection, the gateway can connect to the OPC-UA Server automatically. This is exactly the behaviour I would expect when restarting.
Hi @samy4sam, thanks for your interest in ThingsBoard IoT Gateway!
We were trying to reproduce your problem but in our case, Gateway does reconnect automatically.
Try to use the latest version from the master branch and let us know about the result.
Describe the bug
After restarting the gateway, the OPC-UA Connector refuses the connection.
If I disable and enable the connector manually in the Connectors View, the connection to the OPC-UA server works.
However, I expect the gateway to attempt to re-establish the connection after a certain amount of time without me having to intervene manually.
Connector name (If bug in the some connector):
OPC-UA Connector
Error traceback (If available):
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: