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.
I'm having the same issue with two of my sites, this is my first renewal with certsage so I thought I might be doing something wrong. I'm also on namecheap with the exact same error.
Usually this has to do with whether or not a cPanel instance of the hosting provider makes an internal exception/"pointer" for each "functional" (i.e. internal) subdomain name. Traditionally I've only acquired certificates covering these three domain names for each of my own domains (and some "extra" subdomain names when hosting multiple domain names on one cPanel, which is slightly more complex):
domain.com
mail.domain.com
www.domain.com
I've had mixed results covering the whole lot of internal subdomain names due to the inconsistency over time with how cPanel handles the HTTP-01 challenges used be Let's Encrypt to verify domain control.
If you're hosting multiple domain names on one cPanel, I highly recommend following what I've written here:
Thanks; that results in the same error. I guess this is because it tries to do the challenge through cpanel.vermeer.tv, which is probably redirected by the server internally.
Indeed, there is no website currently installed. I use this mainly for mail.
The crt.sh-page you link to seem to suggest that the certificate was issued on Sept 12, which seems about right. However, I'm not familiar with that website, so maybe I'm reading things wrong. Can you point me to the line that states that it was issued on 11/11?
I'm trying to get a new cert, because this one will expire on Dec 11.
Whoops, I misread the date. Thought it already was 12 November and probably mistaken the "11" from the expiry date as the November mark.. I was waaaaaaaaaaaaaaaaayy off
Unfortunately, if cPanel isn't cooperating, CertSage won't be able to acquire a certificate covering those subdomains. However, there's usually no real harm in not covering those with your own certificate since cPanel will use its own in a sideways way. You can reach the same functionality with your certificate via:
It's a bit unsettling for other users to go to webmail.vermeer.tv and be confronted with a warning about an insecure connection, though. cPanel is fine, that's just for me anyway.
If someone has found a solution or workaround for this, I'd be happy to learn about it!
