tailscale: Windows: suddenly logged out, "tailscale is stopped", "tailscale up" and login doesn't fix it

What is the issue?

Oh no indeed. I got back from a walk, tailscale icon is missing in systray, connectivity is down.

Windows Services thinks its running.

tailscale up allows me to re-auth, but then tailscale status still just says its down.

Something bad happened. Please send help.

Steps to reproduce

No idea.

Are there any recent changes that introduced the issue?

Not on my end.

OS

Windows

OS version

Windows 11 22000.376

Tailscale version

tailscale commit: 22d9699759fa34247153a542e9c4af5696c01fdf

Bug report

BUG-bfefe0c1b08ef8f3e50c08611d06e69f106a2eacb15a58275b38151e4df9b2fd-20211215000139Z-b975da5a355b6209

Front logo Front conversations

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 17 (9 by maintainers)

Most upvoted comments

Is this a dupe of #3170 ?

Not really. That was already fixed (coming out soon), but that’s just cosmetic in this bug. It’s making your logs ugly, but it’s not the problem.

That wsl.exe error/spew is fixed in the latest builds (not yet released to the stable branch).

Oh no indeed. I got back from a walk, tailscale icon is missing in systray, connectivity is down.

Windows Services thinks its running.

When Tailscale on Windows is not running in “Run Unattended” mode, the service shuts down when the GUI disconnects.

So if your systray icon is gone, which I see it is, then the Tailscale service shuts down by design (but stays running, idle):

2021-12-14T15:58:53.582-08:00: Switching ipn state Starting -> Running (WantRunning=true, nm=true)
2021-12-14T15:58:53.583-08:00: ipnserver: conn8: ReadMsg: read tcp 127.0.0.1:41112->127.0.0.1:62516: wsarecv: An existing connection was forcibly closed by the remote host.
2021-12-14T15:58:53.583-08:00: client disconnected; stopping server
2021-12-14T15:58:53.583-08:00: LocalBackend.ResetForClientDisconnect

So the question is why the system tray GUI app shut down.