tailscale / tailscale/tailscale

Running "tailscale status" leads to disconnected node

Open
#12,989 2 comments 0 reactions 1 assignee Claimed by @nickkhyl View on GitHub
bug OS-windows
Dominant language
Go
Stars
36.5k
Forks
3.2k
Avg merge
2d 3h
Merged PRs (30d)
123

Description

### What is the issue?

Tailscale nodes running in Azure Virtual Machines gets logged out when running `tailscale status`:

![image](https://github.com/user-attachments/assets/e42fb895-a4ce-45d5-8dbd-bcfb9bd5ec76)

Note that the issue does not happen to Windows Server 2022 machines running outside of Azure, e.g. in a Hyper-V virtual machine.

The issue is reproducible on newly provisioned VMs.
If not running `tailscale status` locally on the VM, the node connectivity is stable.

### Steps to reproduce

- Install Tailscale for Windows on an Azure virtual machine.
- Start Tailscale using an auth key
- `Start-Process -FilePath "C:\Program Files\Tailscale\tailscale.exe" -ArgumentList "up --unattended --hostname $tailscaleHostname --authkey $authKey" -NoNewWindow`
- Run `tailscale status`

### Are there any recent changes that introduced the issue?

No as far as I know.

### OS

Windows

### OS version

Windows Server 2022

### Tailscale version

1.70

### Other software

_No response_

### Bug report

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.