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 CLI reaching out to Github servers on every request #614

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

Originally created by @jtweaver on GitHub (Jan 20, 2024).

Bug description

On every use of the headscale command, there appears to be a call to GitHub servers (iP 140.82.113.5, for example).

If I block egress for the headscale node, headscale commands hang for 30 seconds or so. I assume it's waiting for some response from GitHub before running the command.

What is this for? Can it be turned off?

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

To Reproduce

Run a headscale command with egress disabled.

Originally created by @jtweaver on GitHub (Jan 20, 2024). <!-- Before posting a bug report, discuss the behaviour you are expecting with the Discord community to make sure that it is truly a bug. The issue tracker is not the place to ask for support or how to set up Headscale. Bug reports without the sufficient information will be closed. Headscale is a multinational community across the globe. Our language is English. All bug reports needs to be in English. --> ## Bug description <!-- A clear and concise description of what the bug is. Describe the expected bahavior and how it is currently different. If you are unsure if it is a bug, consider discussing it on our Discord server first. --> On every use of the `headscale` command, there appears to be a call to GitHub servers (iP 140.82.113.5, for example). If I block egress for the headscale node, `headscale` commands hang for 30 seconds or so. I assume it's waiting for some response from GitHub before running the command. What is this for? Can it be turned off? <!-- Please add relevant information about your system. For example: - Version of headscale used: v0.22.3 - Version of tailscale client: irrelevant - OS (e.g. Linux, Mac, Cygwin, WSL, etc.) and version: Debian 12 - Kernel version: 6.5.11-7 - The relevant config parameters you used - Log output --> <!-- We do not support running Headscale in a container nor behind a (reverse) proxy. If either of these are true for your environment, ask the community in Discord instead of filing a bug report. --> - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ## To Reproduce Run a `headscale` command with egress disabled.
adam added the bug label 2025-12-29 02:21:12 +01:00
adam closed this issue 2025-12-29 02:21:12 +01:00
adam commented 2025-12-29 02:21:13 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Jan 25, 2024):

This is likely the check to see if there is a new version available, you can turn this off:

https://github.com/juanfont/headscale/blob/main/config-example.yaml#L130

@kradalby commented on GitHub (Jan 25, 2024): This is likely the check to see if there is a new version available, you can turn this off: https://github.com/juanfont/headscale/blob/main/config-example.yaml#L130
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#614
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?