Dashboard ​
The Dashboard is the first screen after signing in: a real-time overview of the hosting infrastructure, and the shortest route to anything that needs you.
Overview ​
URL: /admin/dashboard
Counters ​
Five counters run across the top: Total Accounts, Domains, Resellers, Databases, and Mailboxes. Each shows the change over the past week, so you can tell growth from a flat week without opening a report.
Server load ​
CPU, RAM, and disk for the machine you are signed in to, as bars with the raw figures beside them. This is the current reading, not an average.
Needs attention ​
The findings from Health, summarised. Each line states what is wrong and why it matters, and View health opens the full page with the next action for each item.
An empty panel here means the checks ran and found nothing, not that nothing was checked.
Since panel 1.9.4 the card also warns while root can sign in over SSH with a password, naming the SSH settings that allow it, with a link to SSH Access. See Root login over SSH with a password.
Whitelisting your own address ​
Repeated failed panel sign-ins ban the address they come from, on the panel port. Since panel 1.9.0, while the Fail2Ban whitelist is empty, the dashboard offers to whitelist the address you are connecting from. Whitelist followed by the address adds it, labelled as the administrator address added from the dashboard, and Not now dismisses the offer. When the address cannot be whitelisted on the server, the panel says so and the offer stays, so you can try again. Whitelist the address only when it is your own, not one shared with other people, because failed sign-ins from a whitelisted address are never banned.
Nodes overview ​
Remote AdminBolt panels connected to this one as a hub. On a standalone server the panel invites you to add your first node. See Cluster.
System status ​
A one-line verdict per subsystem: Web, Database, Mail, DNS, and Background Jobs. View all services opens Health, where each of them can be restarted or re-provisioned.
The Background Jobs row counts the panel's own background work. It shows how many jobs have failed, in red, or, when none has failed, how many are queued; hover over it to see both numbers, Waiting and Failed. Since panel 1.9.2 the row opens the Background Jobs page, where failed jobs are run again or deleted. A failed job keeps the row red until you do one of the two.
AI usage ​
Tool calls made by the AI assistant over the last seven days. Empty until the assistant is used.
Top accounts and domains ​
Top Accounts by Usage ranks accounts by disk and bandwidth, and Top Domains by Mailbox Count ranks domains by how many mailboxes they hold. Both link to the full report.
Integrations ​
Since panel 1.9.0 the dashboard carries an Integrations card listing the official AdminBolt integrations, with View all integrations leading to the Integrations page.
Updates ​
Whether the panel is on the latest release, with the version you are running. Use Settings > System > System Updates to act on it.
Right after the install ​
Since panel 1.9.4, a fresh install runs its first update check within minutes instead of waiting for the hourly check. The same goes for the local mail server check on the Email Dashboard, the DNS and reverse DNS rows of the hostname Status, and the outbound IPv6 mail check on Health.
When the update status is unknown ​
While the card reads Update status unknown, the line under it says why and what to do:
| Line on the card | What to do |
|---|---|
| The first update check has not finished yet. | Wait a few minutes. If the message stays, open Health to see whether scheduled tasks are running. |
| The last update check is more than 90 minutes old. | Open Health to see whether scheduled tasks are running. |
| The AdminBolt package repository is not configured on this server. | Contact AdminBolt support to restore it. |
| An update was being installed, so the check was skipped. | The check runs again within the hour. To check now, open System Updates. |
| This server could not look up the AdminBolt update server. | Check the server's network and DNS settings. |
| The AdminBolt update server could not be reached. | Check that the server can open outbound HTTPS connections. |
| The AdminBolt update server did not answer in time. | Wait for the next hourly check, or open System Updates to check now. |
| The management agent on this server did not answer. | Restart it with systemctl restart bolt-agent, as the card says. |
| The update check could not be completed. | Wait for the next hourly check, or open System Updates to check now. |