# Error to renew certificate

**URL:** <https://community.letsencrypt.org/t/error-to-renew-certificate/134928>\
**Category:** Help\
**Created:** [September 30, 2020, 3:34pm UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928 "2020-09-30T15:34:49Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![mlopesbjj](https://avatars.discourse-cdn.com/v4/letter/m/94ad74/32.png) [@mlopesbjj](https://community.letsencrypt.org/u/mlopesbjj)\
**Post date:** [September 30, 2020, 3:34pm UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/1 "2020-09-30T15:34:49Z")

</div>

When I do a new request to letsencrypt, return an error:  
Error Exception thrown during renewal process: Fail to load resource from '[https://acme-v02.api.letsencrypt.org/acme/new-acct](https://acme-v02.api.letsencrypt.org/acme/new-acct)'.  
urn:ietf:params:acme:error:rateLimited: Error creating new account :: too many registrations for this IP: see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/)

So, what can I do to solved this problem?

---

<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:** [September 30, 2020, 3:43pm UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/2 "2020-09-30T15:43:53Z")

</div>

Hi @mlopesbjj

if you have that error, your setup is wrong.

> [@mlopesbjj](#):
>
> So, what can I do to solved this problem?

Create **one** account, use that to create all certificates. Not every certificate creation with a new account.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [September 30, 2020, 3:58pm UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/3 "2020-09-30T15:58:08Z")

</div>

Or you've got a terribly buggy client. Getting that rate limit is extremely RARE and would be either because the client has a bug or you're doing some very weird stuff.

---

<div class="post-metadata">

**Author:** ![mlopesbjj](https://avatars.discourse-cdn.com/v4/letter/m/94ad74/32.png) [@mlopesbjj](https://community.letsencrypt.org/u/mlopesbjj)\
**Post date:** [September 30, 2020, 4:17pm UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/4 "2020-09-30T16:17:48Z")

</div>

Hi @JuergenAuer ,

Thanks for answer.  
But I just have only one account. For this server I just need to renew the certificate.

---

<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:** [September 30, 2020, 4:20pm UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/5 "2020-09-30T16:20:05Z")

</div>

> [@mlopesbjj](#):
>
> But I just have only one account. For this server I just need to renew the certificate.

Curious.

Is this a shared hosting, so other customers have the same ip?

Share your setup:

* * *

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

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

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [September 30, 2020, 10:17pm UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/6 "2020-09-30T22:17:31Z")

</div>

> [@mlopesbjj](#):
>
> urn:ietf:params:acme:error:rateLimited: Error creating new account :: too many registrations for this IP

> [@mlopesbjj](#):
>
> But I just have only one account.

> [@JuergenAuer](#):
>
> Is this a shared hosting, so other customers have the same ip?

🌟 **That** is an amazing deduction, @JuergenAuer. I gotta give you props for this one. A ❤ just isn't good enough.

---

<div class="post-metadata">

**Author:** ![mlopesbjj](https://avatars.discourse-cdn.com/v4/letter/m/94ad74/32.png) [@mlopesbjj](https://community.letsencrypt.org/u/mlopesbjj)\
**Post date:** [October 1, 2020, 7:52am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/7 "2020-10-01T07:52:38Z")

</div>

[quote="JuergenAuer, post:5, topic:134928"]  
My domain is:  
[demosense.esqogito.com](http://demosense.esqogito.com)

I ran this command:  
var acme = new AcmeContext(letsEncryptUri);  
var account = await acme.NewAccount("[SenseProxyCRT@esqogito.com](mailto:SenseProxyCRT@esqogito.com)", true);

It produced this output:  
 ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/c/1/c135fa6f73e90b3cc2be5dd68d99d5b6056dbe1b.png)

My web server is (include version):  
IIS - 10.0.14393.0

The operating system my web server runs on is (include version):  
Windows Server 2016 version 1607

My hosting provider, if applicable, is:  
Amazon

I can login to a root shell on my machine (yes or no, or I don't know):  
yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):  
no, I 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):  
no

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [October 1, 2020, 7:56am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/8 "2020-10-01T07:56:59Z")

</div>

Hello Marcio 🙂

You've hit the Duplicate Certificate limit.

> Exceeding the **Duplicate Certificate** limit of 5 per week is reported with the error message `too many certificates already issued for exact set of domains`.

> **[Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)**
>
> Let’s Encrypt provides rate limits to ensure fair usage by as many people as possible. We believe these rate limits are high enough to work for most people by default. We’ve also designed them so renewing a certificate almost never hits a...

---

<div class="post-metadata">

**Author:** ![mlopesbjj](https://avatars.discourse-cdn.com/v4/letter/m/94ad74/32.png) [@mlopesbjj](https://community.letsencrypt.org/u/mlopesbjj)\
**Post date:** [October 1, 2020, 8:03am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/9 "2020-10-01T08:03:36Z")

</div>

Hello @griffin

Thanks for answer.  
Now, I need to wait the next week to do a new request?

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [October 1, 2020, 8:19am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/10 "2020-10-01T08:19:56Z")

</div>

> [@mlopesbjj](#):
>
> Now, I need to wait the next week to do a new request?

In looking up your history on crt.sh, it looks like you should be able to generate another certificate for [demosense.esqogito.com](http://demosense.esqogito.com) sometime tomorrow. The real rate-limit is 5 duplicate certificates in a rolling 7-day period.

Why are you generating so many identical certificates?  
Did you lose all of their private keys?

> **[crt.sh | demosense.esqogito.com](https://crt.sh/?q=demosense.esqogito.com)**
>
> Free CT Log Certificate Search Tool from Sectigo (formerly Comodo CA)

> [@mlopesbjj](#):
>
> var account = await acme. **NewAccount** ("[SenseProxyCRT@esqogito.com](mailto:SenseProxyCRT@esqogito.com)", true);

I'm pretty sure you want to avoid creating a new account. Repeatedly doing so will just cause you to hit a different rate-limit.

> You can create a maximum of 10 Accounts per IP Address per 3 hours. Exceeding this limit is reported with the error message `too many registrations for this IP`.

> **[Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)**
>
> Let’s Encrypt provides rate limits to ensure fair usage by as many people as possible. We believe these rate limits are high enough to work for most people by default. We’ve also designed them so renewing a certificate almost never hits a...

---

<div class="post-metadata">

**Author:** ![mlopesbjj](https://avatars.discourse-cdn.com/v4/letter/m/94ad74/32.png) [@mlopesbjj](https://community.letsencrypt.org/u/mlopesbjj)\
**Post date:** [October 1, 2020, 8:36am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/11 "2020-10-01T08:36:12Z")

</div>

@griffin

I'm working on a software that takes the certificate automatically, I must have made a mistake in the logic of the program and ended up generating this problem, but it has already been corrected and now I must wait for tomorrow or the next week to put it into production. I did the tests in the Let's encrypt test environment and everything is fine now. Thanks for your help.

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [October 1, 2020, 8:39am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/12 "2020-10-01T08:39:09Z")

</div>

You read my mind. 🙂  
Glad you got it fixed.

---

<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:** [October 1, 2020, 8:39am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/13 "2020-10-01T08:39:32Z")

</div>

> [@mlopesbjj](#):
>
> I ran this command:  
> var acme = new AcmeContext(letsEncryptUri);  
> var account = await acme.NewAccount("[SenseProxyCRT@esqogito.com](mailto:SenseProxyCRT@esqogito.com)", true);

If you run that command again and again, the error is expected.

One account, multiple certificates.

---

<div class="post-metadata">

**Author:** ![mlopesbjj](https://avatars.discourse-cdn.com/v4/letter/m/94ad74/32.png) [@mlopesbjj](https://community.letsencrypt.org/u/mlopesbjj)\
**Post date:** [October 1, 2020, 8:43am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/14 "2020-10-01T08:43:37Z")

</div>

@JuergenAuer

I'm working on a software that takes the certificate automatically, I must have made a mistake in the logic of the program and ended up generating this problem, but it has already been corrected and now I must wait for tomorrow or the next week to put it into production. I did the tests in the Let's encrypt test environment and everything is fine now. Thanks for your help.

---

<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:** [October 1, 2020, 8:52am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/15 "2020-10-01T08:52:35Z")

</div>

> [@mlopesbjj](#):
>
> I did the tests in the Let's encrypt test environment and everything is fine now.

Yes, using the test system is a good idea.

Happy to read you have found the bug. 👍

---

<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:** [October 31, 2020, 8:52am UTC](https://community.letsencrypt.org/t/error-to-renew-certificate/134928/16 "2020-10-31T08:52:36Z")

</div>

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