Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: smiths.org.uk
I ran this command: CertSage
It produced this output:
220.127.116.11: Invalid response from https://cpanelemaildiscovery.cpanel.net/autodiscover/autodiscover.xml: 404
My web server is (include version):
Server Name sxb1plzcpnl490290
cPanel Version 94.0 (build 19)
Apache Version 2.4.54
PHP Version 7.4.29
MySQL Version 5.7.38-cll-lve
Shared IP Address 18.104.22.168_64
The operating system my web server runs on is (include version): Linux x86_64
My hosting provider, if applicable, is: tsoHost
I can login to a root shell on my machine (yes or no, or I don't know): I don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): see above
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot): not using certbot
autodiscover.smiths.org.uk redirects to
https://cpanelemaildiscovery.cpanel.net/autodiscover/autodiscover.xml which is never going to work with regard to issuing a certificate. Do you actually require a certificate for all those hostnames? If not, just leave the ones out you don't require a certificate for, especially
autodiscover.smiths.org.uk. If you do require a certificate for this hostname, I have absolutely NO idea how to stop cPanel from redirecting...
Welcome to the Let's Encrypt Community!
I'm the author of CertSage. @Osiris has the right idea. Usually you only want to put domain names together on a certificate if they share the same webroot directory (
mail.smiths.org.uk). The other
x.smiths.org.uk names are directed at cPanel and thus CertSage cannot acquire a certificate for them. As for
www.gs-c.smiths.org.uk, I suspect those share a webroot directory of their own inside of
public_html. Try putting a copy of
certsage.php in that directory, changing line 18 of that copy to
public $dataDirectory = "../../CertSage"; , and acquiring a separate certificate for just those two domain names.
Many thanks @griffin and @Osiris. Bang on. I'd forgotten the notes with CertSage about subdomains and now that all makes sense. Sorted!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.