I am recieving an "Invalid endpoint, check that server has security policy" error when attempting to connect to the ctrlX CORE OPC UA server via Node-RED client (node-red-contrib-opcua). I am not getting a rejected certificate in the OPC UA server either. I am able to connect to the server from UA Expert client.
Versions
- Firmware 1.20
- OPC UA Server 1.20
- Node-RED 1.20
- node-red-contrib-opcua 0.2.281 & 0.2.309 neither work
I verified the same process works with firmware 1.14, OPC UA server 1.14 and Node-RED 1.14 along with node-red-contrib-opcua 0.2.281.
Node-RED snap logs
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19:26:49.155Z :client_base_impl :531 Inner create secure channel has failed ClientTCP_transport3: socket has been disconnected by third party
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: Client connect error: The connection may have been rejected by server,
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: Err = (ClientTCP_transport3: socket has been disconnected by third party)
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19 Jul 14:26:49 - [warn] [OpcUa-Client:9670c3bad02b88ab] OpcUaClientNode: Case A: Endpoint does not contain, 1==None 2==Sign 3==Sign&Encrypt, using securityMode: [3]
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19 Jul 14:26:49 - [warn] [OpcUa-Client:9670c3bad02b88ab] OpcUaClientNode: using securityPolicy: ["http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256"]
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19 Jul 14:26:49 - [warn] [OpcUa-Client:9670c3bad02b88ab] OpcUaClientNode: Case B: UserName & password does not match to server (needed by Sign or SignAndEncrypt), check username: boschrexroth and password: boschrexroth
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19 Jul 14:26:49 - [warn] [OpcUa-Client:9670c3bad02b88ab] OpcUaClientNode: Case C: With Sign you cannot use SecurityPolicy None!!
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19 Jul 14:26:49 - [warn] [OpcUa-Client:9670c3bad02b88ab] OpcUaClientNode: Invalid endpoint parameters:
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19 Jul 14:26:49 - [error] [OpcUa-Client:9670c3bad02b88ab] Client node error on: error: ["Wrong endpoint parameters: {\"id\":\"ae2fdf6a48217315\",\"type\":\"OpcUa-Endpoint\",\"_closeCallbacks\":[],\"_inputCallback\":null,\"_inputCallbacks\":null,\"wires\":[],\"_wireCount\":0,\"credentials\":{\"user\":\"boschrexroth\",\"password\":\"boschrexroth\"},\"endpoint\":\"opc.tcp://192.168.1.100:4840\",\"securityPolicy\":\"Basic256Sha256\",\"securityMode\":\"SignAndEncrypt\",\"login\":true,\"none\":false,\"usercert\":false,\"userCertificate\":\"\",\"userPrivatekey\":\"\",\"user\":\"boschrexroth\",\"password\":\"boschrexroth\"}"]
2023-07-19T14:26:49-05:00 ctrlx-node-red.node-red[3319]: 19 Jul 14:26:49 - [error] [OpcUa-Client:9670c3bad02b88ab] Invalid endpoint
This seems to be an incompatability with the node-opcua library used in node-red-contrib-opcua and our OPC UA Server. I am not getting any logs from the OPC UA Server.
