org.eclipse.milo.opcua.stack.core.UaException: no matching endpoint found: transportProfile=TCP_UASC_UABINARY, endpointUrl=opc.tcp://localhost:62541/discovery, securityPolicy=Basic256Sha256, securityMode=SignAndEncrypt
at org.eclipse.milo.opcua.stack.server.transport.uasc.UascServerAsymmetricHandler.lambda$openSecureChannel$3(UascServerAsymmetricHandler.java:407)
at java.base/java.util.Optional.orElseThrow(Unknown Source)
at org.eclipse.milo.opcua.stack.server.transport.uasc.UascServerAsymmetricHandler.openSecureChannel(UascServerAsymmetricHandler.java:397)
at org.eclipse.milo.opcua.stack.server.transport.uasc.UascServerAsymmetricHandler.lambda$sendOpenSecureChannelResponse$1(UascServerAsymmetricHandler.java:301)
at org.eclipse.milo.opcua.stack.core.channel.SerializationQueue.lambda$encode$0(SerializationQueue.java:57)
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)
I’m not sure what’s going wrong. If it’s really the exact same error message it means UaExpert is using the wrong endpoint URL, but I have the same version and it works fine.
For me, I use the /discovery URL during the custom discovery step in UaExpert, select an endpoint, then it adds the server entry into the tree on the left without the /discovery suffix, as it should, because the endpoints presented in the discovery use a different URL.
Seems to be a bug in UaExpert. I cannot get it to connect when using the advanced configuration instead of discovery either. In either variation of the endpoint URL it attempts to connect with some incorrect detail.