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

Tailscale client v1.48.x: Multiple instances of routes in headscale and --exit-node advertisement dns name not working #552

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

Originally created by @PowershellScripter on GitHub (Sep 5, 2023).

NOTE** I opened a ticket with tailscale but they are saying they may not be able to help because im using headscale even though its with their client

What is the issue?
Latest changes to tailscale client are causing double instances of the same route to show.

v1.48.x
image

v1.46.1
image

Also, tailscale client not following machine name for --exit-node=, only IP:
v1.46.1-latest

image

Steps to reproduce
Mutliple route instances:
installed v1.48.1 client and setup auth devices. verified routes are duplicating. removed device and re-added multiple times and still same result. Verified routes show multiple times in the headscale server, both windows and linux displaying same result.
verified 1.48.0 also affected.

got ahold of v1.46.1 and tested mutliple times and not able to replicate the issue on v1.46.1 compared to v1.48.x

Exit-Node machine name usage:
tailscale clients show up as advertised exit nodes and I can use --exit-node=IP, but cannot use --exit-node=name; regardless of version

Tested everything in containers and straight VMs, all issues point to the client being the offensor

OS
Linux, Windows

Tailscale version
1.46.1, 1.48.0, 1.48.1

Originally created by @PowershellScripter on GitHub (Sep 5, 2023). NOTE** I opened a ticket with tailscale but they are saying they may not be able to help because im using headscale even though its with their client What is the issue? Latest changes to tailscale client are causing double instances of the same route to show. v1.48.x ![image](https://github.com/juanfont/headscale/assets/71091773/4520737f-f9d9-4dfe-abe8-c0e0ff2973a8) v1.46.1 ![image](https://github.com/juanfont/headscale/assets/71091773/7b1b7eb2-d7e0-4825-9f81-efa11a577227) Also, tailscale client not following machine name for --exit-node=, only IP: v1.46.1-latest ![image](https://github.com/juanfont/headscale/assets/71091773/43e73e52-a021-434a-8564-b5412c6d45bb) Steps to reproduce Mutliple route instances: installed v1.48.1 client and setup auth devices. verified routes are duplicating. removed device and re-added multiple times and still same result. Verified routes show multiple times in the headscale server, both windows and linux displaying same result. verified 1.48.0 also affected. got ahold of v1.46.1 and tested mutliple times and not able to replicate the issue on v1.46.1 compared to v1.48.x Exit-Node machine name usage: tailscale clients show up as advertised exit nodes and I can use --exit-node=IP, but cannot use --exit-node=name; regardless of version Tested everything in containers and straight VMs, all issues point to the client being the offensor OS Linux, Windows Tailscale version 1.46.1, 1.48.0, 1.48.1
adam added the bug label 2025-12-29 02:19:53 +01:00
adam closed this issue 2025-12-29 02:19:53 +01:00
adam commented 2025-12-29 02:19:54 +01:00
Author
Owner
Copy Link

@winterheart commented on GitHub (Nov 20, 2023):

Got same issue, doubles routes on recent tailscale client, mine version is 1.50.1-ERR-BuildInfo

@winterheart commented on GitHub (Nov 20, 2023): Got same issue, doubles routes on recent tailscale client, mine version is 1.50.1-ERR-BuildInfo
adam commented 2025-12-29 02:19:54 +01:00
Author
Owner
Copy Link

@zc-devs commented on GitHub (Dec 3, 2023):

Got the same issue.
Tailscale Linux client v1.54.0, Headscale v0.22.3. 1.46.1 works fine.
Android client 1.55.47 works as intended.

As a workaround we can rollout version 1.46.1, approve routes and then upgrade to the latest version ('1.54.0' at time of writing).

If we add another route TS_ROUTES=10.1.0.0/16, then it duplicates again:

$ headscale routes list
ID | Machine  | Prefix      | Advertised | Enabled | Primary
30 | vm1      | 10.1.0.0/16 | true       | false   | false
31 | vm1      | 10.1.0.0/16 | true       | false   | false

As a workaround we can enable one route and delete another:

$ headscale routes enable -r 30
$ headscale routes delete -r 31

$ headscale routes list
ID | Machine  | Prefix      | Advertised | Enabled | Primary
30 | vm1      | 10.1.0.0/16 | true       | true    | true
@zc-devs commented on GitHub (Dec 3, 2023): Got the same issue. Tailscale Linux client `v1.54.0`, Headscale `v0.22.3`. `1.46.1` works fine. Android client `1.55.47` works as intended. --- As a workaround we can rollout version `1.46.1`, approve routes and then upgrade to the latest version ('1.54.0' at time of writing). --- If we add another route `TS_ROUTES=10.1.0.0/16`, then it duplicates again: ``` $ headscale routes list ID | Machine | Prefix | Advertised | Enabled | Primary 30 | vm1 | 10.1.0.0/16 | true | false | false 31 | vm1 | 10.1.0.0/16 | true | false | false ``` As a workaround we can enable one route and delete another: ``` $ headscale routes enable -r 30 $ headscale routes delete -r 31 ``` ``` $ headscale routes list ID | Machine | Prefix | Advertised | Enabled | Primary 30 | vm1 | 10.1.0.0/16 | true | true | true ```
adam commented 2025-12-29 02:19:54 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Dec 9, 2023):

