-
Notifications
You must be signed in to change notification settings - Fork 95
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
IPv4 [0.0.0.0] can't be dualstack #108
Comments
If you've changed it on your repo and works, you could submit a PR to update this repo.
I got curious though, was the wait description on boot something along "Wait for network to be configured"? I had the same problem last week, I just followed this and I didn't have to disable anything in grub. |
Yes it was, I may have a look at iptables, could be something funky there. |
While this was indeed a mistake in the help text, please read the
I did not notice the horrible implications of the proposed changes until now... 🔥 |
I did manually specify the bind to 0.0.0.0, still got the same error message until I flipped the default bool mentioned here |
Had some issues on an Ubuntu VM with Netplan and IPv6 forcing it to wait for network on boot every single time, so I disabled it in grub.
py-kms now refuses to run and spits out an error, even when I manually specify 0.0.0.0 as the IP to bind to.
I believe the issue lies in the pykms_Server.py srv_options array:
py-kms/py-kms/pykms_Server.py
Line 214 in 35fbc76
py-kms/py-kms/pykms_Server.py
Line 215 in 35fbc76
This line should be False by default (if the description is to be believed).
The text was updated successfully, but these errors were encountered: