Short answer: On current cPanel & WHM, Let’s Encrypt is already the default AutoSSL provider and Sectigo no longer works, so no extra plugin is needed. If WHM » SSL/TLS » Manage AutoSSL shows another provider or Disabled, select Let’s Encrypt, accept its terms and save. The hostname certificate is handled separately: the hostname must be a fully qualified name resolving to the server’s main IP, port 80 must be reachable and CAA records must allow letsencrypt.org. Confirm the active provider with whmapi1 get_autossl_providers. (Reviewed October 2026.)
Applies to cPanel & WHM 120 and later (current AutoSSL and hostname-certificate docs are marked valid for 118 through the latest version); Let's Encrypt AutoSSL provider and automatic Let's Encrypt hostname/service certificates
Table of Contents
Let’s Encrypt is the default AutoSSL provider in current cPanel & WHM and is included with the cPanel licence. Sectigo was deprecated in version 118, removed in 120, and has not run on any version since 31 December 2024, so a server still pointing at it, or set to Disabled, needs switching to Let’s Encrypt. The second half of the job is the service certificate for the hostname itself: the one that browsers see on port 2087, that mail clients see on 993 and 465, and that FTP clients see on 21. When that one is expired or self-signed, every mail client on the server complains.
Enable the Let’s Encrypt provider
On current versions the Let’s Encrypt provider is present and selected by default. If WHM shows another provider or Disabled, check and switch it from the shell (or in WHM, which is the simplest place to accept the terms of service):
whmapi1 get_autossl_providers
whmapi1 set_autossl_provider provider=LetsEncrypt
The WHM path is SSL/TLS » Manage AutoSSL, Providers tab, where you tick the terms of service checkbox before saving. Under the Options tab decide whether AutoSSL may replace certificates that were installed manually and whether it should notify users on failures; most hosting providers leave replacement off and notifications on. The Manage Users tab controls which accounts and feature lists are eligible.
Run AutoSSL and read the log
Force an immediate run rather than waiting for the nightly cron:
/usr/local/cpanel/bin/autossl_check --all
/usr/local/cpanel/bin/autossl_check --user=example
The Logs tab in Manage AutoSSL shows each domain and the reason for any exclusion. The two failures that account for most tickets are domain control validation problems. DNS validation fails when a domain’s nameservers point elsewhere and the A record does not resolve to this server; the fix is to update DNS or exclude the domain from AutoSSL in the user’s SSL/TLS Status page so it stops blocking the certificate for the rest of the account.
HTTP validation fails when port 80 is redirected wholesale to HTTPS or blocked by a .htaccess rule; cPanel normally injects an exception for /.well-known/, but custom rewrites written above it can still break it. A proxy such as Cloudflare in front of the domain also needs the DCV path to reach the origin, covered in the CAA and CDN DCV guide.
Fix the hostname certificate
The hostname certificate is separate from account certificates and is managed by checkallsslcerts. It runs daily from cron, but you can invoke it directly after fixing DNS:
hostname -f
dig +short $(hostname -f)
/usr/local/cpanel/bin/checkallsslcerts --verbose
The hostname must be a fully qualified name that resolves to an address on this server, and port 80 on that address must be reachable (otherwise checkallsslcerts reports that it could not connect to the hostname on port 80). On current builds the free hostname certificate comes from Let’s Encrypt, so any CAA records on the hostname’s domain must allow letsencrypt.org. If the hostname does not resolve, set a proper A record first or change the hostname in WHM » Networking Setup » Change Hostname and rerun. Once issued, the certificate is installed automatically across the services; you can review or replace it at WHM » Service Configuration » Manage Service SSL Certificates, which lists cPanel/WHM/Webmail/Web Disk, Dovecot, Exim and FTP with each certificate’s expiry.
Verify
Check each service from outside:
openssl s_client -connect mail.example.com:993 -servername mail.example.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -dates
openssl s_client -connect server.example.com:2087 </dev/null 2>/dev/null | openssl x509 -noout -subject -dates
The issuer should be a public CA, not the cPanel default, and the dates current. In a browser, https://server.example.com:2087 should show no warning. The SSL expiry check script can monitor these ports continuously.
Pitfalls
The most frequent mistake is expecting the AutoSSL provider selection to affect the hostname certificate; it does not: hostname and service certificates are replaced by checkallsslcerts during the nightly upcp run, and on current versions they are free Let’s Encrypt certificates. Another is a mail client configured for the customer’s own domain rather than the server hostname, which produces a name mismatch unless the account’s AutoSSL certificate includes the mail. subdomain; recent cPanel versions do include it, but check the SAN list. Finally, Let’s Encrypt applies rate limits per registered domain, so a reseller with fifty subdomains of one parent domain can hit the weekly cap; the log names the limit explicitly.
cPanel hostname SSL at a glance



Official documentation (checked 9 October 2026): cPanel docs: Manage AutoSSL · cPanel docs: The Let's Encrypt Plugin · cPanel Support: When will Sectigo be deprecated and removed from cPanel · cPanel Support: How to change AutoSSL providers in WHM · cPanel docs: Automatic SSL Certificate Replacement · cPanel docs: The checkallsslcerts Script · cPanel Support: Checkallsslcerts domain resolved to an IP address that does not exist on this server · cPanel docs: The autossl_check Script · WHM API 1: set_autossl_provider · cPanel docs: Manage Service SSL Certificates · Let's Encrypt: Rate Limits
Related guides: Fix WordPress “cURL error 28: Failed to connect” caused by Imunify360 or CSF · CVE-2026-65638, 65639 and 67402 explained: patching the CSF Messenger and URLGET remote-code flaws · Whitelist IPs and countries in Imunify360 from the CLI.
Frequently asked questions
Does switching to the Let’s Encrypt AutoSSL provider also change the hostname certificate?
No. The hostname and service certificate is issued by a separate process, checkallsslcerts, which on current builds orders a free Let’s Encrypt certificate for the hostname whatever AutoSSL provider is chosen for accounts.
How long does AutoSSL take to issue certificates after enabling Let’s Encrypt?
A forced run completes for a typical account in a minute or two. Validation for hundreds of accounts can take an hour, and Let’s Encrypt’s per-domain rate limits may defer some domains to later runs.
Can I undo the change and go back to the Sectigo provider?
No. Sectigo was removed in cPanel version 120 and has not run on any version since 31 December 2024. To stop AutoSSL instead, select Disabled under Manage AutoSSL » Providers or run whmapi1 disable_autossl.
