# Help needed unblocking IP

**URL:** <https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698>\
**Category:** Help\
**Created:** [June 19, 2018, 6:42am UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698 "2018-06-19T06:42:07Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![svcuser](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@svcuser](https://community.letsencrypt.org/u/svcuser)\
**Post date:** [June 19, 2018, 6:42am UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/1 "2018-06-19T06:42:07Z")

</div>

Hi all,

I’m running `cert-manager` on our Kubernetes cluster which requests for a LE cert every time a new feature branch is created.

Previously we were on `0.2.0` and I think we hit the domain limit as we have quite a number of feature branches.

Unfortunately it appears that cert-manager keeps re-requesting and it hit some kind of IP block.

Now I see the following error when we describe the issuer.

```auto
  Warning ErrVerifyACMEAccount 1m (x11 over 2m) cert-manager Failed to verify ACME account: acme: urn:ietf:params:acme:error:rateLimited: Your IP, 52.x, has been blocked due to ridiculously excessive traffic. Once this is corrected you may request this be reviewed on our forum https://community.letsencrypt.org
  Warning ErrInitIssuer 1m (x11 over 2m) cert-manager Error initializing issuer: acme: urn:ietf:params:acme:error:rateLimited: Your IP, 52.x, has been blocked due to ridiculously excessive traffic. Once this is corrected you may request this be reviewed on our forum https://community.letsencrypt.org

```

Would like to request for an unblock so that we can test the upgraded `cert-manager` which should (hopefully) reduce the limit by using wildcard certs.

Thanks!

Not very comfortable sharing the actual ip here, how can we securely send this?

---

<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:** [June 19, 2018, 7:04am UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/2 "2018-06-19T07:04:34Z")

</div>

The “ridiculously excessive traffic” rate limit isn’t about, like, getting a couple too many certificates. It’s about… ridiculously excessive traffic. Likely multiple requests per second. All the time.

Here’s the cert-manager bug:

> <https://github.com/jetstack/cert-manager/issues/407>

What did you upgrade to? 0.3.0 may behave better, but 0.2.4 doesn’t.

You can probably email or private message your IP address to one of the Let’s Encrypt staff. I hope they’ll chime in in this thread.

---

<div class="post-metadata">

**Author:** ![svcuser](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@svcuser](https://community.letsencrypt.org/u/svcuser)\
**Post date:** [June 19, 2018, 7:40am UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/3 "2018-06-19T07:40:48Z")

</div>

Yeah I suspect it was due to cert-manager attempting to retry getting certificates and because we have quite a number of branches, it repeats itself quite a bit.

Hopefully we can get unblocked soon.

---

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [June 19, 2018, 2:38pm UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/4 "2018-06-19T14:38:40Z")

</div>

> [@svcuser](#):
>
> Hopefully we can get unblocked soon.

What version of cert-manager have you upgraded to?

---

<div class="post-metadata">

**Author:** ![svcuser](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@svcuser](https://community.letsencrypt.org/u/svcuser)\
**Post date:** [June 20, 2018, 2:11am UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/5 "2018-06-20T02:11:47Z")

</div>

v0.3.0.

Is there anyone I can contact privately to send my IP?

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [June 20, 2018, 3:06am UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/6 "2018-06-20T03:06:28Z")

</div>

You could talk with @cpu

---

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [June 20, 2018, 1:40pm UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/7 "2018-06-20T13:40:53Z")

</div>

Great 👍 - You can email the affected IP addresses to `cpu` @ `letsencrypt.org` (or send a forum DM)

---

<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:** [July 20, 2018, 1:41pm UTC](https://community.letsencrypt.org/t/help-needed-unblocking-ip/64698/8 "2018-07-20T13:41:05Z")

</div>

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