[Bug] re-assigen node to new user THEN new user can not see this node #969

Closed
opened 2025-12-29 02:26:49 +01:00 by adam · 0 comments
Owner

Originally created by @IamTaoChen on GitHub (Mar 7, 2025).

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

I used the Pre-Auth Key to register node-A to user-A. Then, I assigned Node-A to user-B. but it didn't show in tailscale status (another node of User-B)

Then I delete Node-A, and used User-B's Pre-Auth Key to login. It shown in the tailscale status but I cannot ping node-A.(It works after restart the PC)

Expected Behavior

none

Steps To Reproduce

see above

Environment

- OS: Windows
- Headscale version: 0.25.1
- Tailscale version: 1.80.2

Runtime environment

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

Anything else?

No response

Originally created by @IamTaoChen on GitHub (Mar 7, 2025). ### 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 I used the Pre-Auth Key to register node-A to user-A. Then, I assigned Node-A to user-B. but it didn't show in `tailscale status` (another node of User-B) Then I delete Node-A, and used User-B's Pre-Auth Key to login. It shown in the `tailscale status` but I cannot ping node-A.(It works after restart the PC) ### Expected Behavior none ### Steps To Reproduce see above ### Environment ```markdown - OS: Windows - Headscale version: 0.25.1 - Tailscale version: 1.80.2 ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:26:49 +01:00
adam closed this issue 2025-12-29 02:26:49 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#969