Not every release is a landmark and this one does not pretend to be. AdminBolt 1.2.2 is a quality-of-life release: it takes a few things that technically worked and makes them behave the way you already expected them to. The theme, if there is one, is control. You get finer control over bandwidth, forwarders that stop losing your mail and a Hub that tells you when a node has gone quiet instead of leaving you to find out.

Here is what actually changes day to day.

Bandwidth you can reason about

Three changes land together and they are best understood as one story.

First, limits. Admins and resellers can now set a bandwidth limit on an individual hosting account that overrides whatever the plan says. Leave it blank and the account keeps the plan default. Set it to 0 and the account is unlimited. Clients cannot touch this themselves, so it stays an operator lever. It is the escape hatch for the account that does not fit its plan, without building a whole new plan around one customer.

Second, the counter finally resets. Bandwidth usage now tracks the current calendar month instead of a lifetime total, so it rolls over on its own at the start of each month. No more numbers that only ever climb.

Third, the units line up. The client dashboard now reports bandwidth in the same units as the admin panel, everywhere it appears, including the usage warning and the checks that run on a plan change. What you see in one place is what you see in the other.

Forwarders that keep a copy

Email forwarders used to be forward only. Mail came in, went straight out to the forwarding address and never landed in the mailbox behind it. That is fine until someone wants both and then it is a support ticket.

1.2.2 adds a simple Keep a copy toggle. Turn it on and each message is delivered to the forwarding address and to the local mailbox, so the copy is waiting in webmail whenever the user goes looking for it.

Knowing when a node goes quiet

If you run a fleet, the failure you actually fear is the silent one: a node that stops reporting and sits there looking fine until a customer tells you it is not. The Hub dashboard now watches for exactly that. A node that stops checking in is flagged Stale, then Offline if it stays quiet, with the last time each node was seen shown right next to it. It turns a silent gap into something you can spot at a glance.

Smaller fixes worth naming

A release like this is mostly a stack of small corrections and a few are worth calling out because you would have felt them.

Suspended clients used to be bounced back to the login form with no explanation, which looks exactly like a broken password. They now get a clear message that the account has been suspended. The client IP blocker handles CIDR blocks and IP ranges more consistently, so one block is enforced as a single rule instead of surprising you. And the admin panel is now kept out of search engine results, while the client and reseller panels are unaffected.

On the PHP side, imported domains no longer trip over "The requested PHP version was not found" during a migration; they pick up the correct version on their own. Enabling Redis now keeps the igbinary and msgpack extensions switched on and labelled as required, so you cannot accidentally break PHP by turning off something Redis depends on.

Two more worth a line: the client SSH Terminal page no longer errors on open and the update screen has a follow-up fix so it stops getting stuck on an out of date view mid-update.

Upgrading is one click

Upgrading is done entirely from the panel. Open the Updates screen in the admin UI and apply 1.2.2. The one-click updater shows live progress, runs the version-specific steps for you and reports when it is done. No terminal, no manual package commands. Take a backup first out of habit and expect only a brief interruption on a typical VPS.

Nothing here is an opt-in tax: single-server and multi-server panels both pick these changes up the same way.

Tell us how it goes

That is 1.2.2. Not loud, but the kind of release you feel every day once it is in. Tell us how it lands on Discord, the community forum or through the contact form.