# Too many certificates

**URL:** <https://community.letsencrypt.org/t/too-many-certificates/193699>\
**Category:** Help\
**Created:** [March 1, 2023, 8:11pm UTC](https://community.letsencrypt.org/t/too-many-certificates/193699 "2023-03-01T20:11:56Z")\
**Posts on this page:** 15\
**Page:** 3

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 2, 2023, 10:56pm UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/41 "2023-03-02T22:56:16Z")

</div>

The one I just got this morning is installed in the webapp that has serious problem. I can not use the webapp. that's why I have to set up new webapp. Once I finish this new app, then can I get a certificate over there, new app?

---

<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:** [March 2, 2023, 11:00pm UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/42 "2023-03-02T23:00:31Z")

</div>

I still don't understand. How did you get the certificate you have now? Using Certbot or something else?

Because you're likely running into the same rate limit **again** if you throw this certificate away, again.......

---

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 2, 2023, 11:15pm UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/43 "2023-03-02T23:15:24Z")

</div>

Sorry for my english... I deployed "www.easygoshuttle.com.au" with the ssl certificate but it does not work at all. it says 'disallowed ... and add 'localhost'... ' something like this message. In order to fix this problem, I did pretty much everything but failed. I have to run this website for the business. now for two days it was stopped. no website online.

I think django secret key is very sensitive and something wrong. so I have to build up new django project but this is going to be the same domain name, which is "easygoshuttle.com.au"

Once I finish the new webapp, then I need the certificate for the deployment online. That's why I ask you about this question.

---

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 2, 2023, 11:52pm UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/44 "2023-03-02T23:52:58Z")

</div>

Please allow me to use once more for the new web application. I could not fix this problem. I have no choice to build up new one again. This is going to be the last I promise. Thanks

---

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [March 3, 2023, 12:28am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/45 "2023-03-03T00:28:03Z")

</div>

are you able to ssh into old webapp?

---

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 3, 2023, 12:29am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/46 "2023-03-03T00:29:03Z")

</div>

yes I can

---

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 3, 2023, 12:30am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/47 "2023-03-03T00:30:27Z")

</div>

Sorry I can not.... I deleted old one....

---

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [March 3, 2023, 12:39am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/48 "2023-03-03T00:39:01Z")

</div>

your dns servers are failing where it's pointed to?  
com.au says your nameserver should be on [ns-cloud-b1.googledomains.com](http://ns-cloud-b1.googledomains.com) but it doesn't look like

btw duplicate certificate ratelimit is just for that exact set of domains, adding a subdomain will bypass the ratelimit.  
you should fix the DNS server first though

and backup privekey until you sure webserver will work more than a month or so

---

<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:** [March 3, 2023, 7:06am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/49 "2023-03-03T07:06:43Z")

</div>

> [@sung](#):
>
> I deployed "www.easygoshuttle.com.au" with the ssl certificate

How?

> [@sung](#):
>
> but it does not work at all. it says 'disallowed ... and add 'localhost'... ' something like this message.

Please always copy/paste as much of the _origin_ log file / error message as possible with as much context as possible. We cannnot help you with these kind of vague information I'm afraid.

> [@sung](#):
>
> I have to run this website for the business. now for two days it was stopped. no website online.

As said, you might be perfectly fine temporarily by running just HTTP without HTTPS.

> [@sung](#):
>
> I think django secret key is very sensitive and something wrong. so I have to build up new django project but this is going to be the same domain name, which is "easygoshuttle.com.au"

I have no clue what this all means. Django is unfamiliar for me and possibly with many other volunteers. You might want to include a LOT more information and context when talking about Django. For example, how does Django relate to nginx?

> [@sung](#):
>
> Please allow me to use once more for the new web application. I could not fix this problem. I have no choice to build up new one again. This is going to be the last I promise. Thanks

Rate limits are not controlled by humans. If you hit a rate limit, we cannot do anything about this.

> [@sung](#):
>
> I deleted old one....

Does Certbot still have the certificate you issued yesterday?

---

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 3, 2023, 7:09am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/50 "2023-03-03T07:09:58Z")

</div>

Osiris, Thanks for your help sincerely

But I deleted the instance, so all gone.

I did try build up new webapp, but same domain name. after done this, I tried to get the certificate again.

Now I am in the same situation... I have to wait another 2 days.

I could not leave the business for more than 4 days shut down. I did get the certificate by paying money for a year.

I really appreciate your help. Thanks a lot

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [March 3, 2023, 10:53am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/51 "2023-03-03T10:53:50Z")

</div>

> [@sung](#):
>
> I deleted the instance

You need to learn how to backup, and restore, the certificates folder before doing something like that [over and over again].

---

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 3, 2023, 10:55am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/52 "2023-03-03T10:55:39Z")

</div>

I did not know I could use the certificate again. If I knew, then I would have copied it, of course. Next time, I will do it. Thanks your help.

---

<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:** [March 3, 2023, 11:12am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/53 "2023-03-03T11:12:09Z")

</div>

> [@sung](#):
>
> But I deleted the instance, so all gone.

I'm sorry, but [I **explicitely** said **NOT** to do delete the certificate you got](https://community.letsencrypt.org/t/too-many-certificates/193699/38).

I'm very sorry, but if given advice is not followed, I cannot help you further and I will not reply in this thread again. Good luck with your endeavours.

---

<div class="post-metadata">

**Author:** ![sung](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sung/32/49604_2.png) [@sung](https://community.letsencrypt.org/u/sung)\
**Post date:** [March 3, 2023, 11:14am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/54 "2023-03-03T11:14:35Z")

</div>

Osiris I remember you. you always help me and others. I am doing this to fix the problem for 4 days now. poor me. I think it should be okay by tomorrow. Thanks anyway.

---

<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:** [April 2, 2023, 11:15am UTC](https://community.letsencrypt.org/t/too-many-certificates/193699/55 "2023-04-02T11:15:22Z")

</div>

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

[Previous page](https://community.letsencrypt.org/t/too-many-certificates/193699.md?page=2)
