To be specific, I am talking about using a LetsEncrypt (LE) cert for WHM itself, not a domain being managed by these tools.
I'm well aware that I could install Certbot and reconfigure the underlying web server by hand, but generally, I'm averse to doing this as I could see the changes being trivially overwritten at some point by WHM or cPanel (or flagged by a security addon). For instance, when I used WHM's change hostname function, a new certificate signed by cPanel Inc was automatically installed.
I'm already using the LetsEncrypt AutoSSL plugin, but it explicitly calls out:
The Let’s Encrypt™ provider plugin does not generate hostname certificates for your system’s services. It only generates SSL certificates for your cPanel accounts.
Configuration
- The server's hostname is
web1.example.com
- WHM is accessed from either
whm.example.com
orweb1.example.com:2087
. Either of these access methods presents a cPanel Inc. signed certificate forweb1.example.com
- The underlying server is a VPS I have root access to.
- The server is authoritative for its own DNS (that is,
ns1.example.com
andns2.example.com
andwhm.example.com
) all point to the same IP on the same VM. example.com
has a cPanel account in WHMcpanel.example.com
points at this account and uses the AutoSSL LE certificate
One note: The underlying server's CPanel/WHM was migrated from a shared hosting arrangement by the webhost's technical support team, so there may be vagaries in its configuration that are non-standard.
Basically, I want to stay within WHM's "happy path" if at all possible. If not, and I need to make changes behind its back to make this work, that's fine too.
In summary: What is the right way to get WHM to use a LE certificate?
whm.example.com
so that AutoSSL could fetch the certificate? Then I'd think it would just be a matter of symlinks.whm.example.com
stops pointing to it and starts pointing to a new account skeleton). I deleted it with no issue, and did see that AutoSSL did get a LE cert.