-
Notifications
You must be signed in to change notification settings - Fork 492
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
in OpenNebula 5.8.1 sunstone does not start without an IPv4 address #3282
Comments
Hello @telmich I have done some tests and for it's working if I use the IPV6 address as a host in the sunstone-server.conf, could you try this way and tell me if it works for you?
|
That is correct, 2a0a:e5c0:2:12:0:f0ff:fea9:c3fa as :host: works. However ::1, binding to IPv6 localhost does not work. If I add
So take away:
|
Hello @telmich I did more tests and it worked in these scenarios:
We will add a note in the documentation. |
Closing this. |
@al3xhh It's good to know it works, but using 0::1 or 0::0 are really counterintuitive for anyone using IPv6 and I'd also say it contradicts all IPv6 RFCs out there. |
@telmich this is a workaround for the ruby gems we use in Sunstone, it's not related directly with our code. |
Ohhh, I understand. Can you point me to that gem? I'll open a bug report there. |
@telmich I have done more tests. You can use |
@al3xhh Not sure if I understand "sunstone + apache" - is there an apache module for sunstone? We are running a couple of different ruby on rails projects that use unicorn and as far as I remember that works also with ::. |
You can run sunstone behind apache server, see this. |
Description
Previously it was possible to start sunstone without having an IPv4 address on the system.
To Reproduce
Setup a host that only has IPv4 on localhost like this:
The result is as follows:
If I add a random IPv4 address to eth0, it starts:
Expected behavior
Sunstone can be started on IPv6 only systems.
Even if IPv4 only bindings work, listening on localhost, as defined in the configuration, should work:
root@devuan:/etc/one# grep -e :host -e :port /etc/one/sunstone-server.conf
:host: 127.0.0.1
:port: 9869
Even better / really correct behaviour would be if :host can actually be "[::1]"
Details
Additional context
Progress Status
The text was updated successfully, but these errors were encountered: