> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Node control panel

> Detailed analysis of the node page: statuses, metrics, services, logs, signals, security, domains, agent and settings.

A node control panel is a server-specific page that combines surveillance, diagnostics, and node actions, from viewing a CPU boot to issuing a TLS certificate or restarting a service.

You can open it from the **Node** section by clicking on the desired line.

> [!NOTE]
>
> For whom: Panel Administrator, SRE. Part of the action requires an online agent and appropriate capability.

![Map of the control panel](https://mintcdn.com/axottle/sCAOZ_zMCLaFN-kS/images/nodes/control-panel-map.svg?fit=max\&auto=format\&n=sCAOZ_zMCLaFN-kS\&q=85\&s=29f18f5761a7d5d581057d497a5036a6)

## Top of the page

Before the tabs, the panel shows the general data of the nodes:

* name, country, city, provider and OS;
* the main status of the node and traffic status;
* Communication with Remnawave;
* IP and SSH port;
* condition of the agent and the time of the last heartbeat;
* Actively jamming notifications, if enabled.

Buttons on the right:

\| Button | What does | do?
\|---|---|
\| **Axosun** | Launches a diagnostic query with the context of this node. |
\| **Silence** | Temporarily removes expected node problems from the overall alarm.|
\| **Remove** | Removes the node after confirmation. If the node is used by Flow, deletion is blocked. |
\| **Update** | Requests the current state of Remnawave, agent and installation. |

The information banners under the heading report no agent, loss of communication, unfinished installation or unprepared domain and TLS for SelfSteal.

## Review

Tab **Review** The question is “what’s going on with the node right now.”

* **Now** are the last values of the CPU, memory, incoming and outgoing network speeds.
* **24-hour state** is a timeline for warnings and emergency events.
* **Services** A short list of installed services and their current status.
* **The latest events of** are recent entries in the node log.

Clicking on the timeline section opens up the associated event, and if the metrics haven't arrived yet, the card displays an empty state.

## Health Index and Task Line

The health index shows not only the score, but also the data on which it is based, and the missing measurements should not be considered as zero load or validation.

Check the queue of the agent's tasks: the online state confirms heartbeat, but the agent may not perform orders. The queue card shows the tasks waiting and completing, the waiting time, the delay of catching and completing. Empty queue is neutral; "Slowly" or "Does not understand" requires checking the agent.

There are additional signs of problems in the host information: steal CPUs, OOMs waiting to be updated, containers and log sizes — when the agent transmits the relevant data. Fields and metrics have a help explaining the meaning.

## Metrics.

The **metrics tab** shows the time series obtained from the Axottle Agent:

* CPU and load average;
* used memory and swap;
* disk filling and disk I/O;
* incoming and outgoing network speed;
* Network errors, packet losses, and TCP retransmits
* TCP/UDP connections and conntrack;
* File descriptors, processes, uptime, BBR and qdisc.

The graph period is selected in the interface, hover over the cursor to see the value and time of the measurement, details of the composition of telemetry: [Metrics and services](https://docs.axottle.com/en/nodes/metrics-and-services.md).

## Services

Tab **Services** Shows systemd services and Docker containers that the agent can recognize.

For each installed service, you can see:

* name and type of launch;
* state (`running`, `stopped`, `failed` and others);
* the time of the last update;
* **button Restart** if the agent supports service management.

A separate block lists services from the directory that aren't on that node. It's reference information, not a breakdown list.

Restart requires confirmation. For systemd, the panel restarts the unit, for container service, the corresponding Docker container.

## Logs.

**Logs** requests the log through an agent. First, select the source: systemd-unit or allowed container.

Available parameters:

* **Strok** - volume of the magazine tail;
* **Search** - filter by text;
* **Filter** - the level or type of messages, if available for the source;
* **Update** - Repeat the request
* **Download** - save the resulting fragment.

The collection is blocked if the agent has never been installed, and if you temporarily lose communication, the panel does not create an outdated task: first restore the agent.

> [!WARNING]
>
> Before transferring support logs, check them for client addresses, domains, and other sensitive data.

## Security and signals

The **Security tab** combines profile settings, node validation and investigative signals.

### Security profile

The profile specifies the set of expected settings. After selecting, click **Save Profile**. The profile assignment itself does not change the server: the changes are made by a separate application.

### Mass actions and communication with the server

In the list of nodes, mark the lines for mass action. Status update shows the result and error for each node; [update of selected](https://docs.axottle.com/en/nodes/updates.md#обновить-выбранные-ноды) agents continues on the server after the page is closed.

With the simultaneous loss of agent and communication Remnawave panel shows possible unavailability of the server. This is a reason to check the network and power node; this signal does not automatically determine the cause of failure. Installation and import also have separate states until the emergence of fresh health confirmations.

For additional domains, use [Domains and TLS](https://docs.axottle.com/en/nodes/domains.md), rather than replacing the main domain for each new entry.

## Verification

The button **Run check** performs read-only diagnostics:

* SSH settings;
* sysctl;
* firewall;
* open ports;
* SMTP and amplification surfaces;
* fail2ban and CrowdSec.

The result of the check is recorded in the transaction log.

### Signals.

The signal unit collects related incidents, active limitations, and facts for investigation. The signal is an observation or event, not an automatic proof of a problem. The **Request E-report** button generates an additional report on the selected context.

### Application of the profile

Before application, the panel shows a preview of specific steps. Select the actions you want, check the list and confirm the launch. Firewall changes require separate explicit confirmation.

## Productivity

**Productivity** is designed to configure the server for the network load.

* **Check** checks kernel, BBR, qdisc, file limits, conntrack, THP, irqbalance, zram, journald and swap.
* **Preview** shows future changes without application.
* **Apply** - records a managed sysctl-config and applies parameters.
* **Rollback** restores the previous configuration image.

All actions are performed by the agent and recorded in the Journal.

## Domains and TLS

In the tab **Domains and TLS** are configured:

* **Domain** – used as SNI and SelfSteal address
* **DNS mode** - manual control or supported automation;
* **Cert-mode** is a method of issuing and servicing a certificate.

Main activities:

* maintain the configuration;
* check the DNS;
* issue or update the certificate;
* Check the established certificate.

As a result of the check, the Subject, Issuer, expiration date, key algorithm and certificate source are shown, and the issuance of the certificate is performed by the agent's task.

## Network

Tab **Network** It shows the addresses that the agent found on the node, the default route and its own routing rules, and from there, the address is tied to the node and gets the input or output role in the circuit.

Details: [Network addresses](https://docs.axottle.com/en/nodes/network.md).

## GeoAssets

The **GeoAssets** tab manages geo-bases on a specific node.

* **Profile** determines the set of GeoSet that must be on the server.
* **Synchronize** puts the update in the agent's queue.
* **Check** compares the current state with the profile.
* **roll back** returns the previous set if the shot is available.

The right shows the assigned profile, the status and time of the last synchronization, as well as the availability of rollbacks.

## Provider

Tab **Provider** It shows the origin of the server:

* provider;
* provider account;
* bundle or tariff package;
* plan;
* Account status and associated metadata.

This is a reference tab. The binding is set when you create a node or through your ISP integration settings.

## Agent.

If the agent is connected, the tab shows:

* hostname, OS, kernel and architecture;
* Registration time and last heartbeat;
* time of last metrics;
* address of the last connection;
* token prefix;
* The agent's current capabilities.

The capabilities update button re-requests the capabilities. The actions available depend on the agent's version and the toolkit installed on the server.

If the agent is not installed, two scenarios are available:

1. **Automatic installation by SSH** The master himself creates a temporary enrollment token, installs the agent and withdraws the token after registration;
2. **Manual Installation** - the operator creates an enrollment token and executes the command shown on the server.

Active enrollment tokens are manually installed. Unnecessary tokens can be recalled.

## Installation

Tab **Installation** Shows the latest install-recipe:

* the initial parameters of the node creation master;
* general status and progress;
* sequence of steps;
* the current step being taken;
* warnings and errors;
* output of SSH commands, if received.

The re-start button creates a new installation attempt. Before repeating, first fix the cause of the error: network, SSH access, user rights or missing dependencies.

## Settings

Edited fields:

* **Display name**;
* **Traffic status** - participation of the node in traffic distribution;
* country and provider;
* internal notes.

After the change, press **Save**.

Below are the read-only system fields: ID, slug, IP, SSH user/port, type, pools, tags, weight, priority, and Remnawave binding.

## Journal

Tab **Journal** It contains only the events of this node: the operator’s actions, the agent’s tasks, installation, verification and errors.

Use filters by type and level of event. To investigate, first find the event by time, then match it with the logs and signals in the **Security** tab.

## Verification

> [!TIP]
>
> The node panel works fully when the online agent, heartbeat and metrics are updated, the list of services is loaded, and the test log request is completed without error.

## Rollback

The page itself doesn't roll back. The backup depends on the operation:

* Performance profile – button **Rollback**;
* GeoAssets - rollback to the previous set;
* Changes in settings – return the previous values and save;
* Restart the service and read-only checks do not require a rollback.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.