Clean server.
Any component of Axottle - panel, node, status page, subscription page - is strongly recommended to put on a clean server: a fresh system where there is nothing other than the OS and access over SSH. The reason is that the installation is not just about copying the binary. The panel installer picks up Docker, the container base, the system service, and if the domain is listed, the reverse proxy with TLS; the agent on the node manages its services, ports, and network configuration. The more the machine is worth its own, the more places it will encounter other people’s solutions:- Occupied 80 and 443. Certificate is issued on HTTP-01. If the ports are held by an extraneous process, the installation will either stop and ask them to release, or end without TLS - proxing will have to be completed by hand.
- The other control panel,, is a single Remnawave, 3x-ui, Marzban and the like, and it claims the same ports and the same proxy software, and on the node it claims the core of the proxy that Axottle manages itself.
- Foreign containers and their databases. Coincidences by port and name are found in the middle of the installation, not before it.
- Firewall and Network Configuration Manual Rules. Agent exposes its own, and the discrepancy usually pops up after the first reboot.
Axottle panel
The panel comes with a single binary file with a built-in web interface and runs as a system service.Server resources
The minimum configuration is designed for a panel, PostgreSQL and a small node park. Metric history, logs, backups and frequent health checks increase disk and CPU consumption. For a large installation, start with the recommended configuration and control the panel server with the
axottle doctor command and conventional OS monitoring tools.
The installer can deploy a reverse proxy (Caddy or Nginx) to publish a dashboard by domain with TLS. Without a domain, the dashboard is available at
http://<IP>:8080 - in this case, check that the port is open in the firewall.Nodes
A node is a server that Axottle manages through an agent.
For a node, a clean system is as important as for a panel: an agent deploys and keeps its own stack on the server, so the previous panel or its proxy core at 443 will argue with it over ports and configuration.
Read more about the installation of the agent - Installation of the agent.
Remnawave (optional)
Axottle operates in two modes:- C Remnawave – The panel connects to an existing or jointly installed Remnawave panel and controls it as a control layer.
- Autonomously (standalone) - without connection to Remnawave.
What to prepare in advance
1
Server under the panel
A clean Linux server with a minimum of 2 vCPU, 2 GB RAM and 10 GB SSD, root access, Docker and an open panel port. It is clean - on a busy machine, the installation rests on other people’s ports and services.
2
Domain (recommended)
A DNS record pointing to the panel server if you plan to publish by domain with TLS.
3
Access to Remnawave (if required)
The API address and the token, or the decision to install Remnawave together.
4
Nodes
One or more pure Linux servers that will become nodes.
Next.
Quick start.
Installation of the panel and the setup wizard.
First connection.
Connect Remnawave and the first node.
