AdminBolt 1.9.2 adds a Background Jobs page. It shows the jobs that are waiting, running or failed. Failed jobs can be run again from the panel or the admin REST API. Servers with many sites get more room to grow. Web servers keep serving as sites are added, AutoSSL works through large numbers of domains and the hub DNS sync stays quick on large hubs. Every setting on a PHP version's configuration page now reaches the server. The release also fixes secondary DNS on the hub, LiteSpeed installs and removal, SSH Access, Resolver Configuration and WordPress installs.
Background jobs
- Background Jobs page (AB-1282, AB-1825): Health > Background Jobs lists the jobs that are waiting or running and the jobs that failed, in plain words. For a failed job you see what went wrong and when. The technical details sit behind Details, with sensitive values masked. You can run a failed job again or delete it. Run all again runs the failed jobs again, a batch at a time. Delete broken jobs removes the jobs that can never run again. The admin REST API offers the same actions under
/api/background-jobs. The dashboard and Health link to the page when jobs have failed or are waiting. Long tasks, such as the package check after a system package upgrade, run to completion.
Servers with many sites
- Web server capacity (AB-1688): Apache, LiteSpeed and PHP-FPM keep serving reliably as more sites are added to a server. Existing servers get this on upgrade, without a restart of these services.
- AutoSSL at scale (AB-1692): AutoSSL handles servers with many domains. The AutoSSL tab shows its progress: domains done, issued, failed, skipped and left for a later pass.
- Hub DNS sync at scale (AB-1843): The hub DNS sync stays quick on hubs with thousands of zones. Resync DNS still updates every zone when you ask for it.
PHP
- PHP version settings (AB-1774, AB-1775): Every php.ini and extension setting on a PHP version's configuration page reaches the server. That includes Implicit Flush, the OPcache settings and the Imagick settings. The page reports the configuration as applied once the server uses it. Settings saved earlier carry over on the next save.
- CloudLinux alt-php (AB-1776, AB-1777, AB-1956, CloudLinux Only): Every alt-php extension switch reaches the server. An alt-php version offers only the extensions it ships. Saved alt-php settings take effect at once. The Web Server tabs leave out PHP Migration, because websites move to alt-php in Settings > CloudLinux > Isolation Report.
- PHP versions of different families (AB-1768, AB-1769, AB-1778): Remi PHP, alt-php and LSPHP of the same release are separate versions. Each one lists only the websites that run it. It checks only those websites before it is removed. Installing or removing a Remi PHP version leaves the LSPHP and alt-php builds of that release as they are. The install and removal log names each step.
- PHP-FPM pool settings (AB-1785, AB-1786): The PHP-FPM Configuration tab of PHP Domain Assignment shows Environment Variables, Ping Path, Ping Response and Terminate Timeout. What you save there takes effect for that domain. Settings that could not take effect are removed from the page. Only administrators can set these values.
bolt-cli rebuild-php-fpm-pools reports each domain that failed and exits with an error when any did.
- Run PHP Script cron template (AB-1961): The Run PHP Script cron template in the client panel uses the PHP version of the account's main domain and the account's home folder.
Web servers
- Web Server tabs (AB-1814): The Web Server pages show only the tabs that apply to the server's web server. The engine cards link only to pages that apply. An engine that is not installed shows Install instead.
- LiteSpeed install and removal (AB-1760, AB-1761): A failed LiteSpeed Enterprise, OpenLiteSpeed or LSAPI Engine install names the missing package and the next step. Uninstalling LiteSpeed Enterprise sets the files it left behind aside instead of deleting them. A later OpenLiteSpeed install starts clean.
- LSPHP during a LiteSpeed install (AB-1762, AlmaLinux Only): A LiteSpeed Enterprise, OpenLiteSpeed or LSAPI Engine install sets up LSPHP for every installed Remi PHP version. This includes versions installed outside the panel.
- LiteSpeed Enterprise and OpenLiteSpeed apart (AB-1767, AB-1783): Manage services tells LiteSpeed Enterprise and OpenLiteSpeed apart. The LiteSpeed Enterprise actions act only on LiteSpeed Enterprise. Switch to MyApache is hidden and refused while Apache is already the active web server.
- Phusion Passenger on Apache (AB-1779): The Phusion Passenger is not installed warning and Install Passenger show when Apache serves applications without Passenger.
- Web server API (AB-1855): LSPHP versions stay listed and manageable when no web server uses them, with a note saying so. Web server API errors carry a correlation ID. The Service status tile matches the Engines card. Removing OpenLiteSpeed keeps the LSPHP versions with all their extensions. Applying a LiteSpeed licence key leaves a stopped LiteSpeed stopped.
DNS cluster
- Secondary DNS (AB-1802, AB-1834, AB-1890): Each secondary DNS server receives new zones. SRV records resolve on the hub and on the secondary DNS servers. This covers zones from nodes and from cPanel and Plesk sources. When the Secondary DNS role cannot be turned on for a node, the panel shows the node's reason. A node that is already a secondary keeps its zones. Register again repairs its registration.
Server settings
- SSH Access and Resolver Configuration (AB-1839): Both pages show the server's current settings. Saving changes only the fields you changed. Every other setting stays as it is. Turning root login off asks for confirmation. Changing the SSH port also opens the new port in the firewall. Re-configuring SSH on the Services page keeps its port, root login and allowed addresses.
Websites and applications
- WordPress installs (AB-1837, AB-1952): When the plan has no free database left, the WordPress installer says so before it changes anything. A failed install removes the database and database user it created. It names the reason and the next step. Go to Admin signs in to WordPress through single sign-on. This also works while an administrator impersonates the account. If single sign-on fails, Go to Admin opens
/wp-admin.
- Install Dependencies for Node.js (AB-1841): Install Dependencies uses the Node.js version selected for the application. When it fails, it shows what the command printed.
- Git Version Control (AB-1708): Git Version Control clones a repository into a new or empty folder. A failed clone removes only what it created. The page opens for accounts whose plan includes Git Version Control.
Mail, databases and backups
- Autoresponder time zone (AB-1900): The autoresponder schedule names the time zone of its dates and times. A schedule that has already started can be saved unchanged.
- MariaDB database creation (AB-1901): When the hosting account password has to be reset before a MariaDB database can be created, the panel says so. Nothing is created until then.
- Backup destinations (AB-1902): When the saved settings of a backup destination cannot be read, the backup stops. The message names the destination and the fix. The destination shows Settings unreadable until its settings are entered again and saved.
- Admin phpMyAdmin page removed (AB-1682): The admin phpMyAdmin settings page is gone. Administrators open the panel databases with Adminer. Customers keep phpMyAdmin.
Fixes and smaller changes
- Panel log access (AB-1966): The panel log folder and its files have restricted access.
Install
curl -sSL https://get.adminbolt.com/install.sh | bash
Upgrade from 1.9.1
- Log in to the Admin Panel.
- Open System, then System Updates.
- Click Check for updates and review the release notes.
- Click Install update if a newer version is available.
