tailscale failed to connect to local tailscaled

Not specified by the original author.

TL;DR

This error means the tailscaled daemon is stopped: the tailscale command you type is only a client, it talks to the daemon over a local socket, and every client command fails this way when the daemon is not running. On Linux, start the daemon with sudo systemctl enable --now tailscaled, then run sudo tailscale up again. It is not a network, account, or install problem; the background service is down or was never started.

failed to connect to local tailscaled; it doesn't appear to be running (sudo systemctl start tailscaled ?)

Use this when

• Any tailscale command (up, status, ping) fails with failed to connect to local tailscaled
• The message suggests starting tailscaled with systemctl and you are on Linux
• The same failure appears on macOS, Windows, or a snap install, where the daemon runs as an app, a service, or a snap instead

Not for this skill when

• tailscale status works but shows NeedsLogin. That is an expired session, not a stopped daemon; re-authenticate with tailscale up instead
• The daemon is running and active but nodes cannot reach each other. That is a connectivity or ACL problem, not this one

Steps

1. Start the daemon on Linux with systemd: sudo systemctl enable --now tailscaled. This starts it now and keeps it enabled across reboots.

Expected: no output, which means success.

2. Confirm it stayed up: systemctl is-active tailscaled.

Expected: active. Anything else means the daemon started and died; go to step 4.

3. Retry the client: sudo tailscale status, then sudo tailscale up if it asks you to log in.

Expected: your node info prints instead of the connect error, and the node comes online.

4. If the service will not stay up, read the log: journalctl -u tailscaled -n 50. The common causes are a missing /dev/net/tun device (containers and LXC guests need the TUN device passed through from the host) or another VPN holding the device.

Expected: the log names the cause instead of the generic client-side connect error.

5. On other platforms, start the equivalent service. macOS: relaunch the Tailscale app; the daemon is a system extension, so approve it under System Settings, Privacy and Security if it is blocked. Windows: start the Tailscale service in services.msc. Snap installs: sudo snap restart tailscale.

Expected: the client commands in step 3 succeed on that platform too.

Variant phrasings

tailscaled doesn't appear to be running

The same stopped-daemon failure without the systemctl hint in the text. Start the daemon for your platform (steps 1 and 5), then retry.

tailscale up failed to connect to local tailscaled

tailscale up is a client command, so it fails like all the others while the daemon is down. The fix order matters: daemon first, up second.

tailscale daemon not running ubuntu

On Ubuntu the daemon is the tailscaled systemd unit (step 1), or the tailscale snap on snap installs (step 5). Check is-active before reinstalling anything; a reinstall does not fix a service that was simply never started.

Root cause

Client/daemon split. The socket the CLI dials only exists while tailscaled runs, so a stopped daemon breaks every client command the same way, and the error text points at the daemon because that is the missing piece.

Edge cases

• On headless servers, authenticate with an auth key when you run tailscale up, since there is no browser to complete the login.
• Do not run tailscale up under a short timeout: it blocks waiting for the browser login, and a timeout kill looks like a new failure.
• In containers and LXC guests, no service restart fixes a missing TUN device; the host has to pass /dev/net/tun through.

Tool compatibility

Tailscale on Linux (systemd and snap installs), macOS (app with system extension), and Windows (Tailscale service). Applies whenever the tailscaled daemon is installed but not running.

Related skills

• duplicate node key tailscale: fix the Duplicate node key warning in the admin console: https://vectle.com/skills/skl_qmlicXbtFhGlMME7wMix7w
• tailscale up on a headless server: https://vectle.com/skills/skl_RqENuhopBsY-tKOM-lFSmQ

Provenance

Built from the Tailscale install docs: https://tailscale.com/kb/1032/install-ubuntu

Source: The tailscale command you type is only a client. It talks to the tailscaled daemon over a local socket, and every client command fails with this message when the daemon is not running. This is not a network, account, or install problem. It means the background service is down or was never started.

Verified resolution: Short answer: start the daemon. On Linux: sudo systemctl enable --now tailscaled. Then run sudo tailscale up again. `` failed to connect to local tailscaled; it doesn't appear to be running (sudo systemctl start tailscaled ?) 1. Run sudo systemctl enable --now tailscaled. This starts the daemon now and keeps it enabled across reboots. Expected: no output means success. 2. Confirm with systemctl is-active tailscaled. Expected: active. 3. Retry sudo tailscale status. Expected: your node's info, not the connect error. 4. If the service will not stay up, read journalctl -u tailscaled -n 50. Common causes: a missing /dev/net/tun device (containers and LXC guests need the TUN device passed through from the host) or another VPN holding the device. 5. Other platforms: on macOS relaunch the Tailscale app (the daemon is a system extension, approve it under System Settings, Privacy and Security if blocked). On Windows start the Tailscale service in services.msc. Snap installs: sudo snap restart tailscale. Root cause: client/daemon split. The socket the CLI dials only exists while tailscaled runs, so a stopped daemon breaks every client command the same way. When to use: this exact message on any OS. When NOT to use: if tailscale status works but shows NeedsLogin, that is an expired session, re-authenticate with tailscale up instead. Variant phrasings: "tailscaled doesn't appear to be running", "tailscale up failed to connect to local tailscaled", "tailscale daemon not running ubuntu". Edge cases: on headless servers pass an auth key (tailscale up with your auth key) since there is no browser. Do not run tailscale up` under a short timeout, it blocks waiting for the browser login and a timeout kill looks like a new failure.

Source URL: https://tailscale.com/kb/1032/install-ubuntu

Not specified by the original author.

Fix "failed to connect to local tailscaled"

TL;DR: This error means the tailscale CLI cant reach the tailscaled daemon on your machine. It is never a network problem. Start (or restart) the daemon, and if you are on WSL, start it by hand because there is no systemd to do it for you.

The error

failed to connect to local tailscaled

Often with a detail like (which appears to be running as tailscaled, pid 147358) or Got error: Get "http://local-tailscaled.sock/localapi/v0/status": EOF. Every tailscale subcommand fails the same way.

Fix it

1. Check whether the daemon is actually running

ps aux | grep -v grep | grep tailscaled

Expected: a tailscaled process line. No line means the daemon is simply not running, which is the most common cause.

2. Start the daemon

On systemd Linux:

sudo systemctl enable --now tailscaled
sudo systemctl status tailscaled

Expected: active (running) in the status output.

On macOS, open the Tailscale app once; the system extension starts the daemon. On Windows, start the Tailscale service from Services.

3. WSL: start it by hand

WSL distros often run without systemd, so the deb package install never starts the daemon (gh:tailscale/tailscale#562). Either enable systemd in /etc/wsl.conf:

[boot]
systemd=true

then restart WSL, or start the daemon manually each session:

sudo tailscaled &

Expected: tailscale status returns your machine info instead of the error.

4. Rule out a wedged daemon

If the process exists but the CLI still fails with an EOF on the socket, the daemon is wedged. Restart it:

sudo systemctl restart tailscaled

then retry the command. One reporter hit exactly this after a network change; a retry after the daemon settled worked.

Expected: the second attempt connects cleanly.

When this applies

• Any tailscale command prints "failed to connect to local tailscaled"
• Fresh install on WSL / Ubuntu where the daemon never started
• After migration or restore (Synology reporters hit this too)
• Daemon process exists but the socket read fails with EOF

When it does not apply

• tailscale up fails during login (that is an auth/control-plane problem)
• tailscale status works but peers are unreachable (network/DERP/ACL problem)
• The admin console shows a duplicate node key warning (different fix)

Tool compatibility

All Tailscale clients. The WSL variant is Linux-only; the systemd steps need Tailscale 1.x with the distro package.

Variant phrasings

"failed to connect to local tailscaled (which appears to be running as tailscaled, pid ...)"

Same error with a pid attached. The daemon process exists but is not answering the socket. Restart it (step 4).

Synology after migration: "failed to connect to local tailscaled"

The package daemon did not survive the migration. Reinstall or restart the Synology package, then tailscale up again.

Why it happens

The CLI is a thin client; all real work happens in the tailscaled daemon, reached over a local socket. Anything that stops the daemon (no init system, failed package install, a wedged process after suspend/network change) produces this exact message.

Edge cases

• Socket permission denied: if the error mentions permissions on the socket instead, your user needs access to the daemon (usually just run that one command with sudo to confirm, then fix group membership).
• It comes and goes: transient EOFs right after boot or network changes usually clear on retry once the daemon finishes starting. If it never clears, something is crashing the daemon; check journalctl -u tailscaled.
• Docker: the container needs the tailscaled socket or its own daemon with the right privileges; a bare tailscale CLI in a container without a daemon always prints this.

Thread refs gh:tailscale/tailscale#7229 and gh:tailscale/tailscale#562 (closed). In #7229 a user ran tailscale ping and got 'failed to connect to local tailscaled (which appears to be running as tailscaled, pid 147358). Got error: Get http://local-tailscaled.sock/localapi/v0/status: EOF'; the daemon was mid-state and a retry worked. In #562 (tracking bug) installing the deb packages on Ubuntu under WSL fails because WSL has no systemd running, so tailscaled never starts and every CLI call reports it cannot connect; workarounds in the thread are starting tailscaled manually or enabling systemd in WSL. The common verified pattern: this error always means the CLI cannot reach the daemon socket, so the fix is at the daemon layer (start it, fix permissions, or handle the no-systemd environment), not at the network layer. Sources: https://github.com/tailscale/tailscale/issues/7229 and https://github.com/tailscale/tailscale/issues/562

Not specified by the original author.

failed to connect to local tailscaled

TL;DR: the tailscaled daemon is not running on this machine. Start it with your init system (sudo systemctl start tailscaled on Linux), then retry the tailscale command. The CLI is a thin client that talks to the daemon over a local socket; no daemon means every command fails.

failed to connect to local tailscaled

Steps

1. Check whether the daemon is running:

systemctl status tailscaled

Expected: active (running). If it says inactive or failed, continue.

2. Start it:

sudo systemctl start tailscaled

Expected: no output, and systemctl status tailscaled now shows active.

3. Retry your command:

tailscale status

Expected: your node listed with its tailnet addresses, no socket error.

4. Make it survive reboots:

sudo systemctl enable --now tailscaled

Expected: Created symlink ... and the service stays active.

When this applies

• right after installing tailscale, before the daemon was ever enabled
• after a reboot on a box where the service was installed but never enabled
• snap installs where the service needs a nudge (see the source playbook)

When it doesnt

• tailscale up opening a browser login — that is authentication, not the daemon
• backend error: authkey ... failures — see the authkey skills
• the daemon runs but the node cannot reach the control plane — that is network, not this

Compatibility

tailscale CLI on Linux (systemd). On macOS and Windows the daemon ships inside the app itself.

Other phrasings

• can't connect to tailscaled
• tailscale: failed to connect to local tailscaled, it may not be running

Why it happens

The tailscale CLI holds no state of its own. It sends every command to tailscaled, the background daemon that owns your keys and WireGuard state, over a local socket. If the daemon never started, the socket does not exist and the CLI has nobody to talk to.

Edge cases

• On macOS and Windows there is no systemd service; if the app is not running, start the app.
• Minimal containers may lack systemd; run tailscaled directly in the background instead.
• A stale socket file after a crash can also produce this error; deleting the socket and restarting the daemon clears it.

A user setting up tailscale via snap hit failed to connect to local tailscaled on every command. The verified fix was starting and enabling the tailscaled daemon so the CLI's local socket exists. Source: https://github.com/canonical/tailscale-snap/blob/HEAD/docs/snap-actions-playbook.md (gh:canonical/tailscale-snap snap actions playbook).