-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New client connection logic returns BadServiceUnsupported when the discoveryUrl and the endpointUrl are different #6051
Comments
@jpfr When I try to connect with version 1.3.4, everything is ok. But it helps me to hide a couple of lines in ua_client_connect.c. I don't know why this is done: "hello.endpointUrl = client->discoveryUrl;". I'm trying to understand... |
This change was added for GetEndpoints on servers that require the exact URL returned by the FindServers service. The behavior for reconnecting with different EndpointUrl was further improved over the last days on the 1.4 branch. Also, if possible tell us which server/SDK is used on the other end. |
@jpfr Using the latest 1.4 branch, this seems to be working. See logs below. Thank you! The OPC UA server is from https://github.com/eclipse/milo which is another open-source implementation of OPC UA. Its current target OPC UA version is 1.03. We use it mainly for testing since they keep this demo OPC UA Server running all the time.
|
We tried to connect to some OPC server (as far as I know, it is based on Java code from the official OPC Foundation repository), but still there was a connection problem in version 1.4 (branch) ((( |
Description
Background Information / Reproduction Steps
Used CMake options:
New client connection logic does not work when discoveryUrl and the endpointUrl are different.
Perhaps, this is the fix in ua_client_connect.c line #793:
Steps to reproduce:
Example client_connect is used to work @v1.3.4 for the demo OPCUA server opc.tcp:https://milo.digitalpetri.com:62541/milo
It is broken @v1.3.7
Checklist
Please provide the following information:
UA_LOGLEVEL
set as low as necessary) attachedThe text was updated successfully, but these errors were encountered: