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] Unable to rename nodes #1125

New Issue
Closed
opened 2025-12-29 02:28:24 +01:00 by adam · 4 comments
adam commented 2025-12-29 02:28:24 +01:00
Owner
Copy Link

Originally created by @Haarolean on GitHub (Oct 28, 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

A follow-up on this one: https://github.com/juanfont/headscale/issues/2646#issuecomment-2980824031

These hostnames are still visible/available in different places:

  • logs
  • device lists:
Image

Given we still enconter them in these places, in order to understand what device that is, we have to either:

  • allow adjusting this name (maybe merge them together)
  • do not use them in logs & device lists

Expected Behavior

expected to see the human-readable names I've assigned myself

Steps To Reproduce

  1. add mobile device, which's gonna be labaled as "localhost-sth"
  2. observe it in the device list or logs

Environment

- OS: alpine
- Headscale version: 0.27.0
- Tailscale version: 1.84+

Runtime environment

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

Debug information

Originally created by @Haarolean on GitHub (Oct 28, 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 A follow-up on this one: https://github.com/juanfont/headscale/issues/2646#issuecomment-2980824031 These hostnames are still visible/available in different places: - logs - device lists: <img width="788" height="248" alt="Image" src="https://github.com/user-attachments/assets/1def91e5-30da-4a07-888f-87d0606f9eb3" /> Given we still enconter them in these places, in order to understand what device that is, we have to either: - allow adjusting this name (maybe merge them together) - do not use them in logs & device lists ### Expected Behavior expected to see the human-readable names I've assigned myself ### Steps To Reproduce 1. add mobile device, which's gonna be labaled as "localhost-sth" 2. observe it in the device list or logs ### Environment ```markdown - OS: alpine - Headscale version: 0.27.0 - Tailscale version: 1.84+ ``` ### Runtime environment - [x] Headscale is behind a (reverse) proxy - [x] Headscale runs in a container ### Debug information -
adam added the bug label 2025-12-29 02:28:24 +01:00
adam closed this issue 2025-12-29 02:28:25 +01:00
adam commented 2025-12-29 02:28:25 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Nov 2, 2025):

Which mobile app are you using? Tried to reproduce this on Android (app version 1.88.4) and the name is updated almost immediately after headscale node rename -i 4 new-name.

@nblock commented on GitHub (Nov 2, 2025): Which mobile app are you using? Tried to reproduce this on Android (app version 1.88.4) and the name is updated almost immediately after `headscale node rename -i 4 new-name`.
adam commented 2025-12-29 02:28:25 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 10, 2025):

Your example screenshot is confusing since the names are so similar, but I take it that haarlean-iphone is the name you have set, and haarlean-iphone1 is the "hostname", assigned by Headscale.

This is the expected behaviour, here from my test tailscale.com tailnet:

Image

The original name is preserved in ().

@kradalby commented on GitHub (Nov 10, 2025): Your example screenshot is confusing since the names are so similar, but I take it that `haarlean-iphone` is the name _you_ have set, and `haarlean-iphone1` is the "hostname", assigned by Headscale. This is the expected behaviour, here from my test tailscale.com tailnet: <img width="461" height="404" alt="Image" src="https://github.com/user-attachments/assets/3c88f04d-fd21-40a4-8e0a-29ed607c925b" /> The original name is preserved in `()`.
adam commented 2025-12-29 02:28:25 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 10, 2025):

As far as I can understand, you are able to rename nodes, but not past what we allow. In that case, I think this is no longer an issue and that we can close it?

@kradalby commented on GitHub (Nov 10, 2025): As far as I can understand, you are able to rename nodes, but not past what we allow. In that case, I think this is no longer an issue and that we can close it?
adam commented 2025-12-29 02:28:25 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 11, 2025):

I'm going to close this as "working as intended" as we prepare for 0.27.1

@kradalby commented on GitHub (Nov 11, 2025): I'm going to close this as "working as intended" as we prepare for 0.27.1
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#1125
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?