Skip to content

Tailscale Integration fails to Reconnect After Boot (sometimes) #13597

@lukepolo

Description

@lukepolo

Environmental Info:
K3s Version:

k3s version v1.34.3+k3s1 (48ffa7b)
go version go1.24.11

Node(s) CPU architecture, OS, and Version:

Linux luketestbox 5.15.0-168-generic #178-Ubuntu SMP Fri Jan 9 19:05:03 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:

3 servers, 3 agents.

Describe the bug:

after reboot sometimes tailscale will be logged out.

 tailscale status
# Health check:
#     - You are logged out.
#     - Unable to connect to the Tailscale coordination server to synchronize the state of your tailnet. Peer reachability might degrade over time.

But if you restart the k3s daemon it will reconnect

root@teestbox:/home/qadmin# systemctl restart tailscaled
root@teestbox:/home/qadmin# tailscale status
100.x.201.x   teestbox           teestbox.tailcec4f.ts.net  linux  -
100.x.161.x     dev2      tagged-devices                linux  offline, last seen 22h ago
100.x.57.x   dev 1                  tagged-devices                linux  -
100.x.118.x  dev3             tagged-devices                linux  -
100.x.150.x    dev4                macOS  offline, last seen 93d ago

Steps To Reproduce:

  • Install k3s with tailscale auth key integration.
  • Reboot any node, check if tailscale reconnected

Expected behavior:

We expect tailscale to reconnect.

Actual behavior:

Tailscale sometimes does not connect (various errors, auth key is no longer valid (which is fine because tailscale has state directory that allows connection which a restart of the service makes it connect)

Additional context / logs:

this feels like a race condition as it does not happen all the time. This could be tailsscales problem or the way i set it up.

This happens on k3s and k3s-agent nodes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done Issue

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions