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

Expired nodes error #604

New Issue
Closed
opened 2025-12-29 02:21:07 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:21:07 +01:00
Owner
Copy Link

Originally created by @redstonekasi on GitHub (Jan 3, 2024).

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
Originally created by @redstonekasi on GitHub (Jan 3, 2024). <!-- Before posting a bug report, discuss the behaviour you are expecting with the Discord community to make sure that it is truly a bug. The issue tracker is not the place to ask for support or how to set up Headscale. Bug reports without the sufficient information will be closed. Headscale is a multinational community across the globe. Our language is English. All bug reports needs to be in English. --> ## Bug description <!-- A clear and concise description of what the bug is. Describe the expected bahavior and how it is currently different. If you are unsure if it is a bug, consider discussing it on our Discord server first. --> 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 <!-- Please add relevant information about your system. For example: - Version of headscale used - Version of tailscale client - OS (e.g. Linux, Mac, Cygwin, WSL, etc.) and version - Kernel version - The relevant config parameters you used - Log output --> - OS: Arch Linux - Headscale version: 0.23.0-alpha2 - Tailscale version: 1.56.1 <!-- We do not support running Headscale in a container nor behind a (reverse) proxy. If either of these are true for your environment, ask the community in Discord instead of filing a bug report. --> - [ ] 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` <!-- Steps to reproduce the behavior. -->
adam added the bug label 2025-12-29 02:21:07 +01:00
adam closed this issue 2025-12-29 02:21:07 +01:00
adam commented 2025-12-29 02:21:08 +01:00
Author
Owner
Copy Link

@leroycep commented on GitHub (Jan 12, 2024):

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

@leroycep commented on GitHub (Jan 12, 2024): 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 - [x] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container
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
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#604
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?