# Error creating new order **URL:** \ **Category:** Help\ **Created:** [August 1, 2021, 2:45pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933 "2021-08-01T14:45:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![fransvan](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@fransvan](https://community.letsencrypt.org/u/fransvan)\ **Post date:** [August 1, 2021, 2:45pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/1 "2021-08-01T14:45:55Z")
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? ---
**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\ **Post date:** [August 1, 2021, 5:12pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/2 "2021-08-01T17:12:23Z")
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](https://crt.sh/?q=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): > **[Getting Started - Let's Encrypt](https://letsencrypt.org/getting-started/)** > > To enable HTTPS on your website, you need to get a certificate (a type of file) from a Certificate Authority (CA). Let’s Encrypt is a CA. In order to get a certificate for your website’s domain from Let’s Encrypt, you have to... > **[Certbot - Certbot Instructions](https://certbot.eff.org/instructions)** > > Automatically enable HTTPS on your website with EFF's Certbot, deploying Let's Encrypt certificates. > **[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... ---
**Author:** ![fransvan](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@fransvan](https://community.letsencrypt.org/u/fransvan)\ **Post date:** [August 1, 2021, 7:07pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/3 "2021-08-01T19:07:19Z")
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](https://letsencrypt.org/docs/rate-limits/) 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 ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 1, 2021, 7:15pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/4 "2021-08-01T19:15:16Z")
> [@fransvan](#): > > 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? It seems you've tried _five_ times: [crt.sh | f103.nl](https://crt.sh/?q=f103.nl&deduplicate=y) Please use one of those five certificates. You can check the certificates available in certbot with the `certbot certificates` command. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [August 1, 2021, 8:13pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/5 "2021-08-01T20:13:37Z")
I fail to follow your logic along this set of circumstances: > [@fransvan](#): > > too many certificates (5) already issued > tried to renew the certificate but that did not work > I deleted the certificate and ask a new one Please show: `certbot certificates` `sudo ls -lR /etc/letsencrypt/archive/` ---
**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\ **Post date:** [August 2, 2021, 4:01am UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/6 "2021-08-02T04:01:48Z")
@fransvan thanks for your response... VERY MUCH! > [@rg305](#): > > Please show: > `certbot certificates` > `sudo ls -lR /etc/letsencrypt/archive/` Would you please show the output of @rg305's request, it will help us to resolve your current issue. ---
**Author:** ![fransvan](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@fransvan](https://community.letsencrypt.org/u/fransvan)\ **Post date:** [August 2, 2021, 7:17pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/7 "2021-08-02T19:17:14Z")
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:~# ---
**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\ **Post date:** [August 2, 2021, 7:26pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/8 "2021-08-02T19:26:25Z")
Thank you! I am seeing a lot of "command not found" and "file or directory not found" errors... > [@rg305](#): > > Please show: > `certbot certificates` ---
**Author:** ![fransvan](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@fransvan](https://community.letsencrypt.org/u/fransvan)\ **Post date:** [August 2, 2021, 7:29pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/9 "2021-08-02T19:29:38Z")
> [@rg305](#): > > certbot certificates It says "No certs found." ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 2, 2021, 7:29pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/10 "2021-08-02T19:29:45Z")
I think @fransvan by accident pasted the contents of the clipboard of the `ls` output into the terminal itselve. ---
**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\ **Post date:** [August 2, 2021, 7:38pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/11 "2021-08-02T19:38:19Z")
oh yes I can see that is a probability. ---
**Author:** ![fransvan](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@fransvan](https://community.letsencrypt.org/u/fransvan)\ **Post date:** [August 2, 2021, 7:41pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/12 "2021-08-02T19:41:21Z")
What am I doing wrong? ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 2, 2021, 7:43pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/13 "2021-08-02T19:43:07Z")
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? ---
**Author:** ![fransvan](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@fransvan](https://community.letsencrypt.org/u/fransvan)\ **Post date:** [August 2, 2021, 7:44pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/14 "2021-08-02T19:44:39Z")
I think I did... ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 2, 2021, 7:45pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/15 "2021-08-02T19:45:47Z")
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. ---
**Author:** ![fransvan](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@fransvan](https://community.letsencrypt.org/u/fransvan)\ **Post date:** [August 2, 2021, 7:47pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/16 "2021-08-02T19:47:02Z")
That's the only way? Now my streamserver is down... ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 2, 2021, 7:50pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/17 "2021-08-02T19:50:30Z")
> [@fransvan](#): > > That's the only way? 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](https://letsencrypt.org/docs/rate-limits/)), maar die ga ik uit principiële bezwaren niet voorkauwen. ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [August 2, 2021, 8:00pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/18 "2021-08-02T20:00:08Z")
> [@Osiris](#): > > 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. The (nonexistent) renewal configuration file controls the "existence" of a certificate from certbot's perspective. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [August 2, 2021, 8:01pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/19 "2021-08-02T20:01:31Z")
I know, but it's very hard if not often impossible to recreate the renewal configuration file from scratch. ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [August 2, 2021, 8:02pm UTC](https://community.letsencrypt.org/t/error-creating-new-order/156933/20 "2021-08-02T20:02:25Z")
You'd need to start from a template. Issue the same certificate in staging environment? `--server` ? [Next page](https://community.letsencrypt.org/t/error-creating-new-order/156933.md?page=2)