-
Notifications
You must be signed in to change notification settings - Fork 662
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
Force change FindServers call reply #824
Comments
This is a docker issue/question. I have no idea |
It's not a docker issue, but conflict between endpoints system and NAT translation. |
Can you make PR. So we can look at it? |
I thought we were dumbly returning the same string but maybe someone changed that. There is also a open PR to make that stuff really complicated but I never dared committing it |
If you mean this one: #687 @PGajewski You can test if it solves your problem using this branch. If I remember correctly, in my case a VPN caused freeopcua to announce an unreachable listening address. However, as the client (I don't know if this is always the case) includes the server address during discovery request, I've modified the server code so that this address is also included in the response. |
Hi,
I'm running OPC-UA server on Docker container and I want use client from external device (PLC). This device knows only the docker host IP address.
It is possible to set DiscoveryURL and EndpointURL with docker host IP? I've try set different hostname for BinaryServer(0.0.0.0) nad InternalServer(docker host IP), but still FindServers call return endpoint with docker container IP, co my client on another machine cannot establish the new session (DiscoveryURL is set properly).
The text was updated successfully, but these errors were encountered: