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 times out #1074

New Issue
Closed
opened 2025-12-29 02:28:07 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:28:07 +01:00
Owner
Copy Link

Originally created by @Fastidious on GitHub (Jul 29, 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 have five machines connected to headscale 0.26.1. More often than not, when trying to ssh from one of my Linux machines to a macOS machine, I am getting timeouts. Using tailscale status on the Linux machine shows:

100.100.0.4     arrakis              fastidious        macOS   active; relay "mia", tx 444 rx 0

What is that relay? If all machines are connecting to my self-hosted headscale, is there a way to avoid using relays?

Expected Behavior

I would expect clients connecting to each other without using a relay.

Steps To Reproduce

I am simply trying to connect to one of the clients connected to headscale. It doesn't happen with all clients, but this specific macOS one.

Environment

- OS: Ubuntu 22.04.5 LTS
- Headscale version: 0.26.1
- Tailscale version: 1.80.3

Runtime environment

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

Debug information

arrakis_netmap.json
arrakis_status.json
arrakis_daemon-logs.log

Originally created by @Fastidious on GitHub (Jul 29, 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 have five machines connected to headscale `0.26.1`. More often than not, when trying to ssh from one of my Linux machines to a macOS machine, I am getting timeouts. Using `tailscale status` on the Linux machine shows: ``` 100.100.0.4 arrakis fastidious macOS active; relay "mia", tx 444 rx 0 ``` What is that `relay`? If all machines are connecting to my self-hosted headscale, is there a way to avoid using relays? ### Expected Behavior I would expect clients connecting to each other without using a relay. ### Steps To Reproduce I am simply trying to connect to one of the clients connected to headscale. It doesn't happen with all clients, but this specific macOS one. ### Environment ```markdown - OS: Ubuntu 22.04.5 LTS - Headscale version: 0.26.1 - Tailscale version: 1.80.3 ``` ### Runtime environment - [x] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Debug information [arrakis_netmap.json](https://github.com/user-attachments/files/21490088/arrakis_netmap.json) [arrakis_status.json](https://github.com/user-attachments/files/21490087/arrakis_status.json) [arrakis_daemon-logs.log](https://github.com/user-attachments/files/21490086/arrakis_daemon-logs.log)
adam added the bug label 2025-12-29 02:28:07 +01:00
adam closed this issue 2025-12-29 02:28:07 +01:00
adam commented 2025-12-29 02:28:08 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Jul 29, 2025):

What is that relay? If all machines are connecting to my self-hosted headscale, is there a way to avoid using relays?

Please have a look at How Tailscale works. There is also a section about relay (DERP) that is used in case no direct connection can be established.

Headscale offers a built-in DERP that can be used as relay. See the derp section in the configuration file.

By default, Tailscale's DERPs are made available to your clients to ensure connectivity. This can be disabled via the configuration as well

@nblock commented on GitHub (Jul 29, 2025): > What is that relay? If all machines are connecting to my self-hosted headscale, is there a way to avoid using relays? Please have a look at [How Tailscale works](https://tailscale.com/blog/how-tailscale-works). There is also a section about relay (DERP) that is used in case no direct connection can be established. Headscale offers a built-in DERP that can be used as relay. See the [`derp`](https://github.com/juanfont/headscale/blob/474ea236d0c6d393dbcf7baa98da240ad20c1b66/config-example.yaml#L73) section in the configuration file. By default, Tailscale's DERPs are made available to your clients to ensure connectivity. This can be disabled via the [configuration as well](https://github.com/juanfont/headscale/blob/474ea236d0c6d393dbcf7baa98da240ad20c1b66/config-example.yaml#L109)
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#1074
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?