When connecting OPC-UA for Pactware with UaExpert, an error message 'URL not found' is displayed.

[ys_az]

Dear Support Team,

"When connecting OPC-UA for Pactware provided by Wetcon with UaExpert, an error message 'URL not found' is displayed, and the connection is not successful. We have confirmed that the certificate locations are correct, they trust each other, and the endpoints are correct. We have also checked the firewall port access. What steps should we take to resolve this issue?

Message content: There was no exact match for the specified URL in the server's endpoints, using the first server certificate found for connecting.

The following are all the verified settings:

Pactware's OPC-UA server endpoint:
opc.tcp://localhost:48032/
opc.tcp://localhost:48032
opc.tcp://localhost:<PC name>/
opc.tcp://localhost:<PC name>

UaExpert endpoint setting:
opc.tcp://localhost:48032/
opc.tcp://localhost:48032
opc.tcp://localhost:<PC name>/
opc.tcp://localhost:<PC name>

Sincerely,

[ys_az]

I made a mistake in the notation.

"Incorrect:
opc.tcp://localhost:<PC name>
opc.tcp://localhost:<PC name>/

"Correct:
opc.tcp://<PC name>:48032
opc.tcp://<PC name>:48032/

[Support Team]

Hi,

the UaExpert "reads" the EndpointDescription from the Server. This is part of the discovery process - FindServer() and GetEndpoints() - You must make sure that the server provides correct information (server configuration) in it's Endpoint descriptions. The client UaExpert takes whatever is returned by the server!

An endpoint can NOT have both "localhost" AND "hostname", you must decide for either "localhost" OR for the "hostname". But your server may have mutliple endpoints. The <bind address> is the address where the server is "listening" and can be hostname, loopback, ip4 or ip6 (but not all at once).

The syntax is:
<ua protocol identifiyer>://<bind address>:<port>/<more information, but irrelevant for connect>

Example for server-side endpoint configuration:
opc.tcp://mycomputer:48123 --> which allows to connect via ALL IP addresses to the server (is listening on Any-IP)
opc.tcp://192.148.0.123:48123 --> which allows to connct via this ONE IP address only, in case the server has multiple NICs and IPs
opc.tcp://localhost:48123 --> which is same than opc.tcp://127.0.0.1:48123 and allows LOCAL connection only

Example for client-side:
--> select one of the endpoints as returned in GetEndpoints()-Response, and select some suitable SecurityPolicy, as also given in the EndpointDescription. The client may check if the endpointURI used to connect matches the one given in the x509 certificate (in order to detect if connecting to the correct server).

[ys_az]

Thank you for your reply.

I apologize for the poor explanation.
Basically, I am using it only on localhost.
I listed the four endpoints to indicate that I set and checked each one, and they all resulted in errors.
As you mentioned, I am not using localhost and hostname together.

[Support Team]

Hi,

if you can not connect with the Pactware UA Server provided by Wetcon with latest UaExpert, and you have checked the correct endpoint configuration, you must contact the Wetcon/Pactware support. There must be a configuration error in the Pactware UA Server.

The UaExpert is doing a two fold connect approach, 1) calling GetEndpoints, display the list of endpoints as presented by the server; and 2) calling OpenSecureChannel/CreateSession, on the selected Endpoint as given by the server.

The endpoint descriptions as retured by the server must be consistent and correct, the information presented in the endpoint description (especially the "EndpointURI") must be correct including resolveable hostname/IP, because the UA client will directly use whatever is presented.