Rate limit has been exceeded


#1

I am getting an error:
Could not issue a Let’s Encrypt SSL/TLS certificate for s1.webprodesign.com.
The “Certificates per Registered Domain” rate limit has been exceeded for s1.webprodesign.com. Let’s Encrypt allows no more than 20 certificates to be issued per registered domain, per week.
Detail: Error creating new cert :: too many certificates already issued for exact set of domains: s1.webprodesign.com: see https://letsencrypt.org/docs/rate-limits/

But that cannot be, There has not been more than 20 for this domain this week, should not have been any, just attempts. Any ideas?

My domain is:
s1.webprodesign.com

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):
CentOS 6.10

I can login to a root shell on my machine (yes or no, or I don’t know):
Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
Plesk Onyx Version 17.8.11 Update #15


#2

After looking at this page https://crt.sh/?q=webprodesign.com I am more confused. I see the lets encrypt certs, but then there are a multitude of other certs with domains i have never heard of, except for my domain being listed at the bottom. Where do these come from? Is this why the limit is being reached?


#3

Hi @ohiowebpro

https://crt.sh/ is very slow, also Google - https://transparencyreport.google.com/https/certificates

Quick is

https://certspotter.com/api/v0/certs?domain=webprodesign.com

There are 5 certificates with CN=s1.webprodesign.com created today. Where are these certificates?

This hits the limit.


#4

I attempted to generate certs for this today, but it said the limit was reached every time. None were created today that I know of.


#5

There are 5 created. Which client do you use? There may be cronjobs or something else. “Somebody” has created these certificates. And there is access to your webserver required (if http-01 challenge is used).


#6

I am using Plesk. Under that s1.webprodesign.com there was only one shown. Must be a bug with the lets encrypt extension for Plesk.


#7

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