Hub Settings ​
The Hub Settings page turns a standalone AdminBolt panel into a hub that orchestrates other AdminBolt panels through their REST API.
Overview ​
URL: /admin/hub-settings
Run this panel as a fleet hub orchestrating other AdminBolt panels via their REST API
This is the entry point to the whole area, and the one page in it that is always available. On a standalone panel the sidebar shows a single Cluster entry, and it opens this page. Once Hub Mode is on, Cluster becomes a group with the rest of the pages in it.
When Hub Mode is enabled, the panel keeps doing its own work and additionally manages the other servers:
When enabled, the Cluster section manages a fleet of servers, each running its own full AdminBolt panel. Customers keep logging into their own server's panel - the hub adds fleet-wide visibility, installation and orchestration.
For the bigger picture and the standalone/hub/node distinction, see Cluster.
Settings ​
The page holds one section, Hub Mode:
| Field | Description |
|---|---|
| Enable hub mode | Toggle that turns the panel into a hub. Its helper text reads "Unlocks the fleet dashboard, node management and the DNS cluster". Off by default. |
| Hub display name | A friendly name for the hub (for example, EU Production). |
| Minimum node panel version | The lowest panel version a node may run. Nodes below this version are flagged and blocked from migrations. Leave empty to require the hub's own version. |
Click Save to apply the configuration.
What happens after enabling ​
Turning on Enable hub mode reveals the rest of the Cluster group:
- the Hub Dashboard,
- Servers, where remote panels are connected and managed,
- the DNS Cluster, Global DNS Zones, Fleet Accounts, and Account Migrations.
These pages become useful once servers are connected to the hub. Until at least one is connected, they are available but empty.
Note: The minimum node panel version gates migrations: a node running an older panel is flagged and cannot be migrated to until it is upgraded.