Quick! Need someone to bypass SSL renewal error

I am creating a series of screencast videos in different languages about how to use Siteground to make WP websites. I purchased one domain and have to re-do the video several times in different languages for the diff WP language users. One of the steps is encrypting your domain. So in order to show that in different languages, I've had to re-encrypt the domain multiple times. Now it's locked me out and I am on a deadline! Is anyone available who can somehow bypass this for me? Such tough luck.

My domain is:
wpdemo2024.com

I ran this command:
tried to get an SSL certificate for the above domain

It produced this output:
it produced the following error message:

https://acme-v02.api.letsencrypt.org/acme/new-order" indicated an ACME error: 429 Too Many Requests (429 urn:ietf:params:acme:error:rateLimited (The request exceeds a rate limit) (Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: wpdemo2024.com,www.wpdemo2024.com, retry after 2024-08-11T05:51:47Z: see Duplicate Certificate Limit - Let's Encrypt))

My web server is (include version):
I don't know. I use Siteground hosting if that helps.

The operating system my web server runs on is (include version):
I don't know. I use SiteGround hosting if that helps.

My hosting provider, if applicable, is:
Siteground

I can login to a root shell on my machine (yes or no, or I don't know):
I have no clue how.

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Not sure what this means. I use WordPress. Hope that helps.

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
No idea what this question is even asking about.

Hello @softwaredemos24, welcome to the Let's Encrypt community. :slightly_smiling_face:

Nothing can be done to speed that up.

Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher.

Also see

4 Likes

The rate limit documentation page pointed to in the error message also suggests a workaround that might help some people. But I feel like people trying to train people on using Let's Encrypt would want to have a good understanding of the resources that Let's Encrypt needs to use for each certificate that it issues, even if it's for a "demo" site, and thereby why the rate limits are in place.

Another workaround is to use some other Certificate Authority, there are several to choose from which are also free and can be integrated via ACME just as easily as Let's Encrypt can. But you're going to want to look at their rate limits before just assuming that you can make as many certificates as you want with them, too. While certificates may be free to the person getting them, there are costs (not just in initial issuance, but in promising to keep status available for that certificate throughout its lifetime and in tracking data needed for audits and such), so CAs generally impose limits to help ensure their resources are being used wisely.

5 Likes

Hi Bruce5051, I appreciate your prompt reply. And thanks for welcoming me to the community. I only joined about 30 minutes ago.

I am not very knowledgeable about encryption this and that, or the inner workings of this Let's Encrypt organization. But it looks pretty hopeless. It says the main limit of certificates per registered domain is 50. I am quite sure I've come nowhere near to surpassing that #. I kept deleting the website to re-do the process in a different language (creating screencasts), so after deleting and re-opening a new site with the same domain, it should've deleted the certificate, I imagine, instead of them counting them for the deleted site.

Thanks for your time!

1 Like

Hi @softwaredemos24,

This is the important paragraph from here Rate Limits - Let's Encrypt

Renewals are treated specially: they don’t count against your Certificates per Registered Domain limit, but they are subject to a Duplicate Certificate limit of 5 per week. Exceeding the Duplicate Certificate limit is reported with the error message too many certificates already issued for exact set of domains .

3 Likes

@softwaredemos24 you might want to try what is suggested here My own certificate authority - #10 by danb35

2 Likes

I am not training people on let's encrypt. Please re-read what I wrote. I am showing people the steps for "how to use Siteground to make WP websites." The "Let's Encrypt" part is a simple part of the process, a mere press of a toggle via the Siteground tools panel before entering the WP dashboard. I had no idea that I would be locked out. It's not intuitive nor does it make sense. I deleted the website each time I finished with the language and then used the same domain while changing the UI language. No point in buying dozens of domains/hosting plans when I can use the same one and simply change the UI.

Unfortunately, I've used Let's Encrypt and there needs to be uniformity in the videos. They're each supposed to be carbon copies of each other, just a diff. UI language.

Sigh Thanks anyway! Appreciate it!

1 Like

I suggest that their community forums would be better suited to assisting you, as they are the ones who are acting as an ACME Client (Certbot being one of many) on your behalf in order to obtain a certificate for you.

3 Likes

Ah, that explains why I was able to make precisely 5 vids before getting locked out (when all I needed was 2 more). Appreciate the other link. But since these screencasts need to be carbon copies of each other, and I've already made 5 vids with the "Let's Encrypt" toggle button step, I'll just take the hit. I'll save that link for my personal websites though! Thanks Bruce!

2 Likes

@softwaredemos24

FYI - It looks like that would be nginx.

HTTP Server: nginx

$ curl -Ii http://wpdemo2024.com
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 10 Aug 2024 01:16:17 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Cache-Enabled: True
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Link: <http://wpdemo2024.com/wp-json/>; rel="https://api.w.org/"
X-Httpd: 1
Host-Header: 8441280b0c35cbc1147f8ba998a563a7
X-Proxy-Cache-Info: DT:1

HTTPS - server: nginx

$ curl -k -Ii https://wpdemo2024.com/
HTTP/2 200
server: nginx
date: Sat, 10 Aug 2024 01:16:19 GMT
content-type: text/html
content-length: 1371
last-modified: Thu, 08 Aug 2024 08:29:19 GMT
vary: Accept-Encoding
etag: "66b481df-55b"
remote-addr: redacted
x-default-vhost: 1
accept-ranges: bytes
3 Likes

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