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

headscale post-launch link 3.121.104.141:443 #377

New Issue
Closed
opened 2025-12-29 01:27:55 +01:00 by adam · 2 comments
adam commented 2025-12-29 01:27:55 +01:00
Owner
Copy Link

Originally created by @ttp2016 on GitHub (Nov 23, 2022).

Question description：
Hi, when I start my headscale, I use ss-antup| grep headscale, I found my headscale communicating with 3.121.104.141:443 in some way, Why is this happening?

tcp LISTEN 0 128 127.0.0.1:18080 0.0.0.0:* users:(("headscale",pid=2349426,fd=12))
tcp LISTEN 0 128 127.0.0.1:9090 0.0.0.0:* users:(("headscale",pid=2349426,fd=13))
tcp CLOSE-WAIT 64 0 xx.xx.xx.xx:60438 3.121.104.141:443 users:(("headscale",pid=2349426,fd=8))

Headscale Version
headscale_0.17.0-beta4_linux_amd64

Config
https://raw.githubusercontent.com/juanfont/headscale/main/config-example.yaml

Originally created by @ttp2016 on GitHub (Nov 23, 2022). Question description： Hi, when I start my headscale, I use `ss-antup| grep headscale`, I found my headscale communicating with 3.121.104.141:443 in some way, Why is this happening? tcp LISTEN 0 128 127.0.0.1:18080 0.0.0.0:* users:(("headscale",pid=2349426,fd=12)) tcp LISTEN 0 128 127.0.0.1:9090 0.0.0.0:* users:(("headscale",pid=2349426,fd=13)) tcp CLOSE-WAIT 64 0 xx.xx.xx.xx:60438 3.121.104.141:443 users:(("headscale",pid=2349426,fd=8)) Headscale Version [headscale_0.17.0-beta4_linux_amd64](https://github.com/juanfont/headscale/releases/download/v0.17.0-beta4/headscale_0.17.0-beta4_linux_amd64) Config https://raw.githubusercontent.com/juanfont/headscale/main/config-example.yaml
adam added the bug label 2025-12-29 01:27:55 +01:00
adam closed this issue 2025-12-29 01:27:55 +01:00
adam commented 2025-12-29 01:27:56 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 24, 2022):

This is what I could think of it could be:

I dont really think this is a bug, at least not with ill intentions, block it and see what breaks?

@kradalby commented on GitHub (Nov 24, 2022): This is what I could think of it could be: - TLS setup with Let's Encrypt - Fetching the DERP map: https://controlplane.tailscale.com/derpmap/default - Sending logs with logtail (if not disabled): https://github.com/juanfont/headscale/blob/main/config-example.yaml#L286-L290 - Something other DERP related I dont really think this is a bug, at least not with ill intentions, block it and see what breaks?
adam commented 2025-12-29 01:27:56 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Nov 30, 2022):

That IP address is among the ones Tailscale use for their logtail (nslookup controlplane.tailscale.com).

Disable it and try again.

@juanfont commented on GitHub (Nov 30, 2022): That IP address is among the ones Tailscale use for their logtail (`nslookup controlplane.tailscale.com`). Disable it and try again.
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#377
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?