Replacing hostname certificates for WHM and mail services

Confirm the hostname resolves correctly and obtain a valid matching certificate, private key and required chain. Save the existing working configuration and plan for brief management or mail-service reconnection.

1. Open Manage Service SSL Certificates and inspect certificate names and expiry for the affected service.
2. Use an appropriate existing certificate or the Install a New Certificate form. Select only the services intended to use that hostname certificate.
3. Provide the matching certificate, private key and CA bundle through the secure administrator interface. Check their identity before installation.
4. Install and complete any required service restart prompt, including the cPanel service daemon when applicable.
5. Test new connections to WHM, SMTP and IMAP as relevant using the exact hostname customers or administrators configure. Verify trust, name coverage and expiry.

The selected service should present the intended trusted certificate. A browser test against a website port does not substitute for testing the affected mail or management service.

Reset Certificate creates a self-signed replacement and is not an ordinary trusted-certificate renewal button. If clients still warn, inspect the hostname, chain and actual certificate served rather than disabling certificate verification.

Only a certificate covering the actual WHM hostname is appropriate. A certificate for a different domain will create a hostname mismatch even if a trusted authority issued it.

• Changing a WHM server hostname with DNS and certificate checks
• Reviewing the configured WHM AutoSSL provider and account policy
• Restarting one affected service from WHM
• Checking WHM service status before restarting anything

• cPanel: Manage Service SSL Certificates
• cPanel: Automatic Hostname SSL Certificate Replacement