An agent is offline
Weik.io 2026.2An agent that reported before hasn't sent a status for two minutes. 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 the Home and Observability pages, then from the Health page.
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. Until it’s back, you can’t see what it runs or send it changes. Its integrations keep running for as long as the environment’s offline limit allows.
What raises it#
The agent hasn’t sent a status for two minutes. For a host that runs only a gateway, the row is about the gateway at that site instead.
When you’ve set allowed networks, the problem’s detail also shows that the agent’s address must be in those networks. If the agent last sent from an address outside those networks, the detail shows that address too.
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#
If the agent has stopped, start it. Then check that the agent’s host can reach everything it connects to:
- The two names of your Weik.io installation on port 443
- The installation’s public address
- The link’s address in the bundle’s
leaf.conf
If the agent’s bundle was replaced, install the new one with its setup.sh. The problem clears when the agent reports again.