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-node shows offline #579

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

Originally created by @MilkTeaNo7 on GitHub (Nov 12, 2023).

``One question
I deployed the headscale server and used the Tailscale client, and it worked fine in another environment
But in the current environment
It can connect, and the nodes can communicate with each other
But when I check with 'headscale node ls', all nodes are shown as offline.

`server_url: http://headscale.com:58344
listen_addr: 0.0.0.0:58344
metrics_listen_addr: 127.0.0.1:9090
grpc_listen_addr: 127.0.0.1:50443
grpc_allow_insecure: false
private_key_path: /var/lib/headscale/private.key
noise:
private_key_path: /var/lib/headscale/noise_private.key
ip_prefixes:

  • 100.64.0.0/10
    derp:
    server:
    enabled: false
    region_id: 999
    region_code: "headscale"
    region_name: "Headscale Embedded DERP"
    stun_listen_addr: "0.0.0.0:3478"
    urls:
    • https://controlplane.tailscale.com/derpmap/default
      paths:
      • /etc/headscale/derp.yaml
        auto_update_enabled: true
        update_frequency: 24h
        disable_check_updates: false
        ephemeral_node_inactivity_timeout: 30m
        node_update_check_interval: 10s
        db_type: sqlite3
        db_path: /var/lib/headscale/db.sqlite
        acme_url: https://acme-v02.api.letsencrypt.org/directory
        acme_email: ""
        tls_letsencrypt_hostname: ""
        tls_letsencrypt_cache_dir: /var/lib/headscale/cache
        tls_letsencrypt_challenge_type: HTTP-01
        tls_letsencrypt_listen: ":http"
        tls_cert_path: ""
        tls_key_path: ""
        log:
        format: text
        level: info
        acl_policy_path: ""
        dns_config:
        override_local_dns: false
        nameservers:
    • 119.29.29.29
      domains: []
      magic_dns: true
      base_domain: example.com
      unix_socket: /var/run/headscale/headscale.sock
      unix_socket_permission: "0770"
      logtail:
      enabled: false
      randomize_client_port: true`
Originally created by @MilkTeaNo7 on GitHub (Nov 12, 2023). ``One question I deployed the headscale server and used the Tailscale client, and it worked fine in another environment But in the current environment It can connect, and the nodes can communicate with each other But when I check with 'headscale node ls', all nodes are shown as offline. `server_url: http://headscale.com:58344 listen_addr: 0.0.0.0:58344 metrics_listen_addr: 127.0.0.1:9090 grpc_listen_addr: 127.0.0.1:50443 grpc_allow_insecure: false private_key_path: /var/lib/headscale/private.key noise: private_key_path: /var/lib/headscale/noise_private.key ip_prefixes: - 100.64.0.0/10 derp: server: enabled: false region_id: 999 region_code: "headscale" region_name: "Headscale Embedded DERP" stun_listen_addr: "0.0.0.0:3478" urls: - https://controlplane.tailscale.com/derpmap/default paths: - /etc/headscale/derp.yaml auto_update_enabled: true update_frequency: 24h disable_check_updates: false ephemeral_node_inactivity_timeout: 30m node_update_check_interval: 10s db_type: sqlite3 db_path: /var/lib/headscale/db.sqlite acme_url: https://acme-v02.api.letsencrypt.org/directory acme_email: "" tls_letsencrypt_hostname: "" tls_letsencrypt_cache_dir: /var/lib/headscale/cache tls_letsencrypt_challenge_type: HTTP-01 tls_letsencrypt_listen: ":http" tls_cert_path: "" tls_key_path: "" log: format: text level: info acl_policy_path: "" dns_config: override_local_dns: false nameservers: - 119.29.29.29 domains: [] magic_dns: true base_domain: example.com unix_socket: /var/run/headscale/headscale.sock unix_socket_permission: "0770" logtail: enabled: false randomize_client_port: true`
adam added the bug label 2025-12-29 02:20:43 +01:00
adam closed this issue 2025-12-29 02:20:43 +01:00
adam commented 2025-12-29 02:20:43 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 12, 2023):

Which version of Headscale?

@kradalby commented on GitHub (Nov 12, 2023): Which version of Headscale?
adam commented 2025-12-29 02:20:44 +01:00
Author
Owner
Copy Link

@TymanWasTaken commented on GitHub (Nov 15, 2023):

I can also reproduce on my own headscale server: the last seen date for all nodes doesn't seem to update unless I restart tailscaled to force them to re-connect to the headscale server. All connections work normally, just the last seen date and online status are bugged. The logs are also spammed with the following, so this isn't just a visual issue:

INF node offline, finding a new primary subnet node=<nodename> prefix=<subnet>
WRN no alternative primary route found node=<nodename> prefix=<subnet>

My headscale server is currently the running latest main commit, with 2 OIDC-related PRs manually merged in

@TymanWasTaken commented on GitHub (Nov 15, 2023): I can also reproduce on my own headscale server: the last seen date for all nodes doesn't seem to update unless I restart tailscaled to force them to re-connect to the headscale server. All connections work normally, just the last seen date and online status are bugged. The logs are also spammed with the following, so this isn't just a visual issue: ```log INF node offline, finding a new primary subnet node=<nodename> prefix=<subnet> WRN no alternative primary route found node=<nodename> prefix=<subnet> ``` My headscale server is currently the running latest main commit, with 2 OIDC-related PRs manually merged in
adam commented 2025-12-29 02:20:44 +01:00
Author
Owner
Copy Link

@Sh4d commented on GitHub (Nov 16, 2023):

See https://github.com/juanfont/headscale/pull/1564

@Sh4d commented on GitHub (Nov 16, 2023): See https://github.com/juanfont/headscale/pull/1564
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#579
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?