Troubleshoot an agent that shows offline

Check the daemon first

1. On the device, run remoteagent status.
2. If it is not running, start it: remoteagent start.
3. Confirm it stays up — a crash loop will flip it offline again.

Check the link

1. Run remoteagent login to refresh the device token.
2. Approve the device again in the console.
3. Confirm the console now shows it online.

Check the environment

$ remoteagent doctor

Network and clock

A wrong system clock breaks token checks, and a blocked egress port stops the heartbeat. remoteagent doctor flags both.

When it is the server

If every device drops at once, the console or network is the likely cause. Check the status page, then look at the daemon logs on one device.

Logs to read

$ journalctl -u remoteagent -n 50