some connected nodes after headscale restart remain listed as offline, yet work

[andreiw]

• Headscale Version: v0.23.0

Let's say I restart headscale. Then do headscale nodes list. Some tailscale clients will be listed as offline, but I can still connect to them (over their tailscale/headscale IP, of course). If such a node is an exit node, because it is offline, they will not be listed in the tailscale UI as an available exit node (but if were being used as an exit node, it will continue to work).

The lastSeen value for such nodes does not update. The lastSeen value for online nodes updates, of course. If I restart tailscale on the affected node, then it is again listed as online.

Curiously enough, the behavior does not seem to be consistent with the client version. I.e. I have a host with 1.76.1 that remains listed offline and a host that remains listed online.

[routerino]

not sure that this is a hs-ui problem or headscale problem. The status relies on the online flag, and if the online flag is not set, it relies on last seen instead. This is also what juanfont said is expected behavior as lastseen is no longer reliable if online is set.

[lzz-world]

I used the command [Restart-Service Tailscale] on windows to restart the service and the service was restored