So your www-version uses storehippo.com, not your server. Isn't there a certificate management? It may be impossible to install a certificate, may be storehippo has an integrated solution.
Your non-www version redirects to a not-defined domain name:
This is the first time we are generating the certificate for this particular domain so how can it show the certificate as expired? If the certificate is not generated, where is it getting the old certificate from?
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:
I can login to a root shell on my machine (yes or no, or 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):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
If you have a CNAME entry to another server (not the server you run your ACME-client), you can't create a certificate via http-01 validation. The ACME-client should run on the server with that domain name.
You can create a certificate via dns-01 validation.
But to use / install that certificate, you have to install it on that other server.
So if you use a CNAME, that moves your domain to storehippo: Are you able to install there a certificate?
Perhaps not.
Looks like your server isn't configured and can't talk with Letsencrypt.
But this isn't relevant because you can't install the certificate with your CNAME setting.