Please try the code in the current main branch, there was some changes to this logic in #1564.

@kradalby commented on GitHub (Dec 9, 2023): Please try the code in the current main branch, there was some changes to this logic in #1564.
adam commented 2025-12-29 02:19:54 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Dec 10, 2023):

0.23.0-alpha2 addresses a series of issues with node synchronisation, online status and subnet routers, please test this release and report back if the issue still persist.

In addition, please verify that the issue also appears in tailscales control panel before posting issues on the client, most of the times, Headscale is the problem and we do not want to cause extra work for them unnecessarily.

@kradalby commented on GitHub (Dec 10, 2023): [0.23.0-alpha2](https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha2) addresses a series of issues with node synchronisation, online status and subnet routers, please test this release and report back if the issue still persist. In addition, please verify that the issue also appears in tailscales control panel before posting issues on the client, most of the times, Headscale is the problem and we do not want to cause extra work for them unnecessarily.
adam commented 2025-12-29 02:19:55 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Jan 4, 2024):

Does this issue happen with v0.22.3 and 1.48.1?

If it does, I will separate this from the v0.23.0 so we can address it later.

@kradalby commented on GitHub (Jan 4, 2024): Does this issue happen with v0.22.3 and 1.48.1? If it does, I will separate this from the v0.23.0 so we can address it later.
adam commented 2025-12-29 02:19:55 +01:00
Author
Owner
Copy Link

@PowershellScripter commented on GitHub (Jan 17, 2024):

Does this issue happen with v0.22.3 and 1.48.1?

If it does, I will separate this from the v0.23.0 so we can address it later.

Tried to test this but when using the alpha image, its now requiring a DERP private key?
Nothing has been changed with my headscale instance config from the old to the new, and I was not required to have a DERP private key previously. I also removed all headscale data to try a brand new instance and still same issue.

image

@PowershellScripter commented on GitHub (Jan 17, 2024): > Does this issue happen with v0.22.3 and 1.48.1? > > If it does, I will separate this from the v0.23.0 so we can address it later. Tried to test this but when using the alpha image, its now requiring a DERP private key? Nothing has been changed with my headscale instance config from the old to the new, and I was not required to have a DERP private key previously. I also removed all headscale data to try a brand new instance and still same issue. ![image](https://github.com/juanfont/headscale/assets/71091773/9903861d-b328-455b-b597-738ccfd2de3f)
adam commented 2025-12-29 02:19:55 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Jan 19, 2024):

If you have embedded DERP activated, you now need to give it a path for a private key:
https://github.com/juanfont/headscale/blob/main/CHANGELOG.md?plain=1#L32-L33

@kradalby commented on GitHub (Jan 19, 2024): If you have embedded DERP activated, you now need to give it a path for a private key: https://github.com/juanfont/headscale/blob/main/CHANGELOG.md?plain=1#L32-L33
adam commented 2025-12-29 02:19:55 +01:00
Author
Owner
Copy Link

