I am wondering how I can go about generating certificates (and or keys and or whatever else might be necessary) locally in order to upload the files to my shared hosting provider, so that I can install additional SSL certificates beyond the free ones that were provided.
I can’t seem to find a “download” button anywhere on the CertBot website.
How can I download CertBot and generate some certificates?
I’m running Windows 10. Is this possible to do on Windows?
Server: Apache 2.4.39
OS: Linux (unsure what distro; kernal: 2.6.32-954.3.5.lve1.4.66.el6.x86_64)
If you’re doing this to install shared certificates on a shared hosting provider (rather than locally on Windows), could you share some information about your shared hosting? That’s the information that counts.
For example, what company provides the shared hosting? Is the control panel cPanel or Plesk or something else? What is your domain name?
Otherwise, you can try to manually issue and install the certificate. Keep in mind, these certificates are only valid 90 days, which means you’d have to repeat the process at least that often. You don’t have to download an ACME client to do this, you can do it using your browser.
I really don’t care if I have to manually update the SSL certificates every 3 months. My big concern is getting SSL certs for my other domains without paying as much as the domain itself for an additional SSL certificate.
I have done it many times . Namecheap don’t help as they want to sell you their Comodo certificates.
I use “ssl for free” - https://www.sslforfree.com - to generate the LetsEncrypt certificates and then install them using cPanel. The downside is that I have to renew each one manually every three months.
There was a report that they signed a contract with Comodo, prior to the launch of Let's Encrypt, which obligates them to only provide Comodo certificates in their integrated services. Last November, @_az found this comment apparently by their CEO
Hello Fej, to be honest, we signed an exclusive contract with Comodo before Let's Encrypt even existed. The length of that contract is ten years. It's put us in a tough situation as far as what we can offer out of the box to our customers. While our customers can still install LE on our hosting services on their own, we can't actively do this for them. The only other option here is to break that contract which will cost us millions of dollars and it's something that I continue to consider.
This makes me think that this is much less of an ongoing deliberate decision by Namecheap, compared to, say, GoDaddy.