WIN
Tailscale - Windows
Tailscale Inc.Logs
%ProgramData%\Tailscale\Logs\- Since 1.14.4per-machine
Wrong path? Add a variantTailscale
3 log locations · Windows, macOS
- Linux: managed via the systemd journal - journalctl -u tailscaled.service
Where Tailscale keeps its logs
Tailscale logs to %ProgramData%\Tailscale\Logs\ on Windows. 1 other Windows log location is recorded below, including paths for Before 1.14.4.
Tailscale logs to ~/Library/Containers/io.tailscale.ipn.macsys/Data/Library/Logs/ on macOS. These paths were verified for pkg installs - a different installer, or a portable copy, can put them somewhere else.
Paths are printed exactly as Tailscale writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.
WIN
Logs (legacy)
%LOCALAPPDATA%\Tailscale\logs\- Before 1.14.4 the service logged under the SYSTEM account's LocalAppData. Newer builds use %ProgramData%\Tailscale\Logs\, and only fall back to %LocalAppData%\Tailscale when tailscaled runs without admin rights.MAC
Tailscale - macOS
Tailscale Inc.Logs
~/Library/Containers/io.tailscale.ipn.macsys/Data/Library/Logs/- Standalone build (bundle id io.tailscale.ipn.macsys). The Mac App Store build uses bundle id io.tailscale.ipn.macos, so this folder does not apply to itpkgper-user
Wrong path? Add a variant