tailscale: Cannot connect to coordination server warning

What is the issue?

I have noticed after updating the Tailscale client to 1.76, machines on my tailnet are showing warnings about connecting to the coordination server more frequently. On my MacOSX laptop, basically every time I change locations/connect to a different router, I get a warning in the Tailscale client about not being able to connect to the coordination server:

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

Stopping and starting the Tailscale client resolves the issue, but I would expect the client to be able to resolve this on its own without intervention. Did something change with how the Tailscale client retries connection to the coordination server?

Steps to reproduce

  • Connect to Tailscale coordination server
  • Change local internet connection

Are there any recent changes that introduced the issue?

Seems related to client update to 1.76 but unsure

OS

Linux, macOS

OS version

No response

Tailscale version

1.76.1

Other software

No response

Bug report

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 16 (1 by maintainers)

Most upvoted comments

Why did you close the issue, seems like an active bug. Is this a won’t fix situation?

My issue is resolved after doing what I posted above. If you’re still having issues, it’s unrelated to the problem I was having. Feel free to open another issue.

This seems to be impacting the Android client as well: https://www.reddit.com/r/Tailscale/comments/1gahenk/tailscale_android_out_of_sync/

I rolled back to 1.74 on my laptop (anastasia), and the issue persisted. When I’m off work, I’ll test with a few more versions.

On at least 1.74, this shows up a lot in journalctl -xeu tailscaled -f:

Dec 05 09:05:21 anastasia tailscaled[1452738]: control: lite map update error after 8.33s: Post "https://headscale.example.com/machine/map": connection attempts aborted by context: context deadline exceeded