We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When expired nodes are processed, an error occurs. It seems the node's expiry is still properly set regardless of the error.
2024-01-03T22:55:16+01:00 INF Client requested logout node=xxx 2024-01-03T22:55:16+01:00 TRC ../hscontrol/notifier/notifier.go:79 > acquiring lock to notify type=2 2024-01-03T22:55:16+01:00 TRC ../hscontrol/notifier/notifier.go:81 > releasing lock, finished notifing type=2 2024-01-03T22:55:16+01:00 TRC ../hscontrol/notifier/notifier.go:79 > acquiring lock to notify type=2 2024-01-03T22:55:16+01:00 TRC ../hscontrol/notifier/notifier.go:81 > releasing lock, finished notifing type=2 2024-01-03T22:55:16+01:00 INF ../hscontrol/auth.go:556 > Successfully logged out node=xxx 2024-01-03T23:00:30+01:00 ERR 🤮 Cannot expire node error="invalid value, should be pointer to struct or slice" name=xxx node=xxx
tailscale logout
The text was updated successfully, but these errors were encountered:
I am also running into this bug. Same headscale and tailscale verison.
OS: NixOS 23.11
Headscale version: 0.23.0-alpha2
Tailscale version: 1.56.1
Headscale is behind a (reverse) proxy
Headscale runs in a container
Sorry, something went wrong.
fix node expire error due to type in gorm model Update
3504b54
Fixes juanfont#1674 Signed-off-by: fortitude.zhang <fortitude.zhang@gmail.com>
fix node expire error due to type in gorm model Update (#1692)
a369d57
Fixes #1674 Signed-off-by: fortitude.zhang <fortitude.zhang@gmail.com>
Successfully merging a pull request may close this issue.
Bug description
When expired nodes are processed, an error occurs. It seems the node's expiry is still properly set regardless of the error.
Environment
To Reproduce
tailscale logout
The text was updated successfully, but these errors were encountered: