Hosting Accounts (AutoSSL Management) ​
The Hosting Accounts page allows administrators to enable or disable the AutoSSL feature for individual hosting accounts in the system.

Overview ​
AutoSSL is used to automatically issue and install SSL/TLS certificates for hosted domains. On this page, you can manage AutoSSL status per account, giving you granular control over which accounts benefit from automatic certificate management.
URL ​
/admin/auto-ssl-hosting-accounts
The screen is the AutoSSL tab of the SSL area, beside Certificates and Issuance History, so it is reachable from the panel rather than by its address alone.
Since panel 1.9.2, an AutoSSL progress section above the accounts shows how far AutoSSL has got. See AutoSSL progress.
Description ​
Each row in the table represents a hosting account. Select accounts using the checkboxes and use the bulk Enable AutoSSL / Disable AutoSSL buttons to control which accounts are included in the AutoSSL issuance process.
This can be useful in scenarios where:
- You want to disable AutoSSL for accounts that use custom certificates.
- You need to troubleshoot certificate issues per account.
- A customer explicitly disables automatic SSL provisioning.
Interface Elements ​
| Element | Description |
|---|---|
| User | The username of the hosting account. |
| Selection | Checkbox used to select accounts for bulk actions. |
| Search Bar | Allows you to search accounts by username. |
| Per Page | Sets how many accounts to display per page (pagination control). |
Actions ​
- Enable AutoSSL / Disable AutoSSL - Bulk actions applied to the selected accounts.
- Search - Filter accounts by name to quickly locate the one you want to manage.
Enabling AutoSSL ​
Use the Enable AutoSSL action to turn on automatic certificate issuance for the selected hosting account.
AutoSSL for new accounts ​
Since panel 1.9.5 you choose whether a new hosting account starts with AutoSSL on. The button above the list shows the current choice: New accounts: AutoSSL on or New accounts: AutoSSL off. Click it to open AutoSSL for new hosting accounts with the switch Turn AutoSSL on for new hosting accounts.
The switch is on until you change it, so new accounts start with AutoSSL on, as before. Turn it off when you issue certificates another way, for example with a purchased certificate or through Cloudflare. The hint reads "When off, a new hosting account starts with AutoSSL off and no certificate is ordered for its domains. After you turn AutoSSL on for the account in this list, the next scheduled AutoSSL run orders its certificates. Existing accounts keep their setting."
The choice also applies to accounts that come in through an import, unless the imported account carries its own AutoSSL choice.
The administrator API reads and sets the same choice: GET /api/autossl/settings returns new_accounts_enabled, and PUT /api/autossl/settings with {"new_accounts_enabled": false} changes it.
Parked domains ​
Since panel 1.9.5 a parked domain is covered by the certificate of the domain it is parked on, together with its www name when the parked domain has its www alias on. AutoSSL does not order a certificate of its own for a parked domain. A run of bolt-cli run-auto-ssl --domain=<parked domain> skips it and names the main domain to run it for instead.
Since panel 1.9.7:
- The main certificate follows its parked domains. Adding a parked domain, or saving or renaming one, asks AutoSSL to order the main domain's certificate again when that certificate does not name the parked domain yet. The nightly run and
bolt-cli ssl-health-checkask the same way: one order for the main domain, however many of its parked domains are missing. A certificate uploaded for the main domain is never replaced by such an order. - No certificate of its own. Issuing, uploading, generating a self-signed certificate, or disabling SSL for a parked domain is refused, in the panel and over the client and administrator APIs, with a message that names the main domain to manage SSL on. The client SSL Certificates list shows the main domain's certificate on the parked domain's row.
- The update moves parked domains onto the main certificate. Certificates AutoSSL ordered for parked domains under earlier versions are removed once the certificate the main domain is served with names the parked domain and its
wwwname. A certificate uploaded for a parked domain is kept. A parked domain still served by a web server configuration of its own keeps its free certificate, and AutoSSL goes on renewing it. - Domains with parked domains. A domain other domains are parked on cannot be deleted before them, and a parked domain runs with the PHP settings of its main domain. See Deleting a domain and Parked domains in the client panel.
What the switch covers ​
The per-account switch is honoured everywhere AutoSSL runs: the nightly sweep, the runs started for a single domain, and the health check all skip an account it is switched off for. Naming a domain of such an account explicitly reports that the account has AutoSSL off, instead of returning what looks like a success.
Automatic SSL for hosting domains ​
Beyond per-account control, AdminBolt issues and renews certificates for hosting domains automatically. A scheduled job runs bolt-cli run-auto-ssl once a day at 02:30 and does two things:
- Issues certificates for active hosting domains that do not have one yet, using the certificate provider set in General Settings (Let's Encrypt by default).
- Renews certificates that have auto-renew enabled and have 7 days or less remaining before they expire.
Since panel 1.9.1, a certificate whose type is empty or from an older panel version is renewed by its issuer: a Let's Encrypt or ZeroSSL certificate renews on the usual schedule, a domain whose certificate is no longer installed gets a new one, and a certificate from another authority is kept and reported when its renewal would be due. A certificate uploaded by hand is stored with automatic renewal off, so AutoSSL leaves it alone. To see every domain AutoSSL does not renew, and why, run:
bolt-cli run-auto-ssl --list-unmanagedSee Security commands for the reasons it reports.
The job is installed by bolt-cli setup-cron-jobs. When you update the panel, the entry is added automatically if it is missing, so existing servers pick up automatic issuance without any manual step.
You can also run it on demand:
bolt-cli run-auto-sslUse --domain=<domain> to limit the run to a single domain, or --force to renew every auto-renew certificate regardless of its expiration date. See the CLI reference for details.
New domains are picked up hourly ​
A domain created before its DNS pointed here does not have to wait for the next nightly run. An hourly pass issues certificates for active domains that do not have one yet. A domain that is not pointed at this server is skipped before any certificate authority is contacted, which keeps the account clear of a provider's validation limits.
Note: This job covers certificates for hosting domains. The panel's own hostname certificate is handled separately by
bolt-cli run-hostname-auto-ssl, which runs daily at 03:00. The automatic hostname renewal keeps a purchased hostname certificate installed on General Settings in place.