# Mooo.com rate limit

**URL:** https://community.letsencrypt.org/t/mooo-com-rate-limit/51143
**Category:** Help
**Created:** [January 23, 2018, 12:23am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143 "2018-01-23T00:23:02Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![sora1](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@sora1](https://community.letsencrypt.org/u/sora1)
#### Post date: [January 23, 2018, 12:23am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/1 "2018-01-23T00:23:02Z")

</div>

I am trying to obtain new certificate since I have migrated to a new dynamic dns domain; from [ddns.net](http://ddns.net) to [mooo.com](http://mooo.com) but I am getting a rate limit I have tried this since January 21, uptill now I still get rate limit however whenver I go to the [https://crt.sh/?q=%mooo.com](https://crt.sh/?q=%25mooo.com) I still see that others have successfully obtained new certificates ?how is this possible? I still have the [mydomain.ddns.net](http://mydomain.ddns.net) certificate can I use it to change/add domain to [mydomain.mooo.com](http://mydomain.mooo.com)?

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [January 23, 2018, 12:30am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/2 "2018-01-23T00:30:41Z")

</div>

> [@Remaining time on rate limit](https://community.letsencrypt.org/t/remaining-time-on-rate-limit/51083/5):
>
> am getting a rate limit

What is the full error message you are getting?

`mooo.com` is not on the [public suffix list](https://publicsuffix.org/list/public_suffix_list.dat), which Let's Encrypt uses to determine rate limits, so using it with Let's Encrypt may not be a good idea unless the domain owner submits it to the PSL. `ddns.net` IS on the PSL and has higher rate limits.

---

<div class="post-metadata">

### Author: ![sora1](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@sora1](https://community.letsencrypt.org/u/sora1)
#### Post date: [January 23, 2018, 1:00am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/3 "2018-01-23T01:00:05Z")

</div>

The error states that rate-limit si sxceeded for the [mooo.com](http://mooo.com) domain.  
It is owned by [freedns.afraid.org](http://freedns.afraid.org) a dynamic dns service. I am going to upload a copy of the error log later.

---

<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: [January 23, 2018, 1:30am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/4 "2018-01-23T01:30:27Z")

</div>

Hi. I've split these posts into a new thread, since they concern a different domain. 🙂

> [@sora1](#):
>
> I am trying to obtain new certificate since I have migrated to a new dynamic dns domain; from [ddns.net](http://ddns.net) to [mooo.com](http://mooo.com) but I am getting a rate limit I have tried this since January 21, uptill now I still get rate limit however whenver I go to the [crt.sh | %mooo.com](https://crt.sh/?q=%25mooo.com) I still see that others have successfully obtained new certificates ?how is this possible?

It depends.

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

Some of them are probably, by coincidence or careful timing, creating certs right when the rate limits allow it. (Like when only 19 certificates have been issued in the previous week because the 20th is 1 week and 1 second old.)

Some of them are renewals of existing certificates, which fall under the Renewal Exemption to that rate limit.

If you carefully analyze the CT records, or use a program like [lectl](https://github.com/sahsanu/lectl) to do it for you, you can find out exactly when you can try to create a new certificate, if no one beats you to it. (After that, you would have no problem renewing it.)

The domain owner should submit their domain to the Public Suffix List or apply for a [rate limit exemption](https://goo.gl/forms/plqRgFVnZbdGhE9n1) from Let's Encrypt.

If they're unwilling or unable to, you could switch to a domain that is less popular, already exempt, or already on the Public Suffix List.

---

<div class="post-metadata">

### Author: ![sora1](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@sora1](https://community.letsencrypt.org/u/sora1)
#### Post date: [January 23, 2018, 1:45am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/5 "2018-01-23T01:45:21Z")

</div>

I've already emailed the owner about adding the domain to the Public Suffix Link and now waiting for a reply. Thank You

So I tried to obtain certificate this morning still with the error:

> sudo certbot certonly --standalone -d [XXXXXX.mooo.com](http://XXXXXX.mooo.com)  
> Saving debug log to /var/log/letsencrypt/letsencrypt.log  
> Obtaining a new certificate  
> Performing the following challenges:  
> http-01 challenge for [XXXXXX.mooo.com](http://XXXXXX.mooo.com)  
> Waiting for verification...  
> Cleaning up challenges  
> Generating key (2048 bits): /etc/letsencrypt/keys/XXXXX\_key-certbot.pem  
> Creating CSR: /etc/letsencrypt/csr/XXXXX\_csr-certbot.pem  
> An unexpected error occurred:  
> There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for: [mooo.com](http://mooo.com): see [Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)  
> Please see the logfiles in /var/log/letsencrypt for more details.

---

<div class="post-metadata">

### Author: ![sora1](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@sora1](https://community.letsencrypt.org/u/sora1)
#### Post date: [January 24, 2018, 1:29am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/6 "2018-01-24T01:29:18Z")

</div>

So I tried to use lectl to determine when I can obtain a new certificate for the ‘[mooo.com](http://mooo.com)’ domain and I tried it last night and this morning the results. Last night it says I can obtain certificate at Jan 26 and now it says Jan 27? I have yet to receive a reply to the administrator of [freedns.afraid.org](http://freedns.afraid.org) to include the [mooo.com](http://mooo.com) to the PSL.

 ![SS1](https://global.discourse-cdn.com/letsencrypt/original/3X/8/6/864adb105dcc9b4380f8245e80d9ad96e4988cdb.png)

---

<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: [January 24, 2018, 1:58am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/7 "2018-01-24T01:58:31Z")

</div>

Other people keep renewing certificates, so I guess the number will keep changing. 🙁

[https://crt.sh/?q=%mooo.com](https://crt.sh/?q=%25mooo.com)

---

<div class="post-metadata">

### Author: ![sora1](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@sora1](https://community.letsencrypt.org/u/sora1)
#### Post date: [January 24, 2018, 2:02am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/8 "2018-01-24T02:02:16Z")

</div>

I thought the renewals have higher rate limits?

---

<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: [January 24, 2018, 2:03am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/9 "2018-01-24T02:03:57Z")

</div>

> [@sora1](#):
>
> I thought the renewals have higher rate limits?

Sort of. Renewals can be issued when some of the other rate limits are exceeded, but the renewals will still count against the rate limits, preventing _new_ certificates from being issued.

(Let's Encrypt is working on improving the situation, but it's complicated.)

---

<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 23, 2018, 2:04am UTC](https://community.letsencrypt.org/t/mooo-com-rate-limit/51143/10 "2018-02-23T02:04:03Z")

</div>

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