Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

WHM Service Certificates: Install, Reuse and Verify Safely

Published

WHMSSL

WHM service certificates secure endpoints such as the panel, SMTP and IMAP. They are separate from a customer’s website certificate. Changing the wrong certificate can interrupt mail clients or administrator access.

Check the intended service first

Use authorized WHM access and open Service Configuration > Manage Service SSL Certificates. Record the service, hostname, current coverage, issuer and expiry. Keep a protected recovery copy and an alternative administration route before replacement. A valid certificate for a website is not necessarily valid for the server hostname.

Install or reuse deliberately

  1. Select the affected service rather than changing every service at once.
  2. Use Browse Certificates to select an existing appropriate certificate, or provide the issued certificate and matching private key through the trusted panel. Include the issuer’s required intermediate chain.
  3. Inspect any autofilled data. Autofill does not prove the names, key or chain are correct for this service.
  4. Apply the certificate only to the intended services. Follow WHM’s completion/restart prompts for the installed version; do not assume one blanket daemon restart covers every service.

Do not reset as routine troubleshooting

Reset Certificate replaces the current certificate with a self-signed one. This can create trust failures and is not a harmless renewal button. Prefer diagnosing the actual expiry, hostname, chain or automatic-issuance failure before resetting anything.

After installation, reconnect to each affected hostname and service without bypassing warnings. Confirm the expected certificate is presented and that renewal is owned by the correct mechanism. Keep private keys out of tickets, screenshots and shared text files.

Reference: cPanel service-certificate management.

Reviewed October 15, 2026. Documentation review; no service certificate or daemon was changed.

Related guides

Account services are unavailable until the production backend is configured.