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

[Bug] "Getting started" doc suggests one tailnet per user #902

New Issue
Closed
opened 2025-12-29 02:25:36 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:25:36 +01:00
Owner
Copy Link

Originally created by @samuelallan72 on GitHub (Jan 9, 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

On https://headscale.net/stable/usage/getting-started/ , under "Manage users", there is this sentence:

In headscale, a node (also known as machine or device) is always assigned to a specific user, a tailnet.

This wording suggests that a user is equivalent to a tailnet; ie. one tailnet per user. This however, is not correct for headscale.

Expected Behavior

The wording should be clear that a headscale server provides a single global tailnet, and all users are in the same tailnet.

It would also be nice to be clearer about what the concept of a user is, in the context of headscale - this has confused me a bit.

Steps To Reproduce

.

Environment

.

Runtime environment

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

Anything else?

No response

Originally created by @samuelallan72 on GitHub (Jan 9, 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 On https://headscale.net/stable/usage/getting-started/ , under "Manage users", there is this sentence: > In headscale, a node (also known as machine or device) is always assigned to a specific user, a tailnet. This wording suggests that a user is equivalent to a tailnet; ie. one tailnet per user. This however, is not correct for headscale. ### Expected Behavior The wording should be clear that a headscale server provides a single global tailnet, and all users are in the same tailnet. It would also be nice to be clearer about what the concept of a user is, in the context of headscale - this has confused me a bit. ### Steps To Reproduce . ### Environment ```markdown . ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bugdocumentation labels 2025-12-29 02:25:36 +01:00
adam closed this issue 2025-12-29 02:25:36 +01:00
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 documentation
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#902
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?