Skip to content

AdminBolt for Blesta ​

AdminBolt for Blesta is a Blesta server module that connects Blesta to the AdminBolt hosting control panel. It provisions and manages AdminBolt hosting accounts from Blesta, and adds resource usage and single sign-on to the Blesta client area.

What it does ​

  • Provisioning - create, suspend, unsuspend, and terminate hosting accounts.
  • Package changes - an upgrade or downgrade in Blesta moves the account to another hosting plan, matched by the exact AdminBolt plan name.
  • Password changes - from the service edit screen in the Blesta admin area.
  • Client area - a tab with resource usage and a Log in to Control Panel button that opens the panel with a one-time login link. The login link can be used once and is valid for 30 minutes. It does not bypass two-factor authentication: when the account has 2FA turned on, the client still enters the second factor.
  • Reseller accounts - a server can use a reseller's key pair, so its accounts are created under that reseller, or an administrator key can assign the server's new accounts to a reseller.

Requirements ​

  • Blesta 5.x, with PHP 8.1 or newer and the curl extension.
  • AdminBolt 1.8.2 or newer. The module looks accounts up by username and plans by their exact name, which older panels do not support.
  • An API key and secret, issued under API Keys in the admin panel or under Reseller API Keys in the reseller panel. Use a dedicated key pair per Blesta installation, with the key's IP whitelist turned on.

Setup (step by step) ​

Follow these steps in order; each links to the details below.

  1. Create API credentials in AdminBolt. You need both the key and the secret for the server.
  2. Install the module into Blesta (see Installation).
  3. Add the AdminBolt server in Blesta (see Server configuration).
  4. Create your packages with AdminBolt as the module (see Package configuration).

Installation ​

  1. Download the module package from get.adminbolt.com/bolt-blesta.zip and extract it. The package holds one folder, bolt-blesta. The link always serves the latest release; every release is also kept at https://get.adminbolt.com/downloads/bolt-blesta/v<version>/bolt-blesta-<version>.zip.
  2. Copy the adminbolt folder from bolt-blesta to components/modules/ in your Blesta installation.
  3. In Blesta, go to Settings > Company > Modules > Available and install AdminBolt.

Server configuration ​

Add a server for the AdminBolt module in Blesta and enter:

SettingValue
Server LabelA name for this AdminBolt server in Blesta.
Panel URLThe address of the AdminBolt panel API, with its port, for example https://panel.example.com:8443.
API KeyThe API key issued in the panel.
API SecretThe secret that belongs to the key.
Reseller API credentialsTick this when the key pair belongs to an AdminBolt reseller. Accounts are then created under that reseller, and Reseller ID (optional) is ignored.
Reseller ID (optional)Used only with an administrator key: new accounts on this server are assigned to that reseller.

The connection is checked when you save the server.

Package configuration ​

Create a package, select the AdminBolt module and the server, and enter the plan name in AdminBolt Hosting Plan. The name has to match the plan in AdminBolt exactly.

How services map to accounts ​

BlestaAdminBolt
Service domainMain domain of the account
Service usernameSystem username. When it is left empty, the panel generates one from the domain with a random suffix.
Package plan nameHosting plan, matched by exact name
Server Reseller IDThe reseller a new account belongs to

The module remembers which AdminBolt account belongs to each service. When a service has no account recorded, for example an imported service, the module finds the account by its username.

Errors and troubleshooting ​

  • The module records the panel's response to create, password change, suspend, unsuspend, terminate, and package change in the Blesta module log. Usage, account lookups, and single sign-on are not recorded there.
  • An error from the panel appears in Blesta with the message the panel returned.
  • Terminating a service whose account no longer exists in AdminBolt succeeds, so the service can still be closed in Blesta.
  • For errors such as 403 IP address not whitelisted, a plan that is reported as not found, or a rate limit, see Troubleshooting in the Billing Integration API guide.