Multi-server management

Pro plan

Multi-server management (fleet) is part of the Pro plan.

If you run several servers, Fleet lets you group them into a single panel for central monitoring — no need to open each panel separately.

Add a server to the fleet

Go to Fleet → Add server and enter the name and panel URL of the other server. The hub pings that URL to report online/offline status.

Live metrics (optional API token)

To see real CPU / RAM / disk and the running version of each server, paste an API token from that server (create it under Settings → API tokens on the remote panel). The hub then pulls metrics every 30 seconds and caches them, so the dashboard stays populated even when the page is closed. The token is stored encrypted at rest; without a token, a server is monitored for online/offline only.

Because panels use self-signed HTTPS by default, the hub pins the server’s certificate (SHA-256) when you add it and only sends the token over a connection matching that pinned cert — preventing eavesdropping / MITM. The token is never sent over http:// or before the cert is pinned. If the certificate changes, the hub flags a possible MITM and stops pulling metrics until you remove and re-add the server.

Offline alerts

The fleet_down rule on the Alerts page notifies you (Telegram / Email) when a fleet server fails to respond several times in a row, and again when it recovers.

Migrate websites between servers

Switching VPS or provider is usually an afternoon of pain: rsync/scp each folder, mysqldump and re-import, fix configs, cron, permissions… MyPanel turns all of that into a few clicks. Fleet → Migrate websites moves one or more websites (with files + databases) between this server and fleet servers.

When to use it:

• Switch VPS / provider — spin up a new server, install MyPanel, move every site over, repoint DNS.
• Upgrade specs — move a heavy site to a bigger machine without a long outage.
• Split or consolidate — pack many sites onto one server, or peel a site off onto its own.
• Build a standby — clone a site to a second server.

Steps:

1. Pick a From (source) and To (target) — each is either this server or a fleet server (one that has an API token). Works both ways: push out or pull in.
2. Tick the websites to move, choose include database (default) and overwrite if the domain already exists on the target.
3. Click Migrate — see per-site results right there.

Safe and automated for you:

• Transferred over the encrypted, cert-pinned channel (anti-eavesdrop/MITM) — never exposed online.
• Databases recreated with the exact name/user/password, host/port auto-adjusted for the target, so the site connects immediately — no manual edits.
• Re-deployed automatically on the target (container built, nginx configured).
• On mid-way failure it cleans up the partial work for a clean retry; the source site is not stopped — you only touch it after cutting over DNS.

Caution

The target must be writable (not read-only). MyPanel does not change DNS — after migrating, point DNS to the target and re-issue SSL. The source site is not stopped automatically. The MVP supports image / dockerfile / nixpacks / WordPress / reverse-proxy build kinds (static coming later).

The DB port in the WordPress / DATABASE_URL environment is auto-adjusted for the target (even when the two servers use different native/docker DB modes). If your app uses a custom-named DB connection variable, re-check its host/port after migrating.

Remove a server

Click Delete on a server to remove it from the fleet (this doesn’t affect that server — it just stops monitoring it here).

Note

Each server still needs its own Pro license to unlock its own Pro features. Fleet is the monitoring & orchestration layer on top.