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

[Bug] Self-built DERP server cannot obtain delay information #756

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

Originally created by @MilkTeaNo7 on GitHub (Aug 1, 2024).

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

Report:
        * UDP: true
        * IPv4: yes, 116.230.95.243:31379
        * IPv6: no, but OS has support
        * MappingVariesByDestIP: false
        * PortMapping: UPnP
        * CaptivePortal: false
        * Nearest DERP: Tokyo
        * DERP latency:
                - tok: 115.2ms (Tokyo)
				………………………………………………………………
                -  SH:         (HOME)
  1. The domain name in the derp.yaml configuration file matches the domain name in the Docker DERP Compose file.
  2. Multiple nodes have been checked and all can obtain an IPv4 address.
  3. The DERP server has opened external access permissions for ports 23479 and 3478.
  4. By using the nmap command to scan the corresponding DERP domain name at other locations, it can be confirmed that the UDP port is open.

Expected Behavior

The self-built node can return the correct latency information.

Steps To Reproduce

  1. The domain name in the derp.yaml configuration file matches the domain name in the Docker DERP Compose file.
  2. Multiple nodes have been checked and all can obtain an IPv4 address.
  3. The DERP server has opened external access permissions for ports 23479 and 3478.
  4. By using the nmap command to scan the corresponding DERP domain name at other locations, it can be confirmed that the UDP port is open.

Environment

- OS:
- Headscale version:  headscale version v0.23.0-beta1

- Tailscale version:ALL

Runtime environment

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

Anything else?

No response

Originally created by @MilkTeaNo7 on GitHub (Aug 1, 2024). ### 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 ```INI Report: * UDP: true * IPv4: yes, 116.230.95.243:31379 * IPv6: no, but OS has support * MappingVariesByDestIP: false * PortMapping: UPnP * CaptivePortal: false * Nearest DERP: Tokyo * DERP latency: - tok: 115.2ms (Tokyo) ……………………………………………………………… - SH: (HOME) ``` 1. The domain name in the `derp.yaml` configuration file matches the domain name in the Docker DERP Compose file. 2. Multiple nodes have been checked and all can obtain an IPv4 address. 3. The DERP server has opened external access permissions for ports 23479 and 3478. 4. By using the `nmap` command to scan the corresponding DERP domain name at other locations, it can be confirmed that the UDP port is open. ### Expected Behavior The self-built node can return the correct latency information. ### Steps To Reproduce 1. The domain name in the `derp.yaml` configuration file matches the domain name in the Docker DERP Compose file. 2. Multiple nodes have been checked and all can obtain an IPv4 address. 3. The DERP server has opened external access permissions for ports 23479 and 3478. 4. By using the `nmap` command to scan the corresponding DERP domain name at other locations, it can be confirmed that the UDP port is open. ### Environment ```markdown - OS: - Headscale version: headscale version v0.23.0-beta1 - Tailscale version:ALL ``` ### Runtime environment - [X] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:23:28 +01:00
adam closed this issue 2025-12-29 02:23:28 +01:00
adam commented 2025-12-29 02:23:28 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Aug 1, 2024):

Might be a duplicate of #2025

@kradalby commented on GitHub (Aug 1, 2024): Might be a duplicate of #2025
adam commented 2025-12-29 02:23:28 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Aug 2, 2024):

@MilkTeaNo7 can you check the comments from #2025?

@kradalby commented on GitHub (Aug 2, 2024): @MilkTeaNo7 can you check the comments from #2025?
adam commented 2025-12-29 02:23:29 +01:00
Author
Owner
Copy Link

@MilkTeaNo7 commented on GitHub (Aug 6, 2024):

@MilkTeaNo7 can you check the comments from #2025?

"Well, I'm not sure how he got better, maybe it was just a wrong IP address? Anyway, he's fine now, thank you."

@MilkTeaNo7 commented on GitHub (Aug 6, 2024): > @MilkTeaNo7 can you check the comments from #2025? "Well, I'm not sure how he got better, maybe it was just a wrong IP address? Anyway, he's fine now, thank you."
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#756
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?