Today I had this message:
"Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours:"
I tried to renew the certificate but that did not work. After that I deleted the certificate and ask a new one. Now I have to wait one week??? Is there a way to create a new one earlyer?
1 Like
Hello @fransvan and Welcome to the forum...
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:
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):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
6 Likes
Hi RIP,
Thnx for yur help.
My domain is: f103.nl
I ran this command: certbot certonly --webroot-path="/usr/share/icecast2/web" -d 'f103.nl
It produced this output: Obtaining a new certificate
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: f103.nl: see Rate Limits - Let's Encrypt
My web server is (include version): No webserver. I'm using https for icecast2
The operating system my web server runs on is (include version): Ubuntu 18.04.5 LTS (GNU/Linux 4.15.0 x86_64)
My hosting provider, if applicable, is: I'm running a VPS
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): I'm using certbot. 0.27.0
2 Likes
It seems you've tried five times: crt.sh | f103.nl
Please use one of those five certificates. You can check the certificates available in certbot with the certbot certificates command.
4 Likes
I fail to follow your logic along this set of circumstances:
Please show:
certbot certificates
sudo ls -lR /etc/letsencrypt/archive/
2 Likes
@fransvan thanks for your response... VERY MUCH!
Would you please show the output of @rg305's request, it will help us to resolve your current issue.
4 Likes
Hi Everyone, Thnx for helping me. Note: I'm visial impared so I made somtimes mistakes.
The output:
root@h2938245:~# root@h2938245:~# sudo ls -lR /etc/letsencrypt/archive/
-bash: root@h2938245:~#: opdracht niet gevonden
root@h2938245:~# /etc/letsencrypt/archive/:
-bash: /etc/letsencrypt/archive/:: Bestand of map bestaat niet
root@h2938245:~# totaal 12
-bash: totaal: opdracht niet gevonden
root@h2938245:~# drwxr-xr-x 2 root root 4096 mei 4 19:29 f103.nl
-bash: drwxr-xr-x: opdracht niet gevonden
root@h2938245:~# drwxr-xr-x 2 root root 4096 aug 1 12:05 f103.nl-0001
-bash: drwxr-xr-x: opdracht niet gevonden
root@h2938245:~# drwxr-xr-x 2 root root 4096 aug 1 12:09 f103.nl-0002
-bash: drwxr-xr-x: opdracht niet gevonden
root@h2938245:~#
root@h2938245:~# /etc/letsencrypt/archive/f103.nl:
-bash: /etc/letsencrypt/archive/f103.nl:: Bestand of map bestaat niet
root@h2938245:~# totaal 16
-bash: totaal: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 1822 mei 4 19:29 cert1.pem
-rw-r--r-- 1 root root 3750 aug 1 12:09 chain1.pem
-rw-r--r-- 1 root root 5572 aug 1 12:09 fullchain1.pem
-rw-r--r-- 1 root root 1708 aug 1 12:09 privkey1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 1586 mei 4 19:29 chain1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 3408 mei 4 19:29 fullchain1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 1704 mei 4 19:29 privkey1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~#
root@h2938245:~# /etc/letsencrypt/archive/f103.nl-0001:
-bash: /etc/letsencrypt/archive/f103.nl-0001:: Bestand of map bestaat niet
root@h2938245:~# totaal 20
-bash: totaal: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 1826 aug 1 12:05 cert1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 3750 aug 1 12:05 chain1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 5576 aug 1 12:05 fullchain1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 1704 aug 1 12:05 privkey1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~#
root@h2938245:~# /etc/letsencrypt/archive/f103.nl-0002:
-bash: /etc/letsencrypt/archive/f103.nl-0002:: Bestand of map bestaat niet
root@h2938245:~# totaal 20
-bash: totaal: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 1822 aug 1 12:09 cert1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 3750 aug 1 12:09 chain1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 5572 aug 1 12:09 fullchain1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~# -rw-r--r-- 1 root root 1708 aug 1 12:09 privkey1.pem
-bash: -rw-r--r--: opdracht niet gevonden
root@h2938245:~#
Thank you!
I am seeing a lot of "command not found" and "file or directory not found" errors...
3 Likes
It says "No certs found."
1 Like
I think @fransvan by accident pasted the contents of the clipboard of the ls output into the terminal itselve.
3 Likes
oh yes I can see that is a probability.
4 Likes
What am I doing wrong?
For some reason, all your previously issued certificates (which were at least 5 as you've run into rate limits) are gone? Did you delete them all?
3 Likes
I think I did...
Well, in that case, the most easy thing to do is to wait until the rate limit has been lifted and issue your certificate again with the original command.
3 Likes
That's the only way? Now my streamserver is down...
Not the only way. But you won't be able to get a new certificate for f103.nl until 08-08, as your previous certificates which lead to the rate limit were issued on 01-08 and the rate limit is a sliding window of 7 days.
Of course you could use one of your previously issued certificates in /etc/letsencrypt/archive/f103.nl/, /etc/letsencrypt/archive/f103.nl-0001/ or /etc/letsencrypt/archive/f103.nl-0002/, but getting one of those certificates into certbot again as an "active" certificate which can be automatically renewed is not easy. Currently, certbot doesn't seem to have any record of those certificates as seen by the output of certbot certificates, so that's a problem.
There is another way which can be read on the rate limits page (Rate Limits - Let's Encrypt), maar die ga ik uit principiële bezwaren niet voorkauwen.
3 Likes
The (nonexistent) renewal configuration file controls the "existence" of a certificate from certbot's perspective.
2 Likes
I know, but it's very hard if not often impossible to recreate the renewal configuration file from scratch.
3 Likes
You'd need to start from a template. Issue the same certificate in staging environment? --server ?
2 Likes