12345fleet --version fleet doctor fleet list --json fleet inspect notes fleet logs notes
.fleet addresses don't resolvefleet matches the exact IP printed by fleet setup..fleet names are intentionally rejected. On Linux, Fleet leaves /etc/resolv.conf untouched and relies on Tailscale split DNS; on macOS, fleet setup --install writes /etc/resolver/fleet.~/.fleet/v2, your gateway generates a new root CA, so previously enrolled devices need the updated root certificate.fleet setup --install (on computers) or fleet phone (on iPhone) to install the matching public root.fleet gate reset. Run fleet gate on your gateway to generate a fresh 10-minute code and enter it at https://gate.fleet, or run fleet open notes on the gateway to sign in your local browser automatically.fleet logs notes — if the new edit failed to compile, Fleet keeps the last working build live so the app stays usable.fleet list --json, not a separate copy.fleet logs and fleet inspect directly on the checkout computer. See multiple computers.fleet phone won't startfleet phone on your gateway, not a secondary computer.sudo tailscale set --operator=$USER and rerun fleet phone.tailscale serve status before changing anything.fleet phone for a fresh link, or run fleet phone off to remove Fleet's temporary route manually.fleet inspect APP and fleet logs APP, and confirm the job name in fleet.json matches an exported function under jobs in server/index.ts. Remember that overdue jobs run one catch-up execution after restart, and interrupted runs retry with the same ctx.runId.1fleet uninstall
fleet nameserver in Tailscale DNS settings~/.fleet/runtime and ~/.fleet/v2 after backing up anything you want to keep