[Feature] support tailscale wasm client #844

Closed
opened 2025-12-29 02:24:46 +01:00 by adam · 3 comments
Owner

Originally created by @Need-an-AwP on GitHub (Nov 3, 2024).

Use case

support web assembly version of tailscale client connect to headscale controller

Description

wasm tailscale client is from tailscale/tsconnect, which can run a lightweight tailscale client in front end.
ive rewrite it in https://github.com/Need-an-AwP/wasm-tailscale-react-vite, this wasm client works fine with tailscale's offical controller
and when i tried to use my headscale controller url in this wasm client, some websocket errors keep appearing
image

i have already enabled an nginx reverse proxy on this server, which also works fine(not very sure, cause the nginx configuration which can let destop client connect successfully but cannot work with wasm client at all)

my headscale version is 0.22.3 which is not the latest one, idk if this matter with this problem

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

i havent figure out how does headscale or tailscale controller communicate with wasm client (or destop client)
i dint know what cause this problem

Originally created by @Need-an-AwP on GitHub (Nov 3, 2024). ### Use case support web assembly version of tailscale client connect to headscale controller ### Description wasm tailscale client is from [tailscale/tsconnect](https://github.com/tailscale/tailscale/tree/main/cmd/tsconnect), which can run a lightweight tailscale client in front end. ive rewrite it in https://github.com/Need-an-AwP/wasm-tailscale-react-vite, this wasm client works fine with tailscale's offical controller and when i tried to use my headscale controller url in this wasm client, some websocket errors keep appearing ![image](https://github.com/user-attachments/assets/4de515ae-489a-4f32-a2a5-527b5e7f2cdf) i have already enabled an nginx reverse proxy on this server, which also works fine(not very sure, cause the nginx configuration which can let destop client connect successfully but cannot work with wasm client at all) my headscale version is 0.22.3 which is not the latest one, idk if this matter with this problem ### Contribution - [X] I can write the design doc for this feature - [X] I can contribute this feature ### How can it be implemented? i havent figure out how does headscale or tailscale controller communicate with wasm client (or destop client) i dint know what cause this problem
adam added the enhancementstale labels 2025-12-29 02:24:46 +01:00
adam closed this issue 2025-12-29 02:24:46 +01:00
Author
Owner

@kradalby commented on GitHub (Nov 13, 2024):

my headscale version is 0.22.3 which is not the latest one, idk if this matter with this problem

Likely you need the changes in https://github.com/juanfont/headscale/pull/2132, which are not released, you can try to build from main and see if that works for you.

@kradalby commented on GitHub (Nov 13, 2024): > my headscale version is 0.22.3 which is not the latest one, idk if this matter with this problem Likely you need the changes in https://github.com/juanfont/headscale/pull/2132, which are not released, you can try to build from `main` and see if that works for you.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 12, 2025):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Feb 12, 2025): This issue is stale because it has been open for 90 days with no activity.
Author
Owner

@kradalby commented on GitHub (Feb 12, 2025):

@Need-an-AwP the websocket patch should be out now, did this work for you?

@kradalby commented on GitHub (Feb 12, 2025): @Need-an-AwP the websocket patch should be out now, did this work for you?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#844