-
Notifications
You must be signed in to change notification settings - Fork 663
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
Unable to start with custom url as endpoint #1098
Comments
Linux User? |
Yep, necessary context: This is in a docker container based on debain buster. Testing on the server is slightly annoying as system python is stuck at 3.6.... |
Docker containers do not support ipv6 by default. First check if you can bind to your specific address and port: Also, binding to localhost won't get you anywhere if you want to access from outside. |
My question then I guess is about the resulting endpoints, which have addresses like 172.x.x.x and a discovery url of 0.0.0.0. Would this potentially cause issues when connecting with a client? For example, we're using the National Instruments client and it seems to use the endpointURL to verify the server certificate as part of opening a session. |
The working solution is replying to the client with the address that is (or should be) included in the client's own discovery request. |
Hello,
I am trying to setup an OPC-UA server and I'm not quite clear on the behaviour of
Server.set_endpoint
. If I try to use anything other than0.0.0.0
, I get an error from asyncio that it cannot bind to the address. For example, using localhost givesAnd a similar error, with the public IPv4 addres substituted for
::1
, if using the server IP.Am I not using this correctly?
The text was updated successfully, but these errors were encountered: