# Unable to generate cert on Staging... Rate limit?

**URL:** <https://community.letsencrypt.org/t/unable-to-generate-cert-on-staging-rate-limit/82343>\
**Category:** Help\
**Created:** [January 12, 2019, 11:57pm UTC](https://community.letsencrypt.org/t/unable-to-generate-cert-on-staging-rate-limit/82343 "2019-01-12T23:57:15Z")\
**Posts on this page:** 4\
**Page:** 2

<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:** [January 14, 2019, 2:17pm UTC](https://community.letsencrypt.org/t/unable-to-generate-cert-on-staging-rate-limit/82343/21 "2019-01-14T14:17:31Z")

</div>

> [@Skehardscooby](#):
>
> Well I’ve asked the question in the pfsense forums and waiting on a response. Seems others aren’t having issues though so my head is wrecked.

I hope those folks are able to figure out the problem. Best of luck!

> [@Skehardscooby](#):
>
> Will wait until 16th and try staging again.

The change @JuergenAuer linked to won't change your situation, it's completely unrelated. Unfortunately if your Pfsesne client is not working today I don't have strong reason to believe it will start working on the 16th.

---

<div class="post-metadata">

**Author:** ![Skehardscooby](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@Skehardscooby](https://community.letsencrypt.org/u/Skehardscooby)\
**Post date:** [January 14, 2019, 2:22pm UTC](https://community.letsencrypt.org/t/unable-to-generate-cert-on-staging-rate-limit/82343/22 "2019-01-14T14:22:03Z")

</div>

Annoyingly it was working and nothing has really changed. I just rebuilt the VM and restored the config file. Just lacking the acme settings was all.

Shouldn’t really cause any issue!

There is support for another CA but I’d rather not move because of this issue. I’d rather fix it.

Kinda like buying a new car once the tank is empty!

Just fix it

---

<div class="post-metadata">

**Author:** ![Skehardscooby](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@Skehardscooby](https://community.letsencrypt.org/u/Skehardscooby)\
**Post date:** [January 14, 2019, 8:29pm UTC](https://community.letsencrypt.org/t/unable-to-generate-cert-on-staging-rate-limit/82343/23 "2019-01-14T20:29:21Z")

</div>

SORTED!!

believe it or not, it was capitalisation in the cert that caused it to fail.

If anybody else has issues with certs failing, try going lowercase!

Makes no sense but it works

Thanks to jimp in the netgate forums for suggesting it,  
dispite suggesting it would make no difference!

---

<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:** [February 13, 2019, 8:29pm UTC](https://community.letsencrypt.org/t/unable-to-generate-cert-on-staging-rate-limit/82343/24 "2019-02-13T20:29:31Z")

</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/unable-to-generate-cert-on-staging-rate-limit/82343.md?page=1)
