search

st-one-io / node-red-contrib-opc-da

A Node-RED node to interact with OPC-DA servers.
Apache License 2.0
11 stars 8 forks source link

"Error: Exception occured while forming Session Security Type3Response - Unknown error!" #27

Open RomanBurhenne opened 2 years ago

RomanBurhenne commented 2 years ago

Hello,

I get this Error when trying to connect to the Matrikon OPC Server: "Error: Exception occured while forming Session Security Type3Response - Unknown error!" Im running both node red and the OPC server on Win 10. I can connect with the Matrikon Client so DCOM is in Order. I use node-red 2.2.2 and npm 8.12.2 and node 18.4.0

Did anyone encounter this error?

guidfort commented 1 year ago

For this there are a workaround, see https://github.com/termux/termux-packages/issues/9266. Type3Response Error because ' let md4 = Crypto.createHash('md4');' throw exception.

narttmk commented 6 months ago

Using node 16 to resolve it

Paolo5196 commented 6 months ago

Hello!

I have the same error that is reported: Error: Exception occured while forming Session Security Type3Response - Unknown error! for my Node-red v3.1.7 and my Node.js version is v20.11.1.

I have installed all on my pc Windows and I can't fix these security. How could I resolve this connection problem?

Many thanks!! Paolo

RomanZubcov commented 5 months ago

Hello!

I have the same error that is reported: Error: Exception occured while forming Session Security Type3Response - Unknown error! for my Node-red v3.1.7 and my Node.js version is v20.11.1.

I have installed all on my pc Windows and I can't fix these security. How could I resolve this connection problem?

Many thanks!! Paolo

Have you resolved this issue?

jforge commented 5 months ago

@RomanZubcov

This happened to me on the runtime change Node-16 -> Node-18 For me, it could be resolved by adding the node runtime option --openssl-legacy-provider.

papercodeIN commented 1 week ago

@RomanZubcov

This happened to me on the runtime change Node-16 -> Node-18 For me, it could be resolved by adding the node runtime option --openssl-legacy-provider.

May I know where to add this ? I am getting same error.