# No Modulus error on SSL setup

**URL:** <https://forums.losant.com/t/no-modulus-error-on-ssl-setup/5233>\
**Category:** Help\
**Tags:** ssl\
**Created:** [August 25, 2023, 5:24pm UTC](https://forums.losant.com/t/no-modulus-error-on-ssl-setup/5233 "2023-08-25T17:24:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Murdy](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Michael\_Murdy](https://forums.losant.com/u/Michael_Murdy)\
**Post date:** [August 25, 2023, 5:24pm UTC](https://forums.losant.com/t/no-modulus-error-on-ssl-setup/5233/1 "2023-08-25T17:24:46Z")

</div>

Hi Losant team!

I am trying to add SSL to a domain setup on my application. I followed the steps for using Let’s Encrypt. I have verified the certificate match at [sslshopper](https://www.sslshopper.com/certificate-key-matcher.html) (from a prior forum post). I keep getting a “no modulus” error on attempting to save.

I have tried this for 2 domains. One hosted with GoDaddy and one with NameCheap. I tried the NameCheap domain after reviewing some challenges with Let’s Encrypt and GoDaddy. Both produce the same error however.

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [August 25, 2023, 5:40pm UTC](https://forums.losant.com/t/no-modulus-error-on-ssl-setup/5233/2 "2023-08-25T17:40:01Z")

</div>

Could this be the issue?

> **[How to get the private key modulus](https://community.letsencrypt.org/t/how-to-get-the-private-key-modulus/191078)**
>
> I'm having trouble to upload a new certificate to a hosting provider as it gets rejected as according to them the modulus of the cert and private key don't match. I created this certificate with certbot 2.1.0 on ubuntu 20.4 (WSL). I'm trying to...

If so I will make a ticket to update the Let’s Encrypt guide with this new information.

---

<div class="post-metadata">

**Author:** ![Michael\_Murdy](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Michael\_Murdy](https://forums.losant.com/u/Michael_Murdy)\
**Post date:** [August 25, 2023, 6:11pm UTC](https://forums.losant.com/t/no-modulus-error-on-ssl-setup/5233/3 "2023-08-25T18:11:53Z")

</div>

Thank you Dylan! Yes - it was certainly related. Re-running the command in the Let’s Encrypt guide with `--key-type rsa` added, provided an opportunity to update the cert. The updated private key was then available in the noted directory.

I confirmed the Let’s Encrypt SSL works on both hosting providers (NameCheap and GoDaddy) with this update.

The new command should read:

```auto
docker run -it --rm --name certbot \
  -v "$PWD/my-ssl-certificates:/etc/letsencrypt" \
  -v "$PWD/my-ssl-certificates:/var/lib/letsencrypt" \
  certbot/certbot certonly --manual --preferred-challenges dns --key-type rsa

```

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [August 25, 2023, 6:21pm UTC](https://forums.losant.com/t/no-modulus-error-on-ssl-setup/5233/4 "2023-08-25T18:21:30Z")

</div>

Thanks for the details! I’m filing a ticket now to get that updated in our next documentation update.
