An agent is offline
Weik.io 2026.2An agent that reported before hasn't sent a status for two minutes, and its integrations keep running within the environment's offline limit. Video
Watch: Watching the whole installation, 3:10
The video watches the whole installation from Home, Observability and Health.
This part of the video couldn't be loaded.
| Kind | Severity | Who sees it |
|---|---|---|
agent- |
Error | Platform administrators |
What it means#
An agent that has reported before no longer reaches the hub, so the hub doesn’t know what the agent runs and can’t send it changes. Its integrations keep running on what they had, for as long as the environment’s offline limit allows.
What raises it#
The hub hasn’t had a status from the agent for two minutes. For a host that runs only a gateway, the row is about the gateway at that site instead. When the hub has allowed networks, the detail also says that the agent’s address must be in them, and when the address the agent last sent from is outside them, it gives that address.
What to check#
Read the agent’s last status and when it was seen:
$ weikio describe agent <agent>On the agent’s host, in its folder, check that the agent and its leaf node run:
$ docker compose ps
$ docker compose logs --tail 50 agentHow to fix it#
Start the agent when it stopped, and check that the agent’s host can reach the two names of your Weik.io installation on port 443, its public address and the link’s address in the bundle’s leaf.conf. An agent whose bundle was replaced needs the new bundle installed with its setup.sh. The problem clears when the agent reports again.