# Rate limit issue

**URL:** <https://community.letsencrypt.org/t/rate-limit-issue/79846>\
**Category:** Issuance Tech\
**Created:** [December 11, 2018, 7:29pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846 "2018-12-11T19:29:09Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![grx7](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grx7/32/28109_2.png) [@grx7](https://community.letsencrypt.org/u/grx7)\
**Post date:** [December 11, 2018, 7:29pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/1 "2018-12-11T19:29:09Z")

</div>

here are certs that been issued:

[https://crt.sh/?q=ubi.im](https://crt.sh/?q=ubi.im)

I’ve been running it on multi site with many urls and didn’t know about the limit at the time. So I’ve waited a week, but still it doesn’t issue anymore. Any idea if some can be revoked and then re-issued?

---

<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:** [December 11, 2018, 7:39pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/2 "2018-12-11T19:39:50Z")

</div>

Hi @grx7

> [@grx7](#):
>
> [crt.sh | ubi.im](https://crt.sh/?q=ubi.im)

why do you want to create a new certificate again? Letsencrypt certificates are 90 days valide. So use one of these the next 60 days.

Then you can create one new certificate.

> [@grx7](#):
>
> Any idea if some can be revoked and then re-issued?

Revoking a certificate doesn't change something. Please read

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

> Revoking certificates does not reset rate limits, because the resources used to issue those certificates have already been consumed.

---

<div class="post-metadata">

**Author:** ![grx7](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grx7/32/28109_2.png) [@grx7](https://community.letsencrypt.org/u/grx7)\
**Post date:** [December 11, 2018, 8:49pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/3 "2018-12-11T20:49:07Z")

</div>

I’ve cleared  
/etc/letsencrypt/live

/etc/letsencrypt/renewal

/etc/letsencrypt/archive

while trying to re-create a new one. Are there other places on the server I can get it from? How to use the older issued ones now?

---

<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:** [December 11, 2018, 9:03pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/4 "2018-12-11T21:03:29Z")

</div>

> [@grx7](#):
>
> I’ve cleared  
> /etc/letsencrypt/live
> 
> /etc/letsencrypt/renewal
> 
> /etc/letsencrypt/archive

If you create valide certificates, then delete them ... then you have to wait one week.

---

<div class="post-metadata">

**Author:** ![grx7](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grx7/32/28109_2.png) [@grx7](https://community.letsencrypt.org/u/grx7)\
**Post date:** [December 11, 2018, 9:06pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/5 "2018-12-11T21:06:16Z")

</div>

where on my apache2 they would be located?

---

<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:** [December 11, 2018, 9:12pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/6 "2018-12-11T21:12:12Z")

</div>

> [@grx7](#):
>
> where on my apache2 they would be located?

These

> [@grx7](#):
>
> I’ve cleared  
> /etc/letsencrypt/live
> 
> /etc/letsencrypt/renewal
> 
> /etc/letsencrypt/archive

are the standard folders. If they are empty, ...

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [December 12, 2018, 4:30am UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/7 "2018-12-12T04:30:23Z")

</div>

Certbot has copies of your private keys in `/etc/letsencrypt/keys/`. If that directory hasn’t been erased, it would be possible to download the missing certificates from crt.sh or elsewhere and get going again. (Reconstructing Certbot’s full file and directory structure and the renewal settings would be more complicated.)

However, you started this thread around 6 days and 20 hours after issuing those certificates, shortly before they went out of the rate limit window. By now it’s been about 7 days and 4 hours, so you can just issue more certificates now.

---

<div class="post-metadata">

**Author:** ![grx7](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grx7/32/28109_2.png) [@grx7](https://community.letsencrypt.org/u/grx7)\
**Post date:** [December 12, 2018, 6:40pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/8 "2018-12-12T18:40:56Z")

</div>

I’ll try to run the issuance command again now

---

<div class="post-metadata">

**Author:** ![grx7](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grx7/32/28109_2.png) [@grx7](https://community.letsencrypt.org/u/grx7)\
**Post date:** [December 12, 2018, 7:15pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/9 "2018-12-12T19:15:50Z")

</div>

guys thanks for your help. I just ran it and it worked.

---

<div class="post-metadata">

**Author:** ![grx7](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grx7/32/28109_2.png) [@grx7](https://community.letsencrypt.org/u/grx7)\
**Post date:** [December 12, 2018, 7:47pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/10 "2018-12-12T19:47:36Z")

</div>

Any idea why it is showing up like this:

 ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/f/3/f348ffd4ea1fc7a78f5a7dfd56282c2305534c74.jpeg)

---

<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:** [December 12, 2018, 7:53pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/11 "2018-12-12T19:53:39Z")

</div>

> [@grx7](#):
>
> ubi.im

You have mixed content warnings.

Use FireFox or Chrome, then Ctrl + Shift + I to open the console.

There you see http links:

```nohighlight
http://ubi.im/wp-content/uploads/2018/12/tech.jpg

```

Change these to https. WordPress has options to do that.

---

<div class="post-metadata">

**Author:** ![grx7](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grx7/32/28109_2.png) [@grx7](https://community.letsencrypt.org/u/grx7)\
**Post date:** [December 12, 2018, 8:30pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/12 "2018-12-12T20:30:53Z")

</div>

thanks a lot Juergen

---

<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:** [December 12, 2018, 9:01pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/13 "2018-12-12T21:01:23Z")

</div>

Yep, now all mixed content warnings are away 😉

---

<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:** [January 11, 2019, 9:01pm UTC](https://community.letsencrypt.org/t/rate-limit-issue/79846/14 "2019-01-11T21:01:24Z")

</div>

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