# Installing Cert on Namecheap.com Shared Hosting

**URL:** <https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227>\
**Category:** Help\
**Created:** [August 6, 2019, 4:23am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227 "2019-08-06T04:23:07Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 4:23am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/1 "2019-08-06T04:23:07Z")

</div>

**Has anybody been able to install Let’s Encrypt SSL certificates on [Namecheap.com](http://Namecheap.com) shared hosting before? If so, can you please, please, please help me figure out how to do it. Thanks**

Domain: **[http://lipsynched.com](http://lipsynched.com)**

Server: **Apache 2.4.39**

OS: **Linux (unsure what distro; kernal: 2.6.32-954.3.5.lve1.4.66.el6.x86\_64)**

Host: **[Namecheap.com](http://Namecheap.com) Shared Hosting**

Root: **No**

Control: **cPanel 78.0 (build 34)**

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [August 6, 2019, 4:58am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/2 "2019-08-06T04:58:21Z")

</div>

Hi @bmf,

NameCheap has a contract with another certificate authority which prevents them from integrating Let’s Encrypt support in a convenient way.

You can find some earlier threads about NameCheap on this forum

[https://community.letsencrypt.org/search?q=namecheap%20cpanel%20order%3Alatest](https://community.letsencrypt.org/search?q=namecheap%20cpanel%20order%3Alatest)

which may have useful suggestions for you.

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 5:19am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/3 "2019-08-06T05:19:03Z")

</div>

Yeah, support didn’t seem to friendly to the idea. Is it possible nonetheless?!

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 7:03am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/4 "2019-08-06T07:03:08Z")

</div>

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)**

Host: **[Namecheap.com](http://Namecheap.com) Shared Hosting**

Root: **No**

Control: **cPanel 78.0 (build 34)**

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [August 6, 2019, 7:04am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/5 "2019-08-06T07:04:48Z")

</div>

Hi @bmf

> [@Generate Certs with CertBot](https://community.letsencrypt.org/t/generate-certs-with-certbot/99238/1):
>
> I can’t seem to find a “download” button anywhere on the CertBot website.
> 
> I’m running Windows 10.

Certbot doesn't work with Windows 10.

Start with some basics:

> **[How It Works - Let's Encrypt](https://letsencrypt.org/how-it-works/)**
>
> The objective of Let’s Encrypt and the ACME protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention. This is accomplished by running a certificate...

Then select one of the windows clients:

> **[ACME Client Implementations - Let's Encrypt](https://letsencrypt.org/docs/client-options/)**
>
> Last updated: Jul 22, 2023 | See all Documentation Let’s Encrypt uses the ACME protocol to verify that you control a given domain name and to issue you a certificate. To get a Let’s Encrypt certificate, you’ll need to choose a piece...

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [August 6, 2019, 7:06am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/6 "2019-08-06T07:06:10Z")

</div>

Direct link to Windows clients to save some scrolling: [https://letsencrypt.org/docs/client-options/#clients-windows-/-iis](https://letsencrypt.org/docs/client-options/#clients-windows-/-iis)

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 7:14am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/7 "2019-08-06T07:14:20Z")

</div>

Any idea if it is possible to generate certificates with shell access to my shared hosting account without root privileges?

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 7:15am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/8 "2019-08-06T07:15:41Z")

</div>

So installing those repos on Windows will allow me to generate certificates?

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [August 6, 2019, 7:24am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/9 "2019-08-06T07:24:26Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 7:26am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/10 "2019-08-06T07:26:33Z")

</div>

ive edited my question and added all that stuff

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [August 6, 2019, 7:31am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/11 "2019-08-06T07:31:02Z")

</div>

Ah, I see that this is a duplicate of your other thread: [Installing Cert on Namecheap.com Shared Hosting](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227).

Basically, it’s not really possible to do automatically renewing Let’s Encrypt on Namecheap shared hosting. The one way it _might be_ possible is if you have SSH access to your cPanel account. You can try use acme.sh, following along this tutorial: [https://github.com/Neilpang/acme.sh/wiki/Simple-guide-to-add-TLS-cert-to-cpanel](https://github.com/Neilpang/acme.sh/wiki/Simple-guide-to-add-TLS-cert-to-cpanel) . But it’s a bit “advanced”.

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.

For example, using ZeroSSL ([https://zerossl.com/free-ssl/#crt](https://zerossl.com/free-ssl/#crt)). If you use ZeroSSL, you can follow along one of the cPanel-related videos on this page: [https://zerossl.com/ssl-videos.html](https://zerossl.com/ssl-videos.html)

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 7:33am UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/12 "2019-08-06T07:33:10Z")

</div>

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 to get off now, but I’ll be back tomorrow.

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 8:03pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/13 "2019-08-06T20:03:13Z")

</div>

I believe I still do have access to the shell, but without root privileges! I’ll take a look at that tutorial you linked.

How exactly can I use the browser to generate or issue the certificates? The ZeroSSL stuff?

Man, I’m in a real bind right now. I’ve got 40 domains that don’t have SSL, which is obviously a major issue. I’ve got 5 options:

- Buy individual SSL certificates from Namecheap, which would basically double my cost.
- Potentially buy additional hosting accounts, which might interfere with email forwarders, having a single database, etc
- Switch providers to one that provides free SSLs, but, from my limited knowledge of hosting providers, this would detract from things like email functionality that I need
- Use 301 redirects instead of having a bunch of individual pages, which would detract from the data I’m collecting on my websites
- Try installing free SSLs manually on my current hosting account

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [August 6, 2019, 8:23pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/14 "2019-08-06T20:23:48Z")

</div>

> [@bmf](#):
>
> [lipsynched.com](http://lipsynched.com)

Perhaps check acme.sh. There is a namecheap dns support:

## 53. Use Namecheap

[https://github.com/Neilpang/acme.sh/wiki/dnsapi#53-use-namecheap](https://github.com/Neilpang/acme.sh/wiki/dnsapi#53-use-namecheap)

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 6, 2019, 8:26pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/15 "2019-08-06T20:26:27Z")

</div>

I will be testing this as soon as I have finished my other tests.

Thanks \<333

---

<div class="post-metadata">

**Author:** ![fredbad](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@fredbad](https://community.letsencrypt.org/u/fredbad)\
**Post date:** [August 9, 2019, 1:45pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/16 "2019-08-09T13:45:13Z")

</div>

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](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.

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 9, 2019, 6:44pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/17 "2019-08-09T18:44:54Z")

</div>

Ok, glad to know you can do it for free.

Sucks that I’ve already redirected everything and recoded my website to adjust for it. I guess I’ll switch back once I’m done doing everything else I need to do.

They really should create an option whereby you can choose longer terms like a year or something.

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [August 9, 2019, 6:54pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/18 "2019-08-09T18:54:48Z")

</div>

> [@fredbad](#):
>
> Namecheap don’t help as they want to sell you their Comodo certificates.

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

> <https://news.ycombinator.com/item?id=18567330>
>
> 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...

> 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.

---

<div class="post-metadata">

**Author:** ![bmf](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmf/32/33390_2.png) [@bmf](https://community.letsencrypt.org/u/bmf)\
**Post date:** [August 9, 2019, 7:06pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/19 "2019-08-09T19:06:40Z")

</div>

I think it’s simply PR because I remember way back their support agents would at least help you set-up a Let’s Encrypt SSL.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 8, 2019, 7:06pm UTC](https://community.letsencrypt.org/t/installing-cert-on-namecheap-com-shared-hosting/99227/20 "2019-09-08T19:06:41Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
