AdminBolt 1.4.0: International Domain Names, Login Shortcuts and a Panel-Wide Security Pass

AdminBolt 1.3.0 was about bringing things into the panel: mail from other servers, resource limits for resellers, 18 new languages. 1.4.0 is about names and doors. Domains can now be written the way their owners actually write them, login pages sit on addresses people already use and more than 60 changelog items tighten what the panel accepts and who gets to act on what.

Here is what actually changes day to day.

Domains the way your customers write them

To a large part of the internet, a domain like bücher.example is a perfectly ordinary name. As of 1.4.0, AdminBolt agrees. Internationalised domain names can be added and used across the panel: they are stored as Punycode under the hood and shown in their readable Unicode form, so what you see on screen is the name as its owner knows it.

If you host customers in markets where Cyrillic, Greek, Arabic or CJK domains are everyday reality, the panel no longer makes them transliterate their own brand to use it. The domain reads the way it reads on their business card.

Login pages where people already look

Every hosting panel has its own idea of where the login page lives. End users do not keep up: they bookmark one address, type it for years and expect it to keep working wherever their site happens to be hosted.

1.4.0 meets them there. Account domains now answer on familiar paths: yourdomain.com/cpanel opens the panel login, yourdomain.com/webmail opens webmail and /panel ships as a third default. Bookmarks keep working, muscle memory keeps working and there are fewer "how do I get to my email" tickets in your queue.

You stay in charge of the whole thing. The paths live in the admin panel as a Login Shortcut URLs setting, so you can customise them, add your own or switch the feature off entirely if your setup has other plans for those URLs.

If you move accounts in from other panels, this is one of those small features that makes the change invisible to the people who matter most: your customers' customers.

More than 60 items of quiet hardening

The bulk of the 1.4.0 changelog is a long security and access-control pass. Like the best security work, it asks nothing of you. There is nothing new to configure and nothing to relearn. Things simply check more and assume less.

A few threads run through the list. Actions that touch hosting accounts, databases, email, mailing lists and network settings now verify account ownership before they run. Inputs across the panel, from certificate issuance to database backups to protected directory credentials, are validated on submit. File and configuration operations use restricted path handling. Git got a dedicated round of attention: clone URLs are checked against what is allowed, remote connections verify SSH host keys and repository operations require a valid user context.

Two more items deserve a mention. Communication between the panel and bolt-agent authenticates with a valid token on every request. And sensitive values now stay out of process listings and logs, so what should be private stays private.

The technical changelog in the panel footer lists every item with its ticket number, all sixty-plus of them, if you want the full picture.

Upgrading is one click

Upgrades run entirely from the panel. Open the Updates screen in the admin UI, apply 1.4.0 and watch the live progress while the updater runs the version-specific steps for you. Take a backup first out of habit and expect only a brief interruption on a typical VPS. Single-server and multi-server panels pick the release up the same way.

New to AdminBolt? Installation is a single command:

curl -sSL https://get.adminbolt.com/install.sh | bash

Tell us how it goes

That is 1.4.0: domains in their owners' alphabet, login pages where users look for them and a panel that quietly checks its locks. Tell us how it lands on Discord, the community forum or through the contact form.