-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
fix: set default host to ::
#3348
Conversation
Pull Request Test Coverage Report for Build 6535802558
💛 - Coveralls |
just an FYI - this change broke my docker-compose environment where I have ipv6 disabled. I had to fix by setting an environment variable of HOST and setting it to the value of the container IP |
@Skullduggeryism I'm probably having similar problem to yours.
Could you please give a little bit more details was it the same as you have seen and how you fixed it. Thank you! |
Can someone of you give a try to: #3362 ? I can build a test docker container for it |
@robertsLando Sure, I can. Send me please the new container. |
I have triggered this workflow: https://github.com/zwave-js/zwave-js-ui/actions/runs/6571215103 Once it ends, you can use docker |
@robertsLando : just pulled the test tag And it works fine (after 3 min of interacting with it). Thank you! |
@bpawulski Do you have ipv6 disabled? |
@robertsLando: Yes i do |
Thanks for your report! Need to figure out if ipv6 only works too |
That is correct, I got the error "EAFNOSUPPORT: address family not supported :::8091" To fix (in docker-compose environment), you should be able to just add the following environment variable:
However, for some reason that did not work for me so I hard-coded an IP address for this container, and then made HOST that IP address. |
@Skullduggeryism try with 9.2.2 |
confirmed that I no longer need a workaround in 9.2.2. Removed hard-coded IP address and removed HOST environment variable setting and container is working as expected. |
Perfect, thanks for your feedback 🙏🏼 |
Fixes #3347