# Issue with many certificates already issued **URL:** \ **Category:** Help\ **Created:** [October 10, 2019, 6:29pm UTC](https://community.letsencrypt.org/t/issue-with-many-certificates-already-issued/103826 "2019-10-10T18:29:22Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![felipeEnc](https://avatars.discourse-cdn.com/v4/letter/f/8797f3/32.png) [@felipeEnc](https://community.letsencrypt.org/u/felipeEnc)\ **Post date:** [October 10, 2019, 6:29pm UTC](https://community.letsencrypt.org/t/issue-with-many-certificates-already-issued/103826/1 "2019-10-10T18:29:22Z")
Dear Team: I’d like to ask you for your help. I have deleted my droplet in DigitalOcean many times latetly because I am debuging another issue that I have, so it seams that I have applied multiple times the certification with Let’s Encrypt. I can see here I have 7 certificates Id. [https://crt.sh/?q=www.esahora.cl](https://crt.sh/?q=www.esahora.cl) I have tried to deleted them with command “sudo certbot delete” or “sudo certbot delete --cert-name esahora.cl” but I am getting “No existing certificates found.”, because all settings that could have been have been dropped, cause I have purged my droplet. Could please let me know how could I delete certificates already created? My domain is: www.esahora.cl I ran this command:sudo certbot --apache It produced this output:There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: www.esahora.cl: see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/) My web server is (include version): Apache/2.4.29 (Ubuntu) The operating system my web server runs on is (include version): Ubuntu 18.04, Droplet My hosting provider, if applicable, is:Digital Ocean 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):certbot 0.31.0 ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [October 10, 2019, 6:43pm UTC](https://community.letsencrypt.org/t/issue-with-many-certificates-already-issued/103826/2 "2019-10-10T18:43:34Z")
Hi @felipeEnc please read the document. > [@felipeEnc](#): > > It produced this output:There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: www.esahora.cl: see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/) Then you read that revoking / deleting certificates doesn't reset the rate limit. Looks like you have to wait. Never create certificates and delete these - that's always wrong. Ah - there are some checks of your domain - [https://check-your-website.server-daten.de/?q=esahora.cl#ct-logs](https://check-your-website.server-daten.de/?q=esahora.cl#ct-logs) | Issuer | not before | not after | Domain names | LE-Duplicate | next LE | | --- | --- | --- | --- | --- | --- | | Let's Encrypt Authority X3 | 2019-10-10 | 2020-01-08 | www.esahora.cl - 1 entries | duplicate nr. 5 | next Letsencrypt certificate: 2019-10-15 18:07:07 | | Let's Encrypt Authority X3 | 2019-10-10 | 2020-01-08 | www.esahora.cl - 1 entries | duplicate nr. 4 | | | Let's Encrypt Authority X3 | 2019-10-08 | 2020-01-06 | www.esahora.cl - 1 entries | duplicate nr. 3 | | | Let's Encrypt Authority X3 | 2019-10-08 | 2020-01-06 | www.esahora.cl - 1 entries | duplicate nr. 2 | | | Let's Encrypt Authority X3 | 2019-10-08 | 2020-01-06 | www.esahora.cl - 1 entries | duplicate nr. 1 | | | Let's Encrypt Authority X3 | 2019-10-08 | 2020-01-06 | esahora.cl - 1 entries | duplicate nr. 3 | | | Let's Encrypt Authority X3 | 2019-10-08 | 2020-01-06 | esahora.cl - 1 entries | duplicate nr. 2 | | | Let's Encrypt Authority X3 | 2019-10-07 | 2020-01-05 | esahora.cl - 1 entries | duplicate nr. 1 | | | Let's Encrypt Authority X3 | 2019-09-27 | 2019-12-26 | esahora.cl - 1 entries | | | | Let's Encrypt Authority X3 | 2019-09-27 | 2019-12-26 | esahora.cl - 1 entries | | | | Let's Encrypt Authority X3 | 2019-09-25 | 2019-12-24 | esahora.cl - 1 entries | | | You can create **one** certificate with both domain names. Then store the private and the public key, so you can use the certificate 60 - 85 days. ---
**Author:** ![felipeEnc](https://avatars.discourse-cdn.com/v4/letter/f/8797f3/32.png) [@felipeEnc](https://community.letsencrypt.org/u/felipeEnc)\ **Post date:** [October 10, 2019, 6:53pm UTC](https://community.letsencrypt.org/t/issue-with-many-certificates-already-issued/103826/3 "2019-10-10T18:53:42Z")
Thanks for your reply Juergen. 1.-About this “Then store the private and the public key, so you can use the certificate 60 - 85 days.”, it means that I should have backup up both of the .pem file that were created and after creating a new Droplet I should have import them in my new Droplet, righ? 2.-Also now I have to wait until October 15 to be able to create a new certificate. Is this right? ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [November 9, 2019, 6:53pm UTC](https://community.letsencrypt.org/t/issue-with-many-certificates-already-issued/103826/4 "2019-11-09T18:53:51Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.