> ## 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.

# Installation of the agent

> How to install Axottle Agent manually or SSH from the node page

Both installation methods are located on the node page in the **Agent** tab.

## Before installation

> [!WARNING]
>
> Node is strongly encouraged to take **pure** The agent manages the node's services, its ports and network configuration and deploys its own stack on it. The former panel on the same server (single Remnawave, 3x-ui, Marzban and the like), its proxy kernel on 443 or the manual rules of the firewall will argue with the agent for the same ports and configurations. [Clean server.](https://docs.axottle.com/en/getting-started/requirements.md#чистый-сервер).

Starting a new server is almost always faster than cleaning the old one: it is more difficult to demolish someone else’s panel to the end than it seems, and the remnants of its services pop up already under traffic.

## New server through master nodes

In **Nodes → Add nodu**, the wizard consistently asks for name, location, SSH, Remnawave, main domain, DNS, profiles and additional services, installation and monitoring. Without a domain, the DNS step is skipped. The entered data is saved when you go back and create an error; before starting, check the final plan.

For the usual addition, the initial traffic mode is `standby`, in training it is `active`. The binding of an existing Remnawave node retains its runtime. The installation and import states do not confirm health until new observations become available.

Cloudflare can be configured in the wizard; additional domains are added later to [Domains and TLS](https://docs.axottle.com/en/nodes/domains.md).

## SSH installation

1. Open **Nodes** and select the server.
2. Go to the tab **Agent**.
3. Run the SSH installation wizard.
4. Enter the secret to connect.
5. Run a connection check.
6. After a successful inspection, confirm the installation.

The wizard creates a one-time enrollment token, connects to the server, installs the agent, waits for the first heartbeat and recalls the temporary token. You do not need to release an enrollment token before launching the SSH master. The detailed result is stored in the **Installation**.

## Manual installation

1. In the tab **Agent**, find the block **Manual installation** and click **C generate enrollment token**.
2. Copy the team formed by the panel.
3. Run it on a server with root rights.
4. Return to the panel and wait for the status of `online`.

Enrollment tokens are only for manual installation. They're disposable and time-limited.

## Existing node and runtime ownership

For an already connected Remnawave node, select the binding of an existing record instead of creating a new one. The panel rechecks it through the live API and uses the existing runtime; one outdated snapshot is not enough.

If someone else's or an unrecognized installation is detected, the bootstrap stops before it's replaced. If the wizard offers to take control of the installation, study the target and confirm that action. The routine procedure stores a backup before being replaced. Re-installation must not silently remove someone else's Remnawave container or reset its configuration.

## Verification

> [!TIP]
>
> Tab **Agent.** It shows hostname, OS, capabilities and fresh heartbeat. **Installation** It does not contain unfinished steps.

## Re-installation

If the installation ended in an error, open the **Installation tab**, correct the cause of the last unsuccessful step and run the wizard again.


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