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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Yes, they said they allow but do not have it installed. That I am welcome to install it. I have no clue where to start other than knowing I can get it from here.
Here's the reply from chat.
The Let's Encrypt certificates can be surely installed on our hosting plans. However, we do not have any tools that can install/implement their certificates. Thus, they should be obtained from the provider directly and installed manually.
I got the staging key showing in the CertSage directory. It took me awhile as I changed my main domain and troubleshoot why not working (was pointing to wrong server).
But my website is not up yet, so I should wait before I acquire production key?
At this point I really have no idea what to see. I received notification that my SSL was to expire but that's for the previous main domain. This new main domain never had SSL as it wasn't hosted.
I am looking at using Wordpress. If I cannot make a go of it, I'd look at Shopify. Will the process be the same?
While CertSage has some optimizations for cPanel, you can use it in pretty much any webhosting scenario, possibly with a little tweaking. I've included some guidance for WordPress in the official release pages in this community. (See @_az's link above, which points to the latest official release and information.) You don't need to wait (and probably shouldn't wait) until your site is fully formed to get your production cert. If you were able to successfully acquire a staging cert then you are almost guaranteed to be able to successfully acquire a production cert. Let be know if you run into any trouble.
Hello again,
I tried the staging first. It said successful. Then today I requested the production one and followed the steps up to updating of contact and all said successful. But still showing Not Secure. I went to the .crt to edit but it's all encrypted.
Also, in the Domains to Force to https redirect, the button is grayed out and an alert says there is none or the SSL is not valid.
When I open the .crt (or even the key files) what I see is starts with
-----BEGIN CERTIFICATE-----
MIIFLzCCBBegAwIBAgISBCySK/ReslONR70NnCYbb0xpMA0GCSqGSIb3DQEBCwUA
Yep. That's PEM format as it should be. The "header" and "footer" lines are called the "armor". The seemingly-encrypted block inside the armor isn't actually encrypted. It's Base64-encoded DER, not that you need to know or understand what that means to succeed here. I'm merely providing deep information should you (or anyone who comes along) wish to know more. The information and tools that follow are enough to bring anyone up to nearly an expert level when it comes to certificates. Please don't feel that you need to absorb it all.
Per the chain of trust, there are actually three certificates in the following order in your .crt file:
So I tried again. In the end where I have to force to https, it said cannot enable force redirect to https because my server is not configured to support it.
Is that the end of it other than confirming with namecheap that it is so? and that I have to pay for https?
Or is there something I missed along the line?
I cannot see that you've even acquired a production certificate for cardsetcetera.com, but it may not have been reported yet:
Once you have acquired a production certificate, you need to actually install that certificate into cPanel using the button on your CertSage page. Simply acquiring a production certificate does not automatically install it into cPanel.
