-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
[BUG] No available IPs on the server #17
Comments
okay, it looks like i got a problem. when it generates ip addresses, (IPv6 is disabled), it's trying to set ipv6_address to "-" everywhere, so it fails UNIQUE key. @RaspberryTech01 |
Interesting, how are you setting the IPv6 addresses in the config?
|
INSTANCE.IP.GLOBAL.ADDRESS.IPV6 = [ "2001:19f0:6c00:1bf2::64" ] bug reproduces when instance.ip.local.ipv6.enabled = false; |
That is correct, I never got ipv6 working in docker. Whilst its not a solution I suggest keeping it like that as it doesn't hurt. |
okay, but i suggest to set ipv6 in database field to nullable (keep unique key), and set it to null if IPv6 is disabled |
No available IPs on the server
After sending a postman request to add a key, it's returning:
Also, on my logs of docker container i can see UNIQUE constraint failed message:
My configs is:
MAX_IP: 350
ADDRESS: 10.8.0.1
SUBNET: /16
The text was updated successfully, but these errors were encountered: