starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] expiring a node does not update the online status #751

New Issue
Closed
opened 2025-12-29 02:23:26 +01:00 by adam · 2 comments
adam commented 2025-12-29 02:23:26 +01:00
Owner
Copy Link

Originally created by @akelge on GitHub (Jul 26, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

If I expire a node, using the API, the node still appears to be online

Expected Behavior

Expiring a node should update the online status

Steps To Reproduce

  1. expire a node using headscale nodes expire -i <nodeid>
  2. check with headscale nodes list
  3. under the Expired column you will see yes, but under Connected there will be online

Environment

- OS: docker 
- Headscale version: v0.23.0-alpha12

Runtime environment

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

Anything else?

No response

Originally created by @akelge on GitHub (Jul 26, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior If I expire a node, using the API, the node still appears to be online ### Expected Behavior Expiring a node should update the online status ### Steps To Reproduce 1. expire a node using `headscale nodes expire -i <nodeid>` 2. check with `headscale nodes list` 3. under the `Expired` column you will see `yes`, but under `Connected` there will be `online` ### Environment ```markdown - OS: docker - Headscale version: v0.23.0-alpha12 ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [X] Headscale runs in a container ### Anything else? _No response_
adam added the stalebug labels 2025-12-29 02:23:26 +01:00
adam closed this issue 2025-12-29 02:23:26 +01:00
adam commented 2025-12-29 02:23:27 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 25, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Dec 25, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:23:27 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 1, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jan 1, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#751
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?