Tailscale Stuck on "Starting..."? Here is the 503 Fix

You've got your coffee, your MacBook Pro M4 is docked, and you're ready to hit some internal Azure resources. Then you see it - that greyed-out Tailscale icon just spinning its wheels.

You try to log in again. Nothing. You try to restart the app. Still "Starting...".

If you're a dev, your next move is the terminal, where you get this:

Turns out "Starting..." is Tailscale's way of saying it can't talk to its own background service.

#The Problem

The issue usually isn't your credentials. It's a broken connection between the Tailscale GUI/CLI and the tailscaled.exe service.

Dig a bit deeper in the CLI and you'll likely see something about a missing named pipe:

The pipe between the app and the service is gone. Clicking "Login" in the UI won't fix it.

#The Solution

You have to nuke it. Kill the zombie process and clear the local state.

#1. Kill the Zombie

First, we need to make sure the background process is actually dead. Open PowerShell as Administrator and run:

#2. Clear the Local State

This is the one that usually does it. Local state files can get corrupted after a Windows Update or a hiccup in the Wintun driver. Renaming the folder forces Tailscale to start fresh.

#3. The Resurrection

Start the service again and force a re-authentication.

Your browser will open asking you to log in. Once you do, you're back up.

#Things to know

This fixes the "503 No Backend" error pretty much every time, and it also cleans up any corrupted Wintun driver state as a bonus.

The downside: Tailscale treats this as a new machine registration. You'll want to pop into your Tailscale Admin Console and remove the old dead entry to keep your device list clean.