Overview
Installing an SSL certificate on your cPanel or WHM server is essential
for encrypting data and building trust with your website visitors. However, SSL setup
doesn’t always go smoothly, and many users encounter common errors during installation. In
this guide, we’ll walk you through how to identify and fix frequent cPanel SSL and WHM SSL
issues, so you can secure your site without frustration.
1. Expired SSL Certificates
What It Means:
An expired SSL certificate simply means the validity period has
ended. If the certificate isn't renewed in time, browsers like Chrome or Firefox
will show alarming messages such as:
- "Your connection is not private"
- "This site is not secure"
This not only affects trust but can also harm your SEO and
traffic.
How to Fix It:
- Log in to cPanel
- Go to Security > SSL/TLS Status
- Check the expiration dates
- Log in to WHM
- Go to SSL/TLS > Manage SSL Hosts
- If the certificate is expired:
- Renew it through your SSL provider
- Or issue a new certificate directly from cPanel (especially if using
AutoSSL)
Tip:
Set up auto-renew reminders or use AutoSSL to avoid future expiration issues.
2. Domain Mismatch Error
What It Means:
A domain mismatch happens when the SSL certificate is issued for one domain (like www.example.com) but used on another (like example.com or a subdomain). This triggers a "certificate not valid for this domain" error in browsers.
How to Fix It:
- Log into cPanel or WHM
- In cPanel, go to SSL/TLS
- In WHM, visit Manage SSL Hosts
- Check which domains the certificate is valid for
- If there's a mismatch:
- Generate a new CSR (Certificate Signing Request)
- Reissue or purchase a new certificate for the correct domain
- Consider a wildcard SSL if covering multiple subdomains
- Install the updated certificate via the SSL/TLS manager in cPanel or WHM
Tip:
Always double-check whether you're securing www and non-www versions of your domain.
3. Self-Signed Certificate Warning
What It Means:
Self-signed certificates are not issued by a recognized Certificate Authority (CA), so browsers flag them as untrusted. While they encrypt data, they’re not suitable for public websites.
How to Fix It:
- Purchase a trusted SSL certificate from a reputable CA (like Sectigo, DigiCert, or Let’s Encrypt for free options)
- Install the certificate via:
- cPanel > SSL/TLS > Manage SSL Sites
- Or in WHM under Install an SSL Certificate on a Domain
Tip:
Never use self-signed certificates for production websites. They're best suited for internal testing or development environments only.
4. Certificate Expired Error
What It Means:
Just like any license, an SSL certificate has an expiration date. If it’s not renewed in time, browsers will immediately show a “certificate expired” error — breaking trust with your visitors and potentially affecting SEO.
How to Fix It:
- Log in to cPanel → Go to Security > SSL/TLS
- Check your certificate’s expiration date
- Renew the SSL via your provider or create a new certificate using AutoSSL or Let’s Encrypt
- Reinstall the new certificate using cPanel or WHM
Pro Tip:
Set calendar alerts for certificate renewals, or activate automatic renewal features whenever possible.
5. Missing Private Key
What It Means:
This error shows up when the private key (created during the CSR process) is missing or wasn’t saved correctly. Without it, you can’t install the certificate.
How to Fix It:
- If the private key is lost, generate a new CSR
- Use the new CSR to get a fresh SSL certificate from your provider
- Reinstall the certificate via cPanel or WHM
Reminder:
Always download and store your private key securely during the initial certificate setup.
6. Too Many Redirects (ERR_TOO_MANY_REDIRECTS)
What It Means:
When forcing HTTPS, improper or duplicate redirect rules (especially in the .htaccess file) can cause a redirect loop, leading to this error.
How to Fix It:
- Open your site's .htaccess file (found in your public_html folder)
- Review any existing HTTPS or redirect rules
- Remove or correct any conflicting redirects to ensure a clean HTTPS path
Use Case:
Avoid applying multiple HTTPS rules at both the server and application level (e.g. in WordPress settings and .htaccess).
7. Website Says “Not Secure” Even After SSL Installation
What It Means:
This typically happens due to mixed content — when some website elements (like images, CSS, or JS files) still load over HTTP instead of HTTPS.
How to Fix It:
- Update all internal site links (CSS, images, JS files) to use https://
- Use tools like Why No Padlock to scan for mixed content
- Update your content management system settings to reflect HTTPS (e.g. WordPress URL settings)
Use Case:
Consider a plugin or script to automatically force HTTPS on all assets.
8. “SSL Installation Failed” in cPanel
What It Means:
This generic error message usually points to file permission issues, configuration conflicts, or missing components on the server.
How to Fix It:
- Log in to WHM
- Check error logs for details (under /usr/local/cpanel/logs/error_log)
- Fix permission issues or configuration errors
- Retry the SSL installation via cPanel or WHM
Note:
Ensure that the SSL certificate and private key match and are properly formatted.
9. “SSL Certificate Verification Failed” in WHM
What It Means:
This error occurs when the Certificate Authority (CA) cannot verify the certificate due to firewall blocks or DNS/network problems.
How to Fix It:
- Make sure your server can reach CA endpoints (no DNS or IP blocks)
- Temporarily disable the firewall to test connectivity
- Retry the SSL certificate installation process
Security Tip:
If you disable the firewall, re-enable it immediately after verification.
10. Unable to Force HTTPS
What It Means:
Your website isn’t redirecting to HTTPS even after SSL installation. This could be due to missing rules in .htaccess or not enabling HTTPS redirect in cPanel.
How to Fix It:
- In cPanel, go to Domains
- Toggle Force HTTPS Redirect ON
- Or manually edit .htaccess and add this rule:
sudo dnf install vsftpd
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Reminder:
Always back up .htaccess before making edits.
11. Incomplete Certificate Chain (Missing Intermediate Certificates)
What It Means:
If browsers still show a security warning even after SSL installation, it may be due to missing intermediate certificates, also known as an incomplete certificate chain.
How to Fix It:
- Log in to cPanel or WHM
- Go to SSL/TLS > Manage SSL Hosts
- Ensure all intermediate and root certificates are installed along with your primary certificate
- If missing, download the intermediate bundle from your SSL provider and add it manually during installation
Hint:
Most Certificate Authorities offer a bundled file that includes the full certificate chain — always use that if available.