Expired nodes error

[redstonekasi]

Bug description

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

Environment

• OS: Arch Linux
• Headscale version: 0.23.0-alpha2
• Tailscale version: 1.56.1

• Headscale is behind a (reverse) proxy
• Headscale runs in a container

To Reproduce

1. Setup a headscale instance using the default config, then login.
2. Log out using tailscale logout

[leroycep]

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