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:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:NAMECHEAP
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):CPANEL V3
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):CERTSAGE 1.42
It produced this output:
urn:ietf:params:acme:error:unauthorized
198.54.114.253: Invalid response from https://cpanel.telegraphics.com/.well-known/acme-challenge/55Rs4dY-XOC8xSS-O5tncZTQkdwgxVHxDIxVmUqXwaY: "\n\n\n\n \n "
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:NAMECHEAP
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):CPANEL V3
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):CERTSAGE 1.42
The cpanel subdomain isn't served from the webroot directory where certsage.php is located (usually public_html) and therfore CertSage can't help you fullfill the ACME HTTP01 challenge for the cpanel subdomain.
In my own personal experience, I have never been able to acquire a certificate using CertSage that covers cPanel's "internal function" subdomain names because they don't use the public_html directory or subdirectories of public_html as their webroot directories containing certsage.php. In short, there's nowhere to put certsage.php for CertSage to service those "internal function" subdomain names. If you have somehow figured out how to accomplish this, I am eager to know how. Do you have AutoSSL turned on and that's what is acquiring your Let's Encrypt certificates?
Keep in mind that GoDaddy's (or their affiliate's) cPanels automatically provide free Let's Encrypt certificates using AutoSSL (I believe) for their more expensive hosting plans, but not for their most basic hosting plans. Did you downgrade your hosting plan recently?
Namecheap's web hosting most likely already uses AutoSSL for acquiring certificates. Only two of your recent certificates (from November of last year) could have been acquired using CertSage. It looks like AutoSSL immediately overrode those. Apparently AutoSSL (or Namecheap) recently cut down the subdomain names for which they acquire a certificate. CertSage does not (yet) autorenew certificates, so we should be seeing a very different certificate history than we are for your domain name if CertSage were involved.
If you switched to Namecheap as your registrar around fall of last year, that would explain what happened. CertSage doesn't use DNS-01 challenges to prove domain name ownership/control. It uses HTTP-01 challenges, which do no allow acquiring certificates covering wildcards (*) or those "internal function" subdomain names. By having your registrar and hosting with one provider, builtin solutions (like AutoSSL) can utilize DNS-01 challenges.
None of those certificates (after November of last year) could have been acquired using CertSage.
Notice how the domain name boxes are empty when you go to your CertSage copies for either of the domain names you've mentioned. That means there is no certificate in a CertSage data directory for either of those domain names. Did you delete the CertSage data directories?
While troubleshooting this I deleted all Certsage data and reinstalled. I think when I moved the changed the registrar. It stopped working on the internal sub domains. I had done at least two CertSage SSLs on the two domains previously. So when it was a redirect from GoDaddy to namecheap servers it worked. I'm now trying to turn on AUTOSSL via Cpanel but I can't seem to get there from here.
Do you have AutoSSL turned on and that's what is acquiring your Let's Encrypt certificates?