search

mikakaraila / node-red-contrib-opcua

A Node-RED node to communicate OPC UA. Uses node-opcua library.
Other
215 stars 197 forks source link

invalid endpoint since package uppdate #220

Closed ZeRico closed 3 years ago

ZeRico commented 4 years ago

hi, everything was working fine since I decided to update to 0.2.83 to current (0.2.88) version. then no more connection possible without having a "invalid endppoint" error. so I tried to come back to 0.2.83 but no success to get a valid connection too !

my OPCUA servers (Wago Codesys PLCs) have no certificate and I connect in none/none security policy.

is there something to do after updating? thanks

ZeRico commented 4 years ago

update: I finaly tried to downgrade to 0.2.51 as suggestedd by https://github.com/mikakaraila/node-red-contrib-opcua/issues/151 and it worked !

so I came back to 0.2.84 and also worked..

strange

mikakaraila commented 4 years ago

It is actually improvement inside node-opcua that does not allow to use localhost in the endpoint. endpoint must match with the actual hostname exactly

ZeRico commented 4 years ago

I don't use any localhost, at least IP address yet preferably FQDN. nothing has been changed in the client node config

mikakaraila commented 4 years ago

Perhaps it is causing the invalid endpoint error. There has been some duplicates and re-making flow has solved this issue.

I cannot reproduce this so if you can provide more details that I could inspect then I could try to do something...

mikakaraila commented 4 years ago

New version will show more info at status, please test.

erossignon commented 4 years ago

duplicates #215

erossignon commented 4 years ago

node-opcua@2.24.1 has been released and fixes the issue.

erossignon commented 3 years ago

node-opcua@2.28.3 patch addresses a remaining issue.

mikakaraila commented 3 years ago

New version uses now node-opcua@2.28.3