Skip to main content
Install the Axottle panel and complete the setup wizard in a few steps.
For whom: Administrator deploying Axottle Required rights: root/sudo on the panel server. Time: about 10-15 minutes.

Before you start.

Make sure that requirements: Linux with systemd, Docker, open port 8080 (or domain with a proxy), curl/wget are met.
The panel is strongly recommended to put on clean server. The installer raises Docker, the database in the container, the system service and the reverse proxy with TLS: on a machine where another panel, your web server on 80/443 or extraneous containers already live, the installation rests on occupied ports and remains without TLS. What exactly conflicts - Clean server.

Step 1: Installation of the panel

Run an official installer with root rights. It will deploy the panel in /opt/axottle, raise the database in the container, create a system service, and (if you specify the domain) configure a reverse proxy with TLS.

Last stable release

In the SSH server terminal, copy the entire command. It downloads the installer from get.axottle.com and launches it after successful boot:
--lang en selects English. You choose the method of access, proxy, domain and installation of Remnawave in the installer itself; you do not need to fill in arguments in advance. Bootstrap takes The latest GitHub release public repository Axottle/axottle-releases, downloads the installer and the release archive from the same tag. So the installer code and the panel binary always match the version; branch main It’s not used for installation.
Normal installation does not require GitHub token: a public release repository, curl, Internet access, Linux with systemd and root/sudo rights.

Specific version

To set a specific release, add --version:
Replace v0.1.0 with a published tag. If there is no such release or asset for the server architecture, the installation will be completed before the system changes.

Optional installation parameters

The settings answer the relevant questions in advance, which the installer skips. For normal installation, use the command above. If you want to pre-set the domain and Caddy, replace panel.example.com with your domain:
You cannot transfer --repo, --release, --artifact or --artifact-url: the source of the release is intentionally fixed on the official Axottle/axottle-releases. The version is selected only by the --version parameter.

Script check before launch

To view bootstrap before starting, run these commands in turn:
All settings of the installer are available through:
The installer supports automatic mode via flags, and it can also co-install Remnawave if desired.

If questions are missed or an old domain appears

In some versions, running through curl … | bash mistakenly triggers a response timeout: after 15 seconds, the installer takes the default value. The answer entered later may fall into the next question. Use the main method above, running the downloaded file in the SSH terminal. If the old answers are restored after the interrupted installation, they are taken from /opt/axottle/.install.state. To re-select the parameters, follow:
--reset-state only resets saved installer responses. It does not delete the installed panel and its data. The domain, explicitly transmitted through --panel-domain, is still in use without question.

Re-start after interruption

In the current interactive installer, the domain recovered from the saved answers is shown for reconfirmation: you can leave it or enter another. A domain explicitly transmitted by a flag takes priority. In a launch without a terminal, the stored value is used without an interactive question. The installer itself prepares the required rsync on the minimum supported systems. If the dependency preparation is not completed, eliminate the cause and repeat the installation; do not consider the presence of a part of the files as a completed installation. When selecting nginx, the first issuance of the certificate must be completed before the HTTPS configuration is launched, the result is verified using the actual HTTPS route of the panel, and an error in the certificate or occupied port does not turn the selected installation with the domain into a successful installation without TLS.

If you play Remnawave at the same time

The installer will ask two things. How to publish. The first item is “for reverse proxies, domain and TLS,” and it’s labeled as recommended. It’s not a flavour: the Remnawave web interface works just like that, on a bare port, it breaks the connection with the proxies and HTTPS requirement. If the proxy isn’t there yet, the installer will pick up Caddy; if 80 and 443 are already holding your caddy or nginx, it will sign up the site block; if the ports are busy with something else, the installer will say that and roll back to the local version instead of a fight over the port. The local and the port options will only be available from Awave. Which version. List - the last five fixed versions from the registry, floating tags (latest, dev, bare major) do not fall into it. Unavailable registry or non-interactive launch gives the default version, not the installation stop. Remnawave can then be updated from the panel, see Update Remnawave. Upon completion, the installer will show the panel address: a domain (e.g., https://panel.example.com) or http://<IP>:8080.

Step 2: First entrance and setup wizard

Open the address of the panel in the browser. When you first start, the wizard of the initial setting will open:
1

Administrator

Creating an administrator account: login and strong password, and you’ll enter the panel with that data.
Setup is complete after the administrator account is created.
Domain Publishing and TLS are configured during the installation phase (installator reverse proxy) rather than in the wizard. If the panel only opens on IP:порт, check the DNS and proxy settings.

Step 3. Verification

Open the panel address in the browser, log in under the administrator account and make sure that the home page has loaded.
On the panel server, additionally check the service:

Rollback

Before deleting, save a backup copy of if the data is important.
It will show which components will be removed, and ask separately about the associated data. Additional diagnostics and maintenance commands are collected in the directory CLI.

Next.

First connection.

Connect Remnawave and the first node.

Security after installation

Mandatory hardening steps.