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

# First connection

> Connect a Remnawave panel and register your first node in Axottle.

After installing the panel and completing the setup wizard, connect Remnawave if you use it, register a node, and apply your first Flow.

> [!NOTE]
>
> For administrators.
> Required permissions: panel administrator; root access to the node server.
> Prerequisite: complete [Quick start](https://docs.axottle.com/en/getting-started/quickstart.md).

## Step 1. Connect Remnawave

If you selected Remnawave mode during installation, connect its panel.

**1. Open connections**

In the sidebar, open **Services → Remnawave**.

**2. Enter the API address and token**

Enter the Remnawave API address and access token. When installed together, the connection may be created automatically.

**3. Test the connection**

Run the test. The panel displays success or an error, along with latency.

**4. Synchronize**

Start synchronization to load local snapshots of users, nodes, hosts, and profiles.

For details, statuses, and troubleshooting, see [Remnawave connections](https://docs.axottle.com/en/remnawave/connections.md) and [Synchronization](https://docs.axottle.com/en/remnawave/synchronization.md).

> [!TIP]
>
> In standalone mode, without Remnawave, skip this step and register a node.

## Step 2. Register your first node

Choose one of the two agent installation methods below. For either method, a clean server is strongly recommended for the node. See [Clean server](https://docs.axottle.com/en/getting-started/requirements.md#чистый-сервер).

### Automatically over SSH

**1. Add a node**

Open **Infrastructure → Nodes**, click **Add node**, and choose installation on an existing server over SSH.

**2. Enter SSH access details**

Enter the address, port, user, and authentication method, then complete the wizard.

**3. Install the agent**

Axottle checks the server, issues a temporary enrollment token, installs the agent, and revokes the token after registration. You do not need to create a token manually.

**4. Wait for registration**

After installation, the agent registers and connects; the node status changes to online.

### Manually

If Axottle should not connect to the server over SSH, add a node, open its **Agent** tab, generate an enrollment token in **Manual installation**, and run the displayed command on the server. The token is needed only for manual installation.

For details, see [Node enrollment](https://docs.axottle.com/en/nodes/enrollment.md).

## Step 3. Create your first connection scheme

Open **Infrastructure → Configs → New Flow → Regular Flow**. Add an entry node, connect Gateway → entry → Internet, and configure the connection. Wait for it to save, click **Apply changes**, review the plan, and apply it. Then check **Health** and connect with a client. See [Flow overview](https://docs.axottle.com/en/connection-units/overview.md) and [Builder](https://docs.axottle.com/en/connection-units/constructor.md).

## New user tour

During onboarding, creating the first configuration opens a regular Flow immediately: enter its name and client label. After saving, the tour moves to the canvas and entry setup. Outside the tour, the regular wizard also lets you choose a transit pool; use a regular Flow for the first client connection.

## Verify

> [!TIP]
>
> The Remnawave connection is connected and synchronization completed successfully; the first node is online on the dashboard; and the health dashboard shows no critical problems.

## Rollback

* You can delete an incorrect Remnawave connection. This removes local snapshots but does not affect the Remnawave panel itself.
* You can decommission and delete the node. Enrollment tokens can be revoked or expire automatically.

## Next steps

> [card] [Hardening](https://docs.axottle.com/en/security/hardening.md)
>
> Essential security hardening steps.

> [card] [Health](https://docs.axottle.com/en/health/overview.md)
>
> How to interpret and respond to statuses.


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