@zc-devs commented on GitHub (Jan 26, 2024):

Hi.
I've not been using Tail/Headscale for a while. So, seems this is my last check before decommissioning.

# tailscale version
1.58.2
  tailscale commit: 6a2a8457f0d62c775bfee3e350d2b34d85eda0f5
  other commit: 8c7d4563e46a1856053912ac067fc5036c2d2b3e
  go version: go1.21.5

image: ghcr.io/juanfont/headscale:0.23.0-alpha3

# tailscale up --advertise-exit-node --login-server=https://headscale.example.com

$ headscale nodes list
ID | Hostname         | Name             | MachineKey | NodeKey | User  | IP addresses                   | Ephemeral | Last seen          
| Expiration          | Connected | Expired
15 | ts               | ts               | [/qRA5]    | [Dd3II] | infra | 100.64.0.10, fd7a:115c:a1e0::a | false     | 2024-01-26 10:58:42
| 0001-01-01 00:00:00 | online    | no

$ headscale routes list
ID | Node     | Prefix      | Advertised | Enabled | Primary
50 | ts       | 0.0.0.0/0   | true       | false   | -
51 | ts       | ::/0        | true       | false   | -

Bug with duplicated routes doesn't reproduce anymore.

Off-topic. Headscale UI's Device View doesn't work on Headscale 0.23.0-alpha3.

GET https://headscale.example.com/api/v1/machine
Status 404
@zc-devs commented on GitHub (Jan 26, 2024): Hi. I've not been using Tail/Headscale for a while. So, seems this is my last check before decommissioning. ``` # tailscale version 1.58.2 tailscale commit: 6a2a8457f0d62c775bfee3e350d2b34d85eda0f5 other commit: 8c7d4563e46a1856053912ac067fc5036c2d2b3e go version: go1.21.5 ``` ``` image: ghcr.io/juanfont/headscale:0.23.0-alpha3 ``` ``` # tailscale up --advertise-exit-node --login-server=https://headscale.example.com $ headscale nodes list ID | Hostname | Name | MachineKey | NodeKey | User | IP addresses | Ephemeral | Last seen | Expiration | Connected | Expired 15 | ts | ts | [/qRA5] | [Dd3II] | infra | 100.64.0.10, fd7a:115c:a1e0::a | false | 2024-01-26 10:58:42 | 0001-01-01 00:00:00 | online | no $ headscale routes list ID | Node | Prefix | Advertised | Enabled | Primary 50 | ts | 0.0.0.0/0 | true | false | - 51 | ts | ::/0 | true | false | - ``` Bug with duplicated routes doesn't reproduce anymore. --- Off-topic. [Headscale UI](https://github.com/gurucomputing/headscale-ui)'s Device View doesn't work on Headscale `0.23.0-alpha3`. ``` GET https://headscale.example.com/api/v1/machine Status 404 ```
adam commented 2025-12-29 02:19:55 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Feb 19, 2024):

Could you please test if this is still the case with https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha5 ?

@kradalby commented on GitHub (Feb 19, 2024): Could you please test if this is still the case with https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha5 ?
adam commented 2025-12-29 02:19:55 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Apr 17, 2024):

Could you please try the newest alpha (https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha6) and report back?

@kradalby commented on GitHub (Apr 17, 2024): Could you please try the newest alpha (https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha6) and report back?
adam commented 2025-12-29 02:19:56 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Apr 30, 2024):

Could you try the newest alpha (https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha10) and report back? If we do not hear back I will assume it has been resolved.

@kradalby commented on GitHub (Apr 30, 2024): Could you try the newest alpha (https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha10) and report back? If we do not hear back I will assume it has been resolved.
adam commented 2025-12-29 02:19:56 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (May 24, 2024):

I believe fixes in https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha12 should resolve this issue, let me now if not and we will reopen it.

@kradalby commented on GitHub (May 24, 2024): I believe fixes in https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha12 should resolve this issue, let me now if not and we will reopen it.
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#552
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?