Troubleshooting

Start with these two. The first shows this computer's state, even offline. The second follows the host's log as it's written.

Host
terminal
latch status --local --pretty
latch logs -f

What an error means

You seeMeansDo
command not found: latch~/.local/bin isn't on your PATH yet.After a host install, open a new terminal. After an agent install, add it: export PATH="$HOME/.local/bin:$PATH".
not_logged_inThis computer has no login.latch login
host_offlineThat host isn't running.Run latch serve -d there.
host_unreachableCouldn't connect. Nothing was sent.Retry.
host_requiredYou have several hosts and named none.Add --host NAME.
serve_requiredThis computer's host isn't running.latch serve -d
gatekeeper_unavailableThe host couldn't judge the request, so that step didn't run. In a browser plan, earlier steps may already have acted.Read the answer's steps, then retry later only what didn't happen. If the error says the account is out of credits, add Plow credits.
gatekeeper_deniedThe gatekeeper refused.For not_covered, ask in your Plow chat, then retry. For login_site_mismatch, use the login only on its saved sites; this refusal happens before the model is asked.
exec_deniedThis host doesn't let agents run programs.Asking again won't help.
not_enabledThat connector is off on the host.On the host, run the latch plugins enable command the error gives.
outcome_unknownSent, but no answer came back.Check before you send it again.
state_formatThe state folder was made by another version of Latch.Update Latch, or run the command the error gives.

Something else

Messages or Contacts not working? Grant Full Disk Access to Plow Latch in System Settings, then restart the host.

Google not working on macOS 13 or 14? Google needs macOS 15 or later.

A connection problem? Run the command again with LATCH_TRACE=iroh=debug,latch=info set, then read trace.log in the state folder.

This page is made from its source in latch-cli. Found a mistake? Open a pull request there.