Skip to content
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

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

Open
andreiw opened this issue Oct 28, 2024 · 1 comment

Comments

@andreiw
Copy link

andreiw commented Oct 28, 2024

  • 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
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants