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

[Bug] Connection lost after another user/node join the tailnet #1081

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

Originally created by @Atheryl on GitHub (Aug 11, 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've moved from Tailscale due to a bug i've encountered.

Right after inviting a collaborator on my tailnet, none of us can connect the machine on the tailnet any longer (Specifically, we are using SSH Tunnel, so not SSH any longer).

The issue is fairly simple to replicate and same on both headlscale and tailscale

Expected Behavior

I would expect the tool to allow full collaboration regardless on how many users on the tailnet.

Steps To Reproduce

Fresh install of Headscale on Unbutu 24

I setup myself and a second server (Linux Ubuntu 24 as a client)

Everything works fine, both direction. I can interact with the linux via it's tailnet IP.

As soon as my colleague join the tailnet, the Ubuntu can ping both our laptops and ssh, but we can't.
Kicking him out of the tialnet and removing his machine restore the ssh.

Environment

- OS: MacOS 15.5 / Ubuntu Server 24.04
- Headscale version: 0.26.1
- Tailscale version: 1.86.4

Runtime environment

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

Debug information

Can't do on macos

Originally created by @Atheryl on GitHub (Aug 11, 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've moved from Tailscale due to a bug i've encountered. Right after inviting a collaborator on my tailnet, none of us can connect the machine on the tailnet any longer (Specifically, we are using SSH Tunnel, so not SSH any longer). The issue is fairly simple to replicate and same on both headlscale and tailscale ### Expected Behavior I would expect the tool to allow full collaboration regardless on how many users on the tailnet. ### Steps To Reproduce Fresh install of Headscale on Unbutu 24 I setup myself and a second server (Linux Ubuntu 24 as a client) Everything works fine, both direction. I can interact with the linux via it's tailnet IP. As soon as my colleague join the tailnet, the Ubuntu can ping both our laptops and ssh, but we can't. Kicking him out of the tialnet and removing his machine restore the ssh. ### Environment ```markdown - OS: MacOS 15.5 / Ubuntu Server 24.04 - Headscale version: 0.26.1 - Tailscale version: 1.86.4 ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Debug information Can't do on macos
adam added the bug label 2025-12-29 02:28:09 +01:00
adam closed this issue 2025-12-29 02:28:10 +01:00
adam commented 2025-12-29 02:28:10 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Aug 11, 2025):

As soon as my colleague join the tailnet, the Ubuntu can ping both our laptops and ssh, but we can't.
Kicking him out of the tialnet and removing his machine restore the ssh.

Please provide the exact details and debug information as described in the bug template, including:

  • headscale logs
  • client logs
  • exact commands to reproduce
  • …
@nblock commented on GitHub (Aug 11, 2025): > As soon as my colleague join the tailnet, the Ubuntu can ping both our laptops and ssh, but we can't. Kicking him out of the tialnet and removing his machine restore the ssh. Please provide the exact details and debug information as described in the bug template, including: - headscale logs - client logs - exact commands to reproduce - …
adam commented 2025-12-29 02:28:10 +01:00
Author
Owner
Copy Link

@Atheryl commented on GitHub (Aug 13, 2025):

I don't have the bandwidth for the foreseeable future, i'm sorry about that. The replication steps are fairly straightforward, hopefully someone else will be able to reproduce it. Closing for now.

@Atheryl commented on GitHub (Aug 13, 2025): I don't have the bandwidth for the foreseeable future, i'm sorry about that. The replication steps are fairly straightforward, hopefully someone else will be able to reproduce it. Closing for now.
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#1081
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?