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

# Creating a server through the provider

> Order VPS from the master node, the choice of tariff and OS, the installation of the agent and the analysis of unfinished orders.

Order begins in **Nodes → Add node → New server · via** provider. Before that, [connect your](https://docs.axottle.com/en/providers/accounts.md) account with support for server creation. `settings.manage` and `nodes.create` permissions are required.

## Ordering and installation

**1. Select your account and configuration**

Specify your account, region, tariff and operating system. The wizard shows the compatible Ubuntu and Debian images available. If there is no suitable image, select a different tariff or update the directory.

**2. Check the price**

Check the currency and payment period. Public IPv4 is automatically connected and can be paid separately; taxes and additional resources are calculated according to the terms of the provider.

**3. Set up the node.**

Pass the remaining steps of the wizard: node assignment, domain and necessary software. IP and SSH key Axottle will prepare automatically.

IP is unknown before ordering. For automatic DNS, use Cloudflare or select the TLS setting after the server is created and add an A record when the address appears.

**4. Confirm the order.**

At the final step, check the settings, mark **Confirm the order of the paid server** and click **Order and install Z**.

> [!WARNING]
>
> After ordering, the provider can start charging fees. Closing the wizard, browser or Axottle does not cancel the server and payment.

## Order stages

Axottle saves the operation, registers the SSH key, orders the server, receives IPv4, waits for the SSH, and installs the agent and the selected software. The operation continues in the background. It can be opened in **Providers → Create servers** (`/new/providers/orders`).

| Condition | Value | |
| - | - | - |
| Preparing the SSH key / Checking the registration of the | key Preparing access from the provider | |
| Order server / Check the result of the order | Creating VPS and matching the response | |
| Check IPv4 connection / Waiting for IP and SSH | readiness Getting the address and waiting for access | |
| Install agent and software | Server created, installed node | |
| Node is ready | You can go to the node and installation log | |
| Order rejected by | Execution stopped; no | automatic repeat order |
| Attention | Surgery suspended, you need to study the cause of | |

## If the order is not completed

Open **Error Log**: it contains the step, time, message and, if saved, the provider's response. To install the already created node, go to its log.

If there is a server ID from the provider, the server already exists and can be charged. Fixing the installation of this node does not require the purchase of another VPS. For the state of **Attention is required** button available **Check again**: first disassemble the error and compare resources in the office of the provider.

An indefinite API response after an order does not prove that the server is not created. Do not launch a new independent order until you have checked the result of the previous one.

## Verification

1. The order ended with **Node ready**.
2. The node card has the expected IP, the agent is in communication, the installation was completed without errors.
3. In the provider’s office, one expected server with the selected configuration has been created.
4. If a domain has been used, check the DNS and TLS after the IP appears.

## Rollback

Deleting a completed record from history only removes the record and its stored log. Axottle nodes and the ISP server are saved.

To stop paying for an unnecessary server, delete the resource separately in the provider's office, pre-checking the data and dependencies of Flow. Removal of the resource may be irreversible. Do not use deleting the history record as a cancellation of an order.

Real paid orders within the reconciliation were not fulfilled.


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