Appearance
Multi-server
Administration → Servers (marked new in the sidebar) runs several AIO Panel servers from the panel you are signed in to: their health and services, the hosting accounts of all of them, new accounts on the server with the most room, and a standby that takes over when a server fails. Each server still serves its own websites and mail.

How do I add a server?
- On the other server, create an API token for an administrator (Profile → API tokens). Full access is required, because the panel reads services and metrics.
- On this server, click Add server.
- Enter a name, the other panel's URL (including
https://and the port) and the token. - Use Test connection before saving. Leave Verify TLS on unless the other panel still uses its self-signed certificate.
The token is stored encrypted. It is never shown again after you save.
How do I manage the accounts of all servers in one place?
Servers → Accounts on all servers lists every hosting account of every server, with the server it lives on, its package, its domains and its disk use. Search by username, e-mail or domain, or filter by server.
- New account creates an account on a server you choose, or Automatic: the server with the most room for its package (free disk counts for half, then free memory and idle CPU; a server whose free disk is smaller than the package's quota is skipped). The dialog shows how each server was ranked. The username and the domain must be free on every server, so accounts can later move between them. Packages are matched by name, so give packages the same names on every server.
- Open signs you in to the account on its own server, with a link that works once within a minute.
- Suspend and Unsuspend work on any server.
- Move copies the account from its server to any other one, this server included: files, databases, mail, DNS zones and cron jobs. It keeps running on its old server until the copy is complete and is suspended there afterwards; then point its domains at the new server. When the source is another server, the copy runs there and its Tasks show the progress; it adds the target to its own Servers list if needed. Moving to this server gives the source a one-day API token for the copy.
The other servers must run AIO Panel 0.3.49 or newer; an older one is listed with a note to update it. The panel reaches them with the administrator API token you added them with.
How do I keep servers from filling up?
Servers → Balance shows the disk, memory and CPU of every server. A server whose disk is fuller than the chosen limit (80% by default) is marked Full, and the card suggests which of its accounts to move where: the largest active accounts first, each to the server that stays emptiest, until the full server is 10 points under the limit and no target goes above it. Move starts one of them. Nothing moves on its own.
How do I update all servers?
Servers → Versions and updates shows the version of every server and whether a newer release is out. Tick the servers and click Update selected: they are updated one after another, and each must answer on the new version before the next one starts, so a bad release stops at the first server. This server is updated last, because its panel restarts. Websites and mail keep running on every server during its update. The progress is under Tasks.
How do I keep packages the same on every server?
New accounts and moves between servers find a package by its name, so every server should have the same packages with the same limits. Servers → Packages on every server compares this server's administrator packages with each other server's: missing there, different limits or features, or only there. Copy to … servers creates the missing packages and gives the different ones this server's limits and features (the other server applies them to its accounts at once). Packages that exist only on the other server are never deleted, and reseller packages are not touched.
How do I set up a standby server?
Install AIO Panel on a second server and add each server to the other under Servers with an API token. Then, on the primary, open Servers → Failover:
- Replicate this server to a standby: pick the standby and a schedule (every 6 hours is a sensible default). Each run backs up every account and pushes it to the standby, where it lives as a suspended replica account: files, databases, mail, DNS zones and cron jobs included.
- On the standby, Watch a primary and take over: choose the primary, the minutes without an answer that count as an outage, and whether to Promote automatically.
When the primary stays unreachable, the standby alerts you (or promotes on its own): replica accounts are unsuspended and every A record that pointed at the primary is rewritten to the standby in the zones it is authoritative for, and in linked Cloudflare zones. Preview promotion shows exactly what would change; Promote now does it by hand. Keep the registrar's nameservers pointing at both servers (or use Cloudflare) so the new addresses are served. Failing back is deliberate: replicate from the standby to the repaired primary, promote there, then Clear promotion state.
What can I do from here?
Open a server to see its CPU, memory, disk and the state of Nginx, MariaDB, Postfix and the other services. You can start, stop and restart a service from the drawer. Renaming a server or changing its location does not throw away its history; changing the URL, token or TLS setting does, and the panel checks the connection again.
This server is listed too. Its Settings tab is where you set the country and city shown to the others.