Telemetry or commands stopped
The agent uses two separate channels, and they fail independently:
- Telemetry and events go out over HTTPS.
- Commands arrive over a WebSocket the agent keeps open.
Knowing which one is broken cuts the search in half, and the symptom tells you directly.
Telemetry arrives, commands never land
Section titled “Telemetry arrives, commands never land”The classic signature: the machine is online, numbers are updating, and every command sits at Queued or Sent and never completes.
That means HTTPS works and the WebSocket does not. Two causes:
Something blocks WebSocket upgrades. Corporate proxies and some ISP middleboxes allow plain HTTPS and drop upgrade requests. Test from the machine:
curl -sS -o /dev/null -w '%{http_code}\n' https://agent.flotera.com/The agent is holding a stale address. The endpoint the agent connects to lives in a configuration snapshot taken when the machine registered. A very old agent can keep a retired address and reach it for telemetry while the command channel is refused.
Fix: update the agent from the panel. Agents older than 0.1.49 need a restart after the address moves, because they only pick up a new snapshot at startup:
sudo systemctl restart flotera-agentCommands work but data is stale
Section titled “Commands work but data is stale”Less common. Check the machine’s clock — telemetry is timestamped on the host, and a clock that is badly wrong puts readings in the wrong place on the chart.
timedatectl statusA command says Queued and stays there
Section titled “A command says Queued and stays there”Read the reason next to it; the panel always gives one:
| What it says | What is happening |
|---|---|
| server is offline — queued until it reconnects | normal. It runs when the machine returns |
| awaiting the next delivery attempt | normal, briefly |
| waiting for a guard or the previous command | something is blocking it — usually a rental |
Commands are serial per machine: the next one waits for the previous to reach a terminal state.
A command failed with an error
Section titled “A command failed with an error”The Activity tab has the machine’s own answer, which is more specific than the chip. If it says retrying will not help, it means the agent rejected the command outright rather than failing to run it — a power limit outside the card’s range, or an operation the agent lacks privilege for.
Nothing at all after an install
Section titled “Nothing at all after an install”If the machine never appeared, the install did not finish. See a machine is offline from step 3 — the cause is almost always the outbound connection.