Reviewing the configured WHM AutoSSL provider and account policy

Confirm server-administrator responsibility and review existing certificate arrangements. Record any commercial certificates that should not be replaced and check that the domains can complete the provider’s validation.

1. Open Manage AutoSSL and review the currently selected provider and its details. Record the provider name and the active server policy.
2. Review the provider’s terms and required options before selecting or changing it. Save the authorised configuration.
3. Check the account’s package feature list and Manage Users policy. Resolve an explicit account disable or feature exclusion where appropriate.
4. Review notification and replacement settings, especially whether AutoSSL may replace an invalid or expiring non-AutoSSL certificate.
5. Run a targeted account check when needed and inspect its log and pending status. Avoid repeatedly triggering server-wide checks to diagnose one domain.

The intended account should participate in the configured issuance process and obtain coverage for names that pass validation. Monitor renewal failures rather than assuming initial issuance guarantees future success.

If the customer interface offers no AutoSSL action, diagnose the account through the authorised WHM controls. DNS, CAA, proxy and validation-path issues still require correction before issuance can succeed.

A provider change can affect certificate issuance across many accounts. Before changing it, review existing certificates, accounts excluded from AutoSSL and any applications relying on separately installed certificates.

Read the terms and capabilities shown for the available provider, then test the intended workflow on a non-critical account. Confirm that the account's domains can complete validation and that the resulting certificate is installed for the correct service.

Should I replace every valid certificate immediately?

Do not assume this is necessary or appropriate. Review the provider's renewal behaviour and existing certificate management before forcing changes. Record the old configuration and a recovery plan so that a server-wide adjustment does not become an unplanned outage.

When a particular domain fails, examine its validation log instead of repeatedly switching providers. DNS, reachability and domain authorisation problems may remain regardless of provider choice. Root-level WHM instructions apply only to authorised server administrators. If you use our shared hosting or a reseller package without this control, contact us with the affected domain and error. Do not attempt to alter server-wide certificate settings through an account-level workaround.

Coverage depends on the provider, account and supported validation method. Verify the actual requested names and DNS-control requirements rather than assuming every domain automatically receives wildcard coverage.

• Reading AutoSSL logs for a domain-validation failure
• Replacing hostname certificates for WHM and mail services
• Enabling the cPanel HTTPS redirect without a redirect loop
• Choosing a cPanel update policy and maintenance window

• cPanel: Manage Autossl
• cPanel: SSL TLS Status