# Ignition opcua server error **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [March 3, 2024, 6:12am UTC](https://forum.inductiveautomation.com/t/ignition-opcua-server-error/86728 "2024-03-03T06:12:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Henrol\_Jeo\_Gutierrez](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/henrol_jeo_gutierrez/32/50993_2.png) [@Henrol\_Jeo\_Gutierrez](https://forum.inductiveautomation.com/u/Henrol_Jeo_Gutierrez)\ **Post date:** [March 3, 2024, 6:12am UTC](https://forum.inductiveautomation.com/t/ignition-opcua-server-error/86728/1 "2024-03-03T06:12:30Z")
Hello community, I created a opcua client and I want to connect it to Ignition opcua server in Ignition opcua server settings: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/2/92f7656235b803733dd761b265cf7f0a4857754c.png) I also created a user under opcua-module to be use by my client. In the Ignition log, everytime I try to connect using my opcua-client, below is the error: ```auto org.eclipse.milo.opcua.stack.core.UaException: no matching endpoint found: transportProfile=TCP_UASC_UABINARY, endpointUrl=opc.tcp://Henjoe-ObX:62541/discovery, securityPolicy=Basic128Rsa15, securityMode=SignAndEncrypt at org.eclipse.milo.opcua.stack.server.transport.uasc.UascServerAsymmetricHandler.lambda$openSecureChannel$3(UascServerAsymmetricHandler.java:397) at java.base/java.util.Optional.orElseThrow(Unknown Source) at org.eclipse.milo.opcua.stack.server.transport.uasc.UascServerAsymmetricHandler.openSecureChannel(UascServerAsymmetricHandler.java:387) at org.eclipse.milo.opcua.stack.server.transport.uasc.UascServerAsymmetricHandler.lambda$sendOpenSecureChannelResponse$1(UascServerAsymmetricHandler.java:298) at org.eclipse.milo.opcua.stack.core.channel.SerializationQueue.lambda$encode$0(SerializationQueue.java:52) at org.eclipse.milo.opcua.stack.core.util.ExecutionQueue$Task.run(ExecutionQueue.java:119) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) ``` on my opcua-client configuration: > **securityMode:** `Basic128Rsa15` > **securityPolicy:** `Sign & Encrypt` > **username:** `"my username in Ignition opcua module"` > **password:** `"my password in Ignition opcua module"` > **uri:** `opc.tcp://Henjoe-ObX:62541/discovery` ✅ Note that in URI settings I also use the ` opc.tcp://localhost:62541/discovery` but it gives me the same error. ✅ Already accepted/trusted my client certificate under server security in Ignition opcua. ✅ Note that I can connect to other opcua server using this client this is the error I received from my client-opcua: ```auto 'Ignition' connect failure! Error: The connection may have been rejected by server, Err = (_socket has been disconnected by third party) ``` The error from Ignition logs it's quite obvious "no matching enpoint", but I am not quite sure how to troubleshoot it. Thanks in advance. ---
**Author:** ![Henrol\_Jeo\_Gutierrez](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/henrol_jeo_gutierrez/32/50993_2.png) [@Henrol\_Jeo\_Gutierrez](https://forum.inductiveautomation.com/u/Henrol_Jeo_Gutierrez)\ **Post date:** [March 3, 2024, 7:40am UTC](https://forum.inductiveautomation.com/t/ignition-opcua-server-error/86728/2 "2024-03-03T07:40:04Z")
I recreated the scenario of the error using the Prosys Simulation server. The error will be gone when I accept the certificate from ```auto rejected -> trusted ``` In Ignition, I already accepted the certificate but it seems like it doesn't accept it, that's why the error continues. ---
**Author:** ![Henrol\_Jeo\_Gutierrez](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/henrol_jeo_gutierrez/32/50993_2.png) [@Henrol\_Jeo\_Gutierrez](https://forum.inductiveautomation.com/u/Henrol_Jeo_Gutierrez)\ **Post date:** [March 3, 2024, 8:00am UTC](https://forum.inductiveautomation.com/t/ignition-opcua-server-error/86728/3 "2024-03-03T08:00:27Z")
The answer is here: > [@Error installing security token](https://forum.inductiveautomation.com/t/error-installing-security-token/35562/4): > > Okay, it’s what I suggested. By default Ignition’s OPC UA server only accepts secured connections at opc.tcp://10.122.220.204:62541. Unsecured discovery services can be found running at opc.tcp://10.122.220.204:62541/discovery. Some clients are defective and can’t handle this kind of setup. If that’s the case here, you change the configuration of Ignition’s server to allow None,Basic256Sha256 for its security policies (and restart) then this client will probably be able to connect. I am trying to connect to Ignition opcua server using enpoint with `/discovery` I should not put that. Lol. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [March 3, 2024, 1:09pm UTC](https://forum.inductiveautomation.com/t/ignition-opcua-server-error/86728/4 "2024-03-03T13:09:23Z")
> [@Henrol\_Jeo\_Gutierrez](#): > > I should not put that. Lol. Many clients are broken and don't understand that the endpoint URL in the endpoints returned by the GetEndpoints service might be different than the one used to call GetEndpoints. They ignore it, and instead try to subsequently open a Session against the discovery URL, instead of the session URL indicated in the EndpointDescriptions.