OpenOpcUa

Michel,

Actually OpenOpcUa is constructing that URL from my hosts file. It had some 3dns.adobe.com entry which was causing the weird opc.tcp://3dns.adobe.com:16664/4CEUAServer URL. After cleaning up the hosts file, it took my laptops hostname (peter).

I tried configuring Ignition to connect to opc.tcp://peter:16664. I can't point it directly to opc.tcp://peter:16664/embedded , I can only give a hostname and a port. (I think)

I also tried to force OpenOpcUa to construct the url opc.tcp://192.168.0.101:16664/embedded using the hosts file with as first line "127.0.0.1 192.168.0.101" but I am still getting the same errors.

The Ignition client certificate is also in the CertificateStore\certs directory.

Peter,
In the OpcOpcUaCoreServer the endpoint url is build from the information available in the XML configuration file.
Let say you have :

the endpoint url will be opc.tcp://localhost:16664/4CEUAServer.
The client MUST use this EndPoint url to connect. So you just have to configure Ignition to force him to use the correct Endpoint url.

Regards
Michel

Michel,
Thank you for the clarification. I will try and force this. Ignition does have an option to override the host name:
@If specified, the host in the endpoint URL returned by the server will be ignored and the override will be used in its place.@

However, while debugging, I noticed that not all information is coming from the XML config file.
In the example you give here, the "localhost" is fetched from the hosts file from the operating system.
To block certain domain names, I had some non standard entries in there and the first one was used to construct the endpoint URL. In my case that was not localhost.

The part of the code where it gets that entry is the "getnameinfo" call in OpenOpcUaSharedLib/source/opcua_certificates.cpp, line 2882.

If I modify the hosts file, the endpoint url changes (if I remove the generated certificate).

Anyway, I will experiment some more and keep you updated.

Peter,
To clarify, let me suggest the following :
1- Configure the IP address instead of the Hostname. Both works but it will remove resolution problems
2- You have to use full Endpoint url ie:opc.tcp://192.168.0.1:16664/4CEUAServer

Remember that is project is based on sponsoring and feedback.

Regards
Michel Condemine
OpenOpcUa Project Leader
+33 (0)4 67 79 07 37

Peter,
The Ignition Moderator is right. The server is not suppose to provide a null EndPoint Description.
But the client is suppose to use the correct endpoint in its request. The Ignition client is not using the EndPoint URL of the server.
Ignition client request for opc.tcp://moefie:16664 so the answer is empty because based on your configuration the correct endpoint url is opc.tcp://moefie:16664/embedded

I hope it helps

Regards
Michel