Regarding rate limiting

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: patryknamyslak.pl

I ran this command: certbot -v

It produced this output: Your regular success message

My web server is (include version): Apache2 Newest version

The operating system my web server runs on is (include version): Ubuntu 24.04

My hosting provider, if applicable, is: Contabo

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): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 2.9.0

I had an issue where my main domain certificate was grouped with my subdomain certificate, I have always separated them and it always worked as it should, however now I had the subdomain displaying what is displayed on my main domain as if my web server was not working properly but whenever i tried to make my certificate for my subdomain I ran it for both the subdomain and domain and thats where my mistake was I presume, but now I am stuck at a rate limit and I need this to be up asap, from what I have read the rate limit is for 7 days. I tried revoking the certificates however the rate limit is still in place

2

A few things ...

The Rate Limit for duplicate certs is not 7 days (anymore). See: Rate Limits - Let's Encrypt

Certbot should have displayed the exact date and time by which you can try again. You could try the work-arounds in that link but otherwise the rate limit cannot be changed.

Just today I see you got 5 certs for just your apex domain; another 4 with just portal name and another 2 with your apex and portal subdomain. You really should use the Let's Encrypt Staging system when testing. Repeatedly replacing good certs usually means something else has gone wrong.

Your domain is proxied at Cloudflare. You could use one of their Origin CA certs at least temporarily. Or even permanently. See: Cloudflare origin CA · Cloudflare SSL/TLS docs

Another option is to use Certbot to get a cert from a different Certificate Authority. Or, of course wait until the 34 hours has expired (see earlier link)

This has no effect on rate limits. You already "consumed" the resources of Let's Encrypt to get the cert. You don't reverse that by revoking a cert. You just make even more work.

2 Likes