You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my Cpanel site, there is a domain. Let's call it example.com. The hosting infrastructure creates a bunch of artificial hostnames underneath it:
autodiscover.example.com
cpanel.example.com
And 5 more
They are hosted effectively together. A single cert is used for all of them. In Cpanel's UI, there is a single line for all of them. When renewing the certs, you want to specify them all, so that the back-end at Let's Encrypt places all those hostnames into in the cert. So the certbot line goes:
certbot run -a cpanel -i cpanel --cpanel-credentials cred.ini -d example.com,autodiscover.example.com,...
Now, when you run that line, it installs the cert for example.com, then gives the following error:
Error installing the SSL certificate for autodiscover.example.com : The certificate could not be installed on the domain “autodiscover.example.com”.
Sorry, autodiscover.example.com is not one of the domains on your account.
Indeed it's not. As in, it's not a domain as a unit of hosting. Not a zone. But autodiscover.example.com doesn't need a separate cert, either. The one that covers example.com will cover it too.
The error message is not fatal (the cert is installed, after all, where it matters), but it's annoying and it throws off batch processing - as far as surrounding code is concerned, the certbot invocation has failed.
The text was updated successfully, but these errors were encountered:
In my Cpanel site, there is a domain. Let's call it
example.com
. The hosting infrastructure creates a bunch of artificial hostnames underneath it:They are hosted effectively together. A single cert is used for all of them. In Cpanel's UI, there is a single line for all of them. When renewing the certs, you want to specify them all, so that the back-end at Let's Encrypt places all those hostnames into in the cert. So the certbot line goes:
Now, when you run that line, it installs the cert for example.com, then gives the following error:
Indeed it's not. As in, it's not a domain as a unit of hosting. Not a zone. But
autodiscover.example.com
doesn't need a separate cert, either. The one that coversexample.com
will cover it too.The error message is not fatal (the cert is installed, after all, where it matters), but it's annoying and it throws off batch processing - as far as surrounding code is concerned, the certbot invocation has failed.
The text was updated successfully, but these errors were encountered: