Whenever I boot Windows for the first time, my machine can’t connect to any other Tailscale IPs. And other machines can’t connect to me. It’s as if Tailscale is down. But tailscale ping some-other-machine works correctly.
But I found a workaround: right-click on the Tailscale icon in the bottom-right taskbar, click “Disconnect”, then “Connect”. Incoming and outgoing Tailscale connections work perfectly after that.
I originally thought this was a Windows Firewall issue, but the disconnect/connect workaround confuses me. How do I continue troubleshooting? Is this a known issue? I’d like to stop using this workaround because it won’t work on unattended boots, and it’s annoying to remember after a reboot.
I’m running Tailscale 1.26.0 on Windows 10 Pro (10.0.19043 Build 19043). I also have some network adapters related to TAP, VPNs, and VirtualBox installed.
This problem doesn’t happen on another Windows 10 machine (a laptop) that I also use.
Also getting the same issue and using the same workaround, running Tailscale 1.28.0 on Windows 10 Enterprise (Build 19044.1889).
Without the workaround, neither the Tailscale IP nor the MagicDNS name works for addressing, but using tailscale ping machine-name returns a pong as intended.
Setting the Tailscale service to “Automatic (Delayed Start)”
The GUI launches on startup, but shows an error popup that the service failed
Enable “Allow service to interact with desktop” in the service
Add option to restart service after 1 minute of failure
No change (the service isn’t failing, it just couldn’t connect to the machine)
My guess is that the service starts successfully, but nonetheless fails to load Tailscale’s routes into Windows on startup; maybe it’s trying to establish the routes while the network isn’t ready yet (drivers still loading, network still connecting, etc.)?