You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had been having issues with the latest stable, so I've been running on the alpha versions. I updated from alpha4 to alpha5, and I started getting this error: cmd/headscale/cli/root.go:54 > Failed to get headscale configuration error="netip.ParsePrefix(\"\"): no '/'"
I researched on the discord, and found this was related to changes made to ACL and ipv6. So I added a subnet mask to my DNS record:
And it builds and runs, but none of the added DNS records are resolving on any of my tailscale devices.
Environment
Headscale v0.23.0-alpha5
Several, but my main testing rig was running tailscale 1.62.0
NixOS 24.05 unstable
6.1.77
[X ] Headscale is behind a (reverse) proxy, but I have not had any issues with it before upgrading to alpha5
To Reproduce
Use an existing configuration that adds extra records from alpha4 or earlier, then try the same configuration on alpha5, and the ip value will cause an error if a subnet mask is not defined.
I'm not entirely sure if it is intended behavior for DNS records to require a subnet mask now, or if it was a bug caused by the new IP validation, so I figured I would open a ticket about it.
The text was updated successfully, but these errors were encountered:
Bug description
I had been having issues with the latest stable, so I've been running on the alpha versions. I updated from alpha4 to alpha5, and I started getting this error:
cmd/headscale/cli/root.go:54 > Failed to get headscale configuration error="netip.ParsePrefix(\"\"): no '/'"
I researched on the discord, and found this was related to changes made to ACL and ipv6. So I added a subnet mask to my DNS record:
And it builds and runs, but none of the added DNS records are resolving on any of my tailscale devices.
Environment
Headscale v0.23.0-alpha5
Several, but my main testing rig was running tailscale 1.62.0
NixOS 24.05 unstable
6.1.77
[X ] Headscale is behind a (reverse) proxy, but I have not had any issues with it before upgrading to alpha5
To Reproduce
Use an existing configuration that adds extra records from alpha4 or earlier, then try the same configuration on alpha5, and the ip
value
will cause an error if a subnet mask is not defined.I'm not entirely sure if it is intended behavior for DNS records to require a subnet mask now, or if it was a bug caused by the new IP validation, so I figured I would open a ticket about it.
The text was updated successfully, but these errors were encountered: