Skip to main content

Agent offline.

  1. Open the page of the node → Agent.
  2. Check the time of the last heartbeat and the condition of the agent.
  3. Open the tab. Installation And watch the last attempt.
  4. Open Logs, select axottle-agent.service and request a fresh log.
  5. After correcting the cause, press Update in the node header.
If the agent has never connected, the Agent tab offers installation. If it has been online before, the panel shows the time of the last communication.

SSH installation fails

Open the Install tab and find the unsuccessful step. The wizard separately shows SSH connection issues, rights, installer loading, heartbeat registration and waiting.

The agent is online, but the actions are not carried out

Check the task queue and pickup time. Fresh heartbeat does not prove execution of commands. Find the suspended task, result and supported capabilities of the agent; after the update, check the new task and target version.

Installation or occupied port conflict

Read the owner of the resource in the preview. Do not delete an unknown service for the sake of restarting the wizard. For an existing Remnawave node, use the binding of an existing runtime, for a managed web route, use the supported proxy configuration.

Node degraded

  1. Open OZZZZ and the status timeline.
  2. Check out Services and Metrics.
  3. Open Journal and find the degraded event.
  4. Press Update after the cause has been eliminated.

Verification and rollback

After fixing, check the fresh heartbeat, task completion, and client path through the desired Flow. Diagnostics does not change the route. If the problem occurs after application, use the working version of Flow; for an unsuccessful update, the agent’s report and recovery mechanism.

Escalation

Attach screenshots of the Agent and Installation, the problem time window and associated tab entries Journal.