[Bug] Running Tailscale client with exit node on the same host with Headscale slows uplink for connected clients. #1108

Closed
opened 2025-12-29 02:28:19 +01:00 by adam · 2 comments
Owner

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

It seems that clients connect through DERP nodes. I tried enabling built-in DERP for Headscale, too, but it did not help much. Any way to circumvent this behaviour?

Expected Behavior

Tailscale client with exit node should co-exist on the Headscale server.

Steps To Reproduce

Used both host and Docker versions of both Tailscale and containerized Headscale.

Environment

- OS: 24.04
- Headscale version: 0.26.1
- Tailscale version: 1.88.3

Runtime environment

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

Debug information

Will leave this empty.

Originally created by @skakdollar on GitHub (Oct 13, 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 It seems that clients connect through DERP nodes. I tried enabling built-in DERP for Headscale, too, but it did not help much. Any way to circumvent this behaviour? ### Expected Behavior Tailscale client with exit node should co-exist on the Headscale server. ### Steps To Reproduce Used both host and Docker versions of both Tailscale and containerized Headscale. ### Environment ```markdown - OS: 24.04 - Headscale version: 0.26.1 - Tailscale version: 1.88.3 ``` ### Runtime environment - [x] Headscale is behind a (reverse) proxy - [x] Headscale runs in a container ### Debug information Will leave this empty.
adam added the questionbug labels 2025-12-29 02:28:19 +01:00
adam closed this issue 2025-12-29 02:28:19 +01:00
Author
Owner

@kradalby commented on GitHub (Oct 15, 2025):

Will leave this empty.

We need logs from headscale, tailscale and so on, there is not much for us to go on here other than "it work for me".

@kradalby commented on GitHub (Oct 15, 2025): > Will leave this empty. We need logs from headscale, tailscale and so on, there is not much for us to go on here other than "it work for me".
Author
Owner

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

No further details sent, closing for now.

@nblock commented on GitHub (Nov 12, 2025): No further details sent, closing for now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1108