# OPCUA Client node always on statuts "Connecting"
**URL:** https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158
**Category:** Industrial
**Created:** [1 February 2021 10:27 UTC](https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158 "2021-02-01T10:27:51Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@jlb](https://discourse.nodered.org/u/jlb)
#### Post date: [1 February 2021 10:27 UTC](https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158/1 "2021-02-01T10:27:52Z")
I have a simple flow in order to read values on a OPCUA serveur on a PLC:
I first test the OPCUA value with UAExpert and it works well:
it works with no security&certificate and anonymous.
Then i try to test it in node-red with the same configuration values:
But when i inject i have nothing in return, no error messages, just the status of OPCUA client in "Connecting"... I try with other values, that's the same. I access well the PLC because i tested it with a classic S7 node.
Some ideas ? Thanks in advance !
---
### Author:  [@statsmi](https://discourse.nodered.org/u/statsmi)
#### Post date: [10 February 2021 21:02 UTC](https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158/2 "2021-02-10T21:02:46Z")
I have the same issue. I am able to see that endpoint with the same settings in a test client but my UAClient node remains in connecting like yours. Did you happen to find a solution?
---
### Author:  [@jlb](https://discourse.nodered.org/u/jlb)
#### Post date: [11 February 2021 07:21 UTC](https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158/3 "2021-02-11T07:21:20Z")
No solution found yet 😕but with the same flow on another PC (the other is on a server) it works so it means that's a network filter or access issue. (but i can ping the IP en both cases...)
---
### Author:  [@statsmi](https://discourse.nodered.org/u/statsmi)
#### Post date: [11 February 2021 08:34 UTC](https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158/4 "2021-02-11T08:34:37Z")
I also tried the same using a different PC as well as a different PLC and still have the problem.
Same issue, I can see the tags with a free OPC client using "none/none" for security policy but my OPC node remains in connecting state. If you see the debug node there is an error, I will post mine later today.
I have been trying with a Beckhoff Twincat3 OPC Server and also a Siemens S7-1500 OPC server. No luck.
---
### Author:  [@rromele](https://discourse.nodered.org/u/rromele)
#### Post date: [12 February 2021 23:58 UTC](https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158/5 "2021-02-12T23:58:39Z")
I have the impression that it is a widespread problem with the OPC\_UA node, I also tried installing certificates on the server, setting security policies with user and password, without obtaining positive results.
I would investigate the "local own certificate is not used" system message.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [13 April 2021 23:58 UTC](https://discourse.nodered.org/t/opcua-client-node-always-on-statuts-connecting/40158/6 "2021-04-13T23:58:56Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.