# Letsdebug Problem **URL:** \ **Category:** Help\ **Created:** [December 11, 2019, 1:05pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402 "2019-12-11T13:05:45Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![afagund](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@afagund](https://community.letsencrypt.org/u/afagund)\ **Post date:** [December 11, 2019, 1:05pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/1 "2019-12-11T13:05:45Z")
Hi, I am actually having a problem with too many pending authorizations. I used to use the tool letsdebug to clear out those pending authorizations, however, it seems the tool is not working properly now, it says I have 0 pending authorizations and the check runs too fast, it used to take few minutes to complete. Please could someone help me out with this? #### 4. Wait for each authz to be checked … Please wait until we have found all of the pending authorizations. _Found 11991 unique authorizations in 54851 lines …_ _Checked 11991 of 11991 authorizations …_ _Found 0 pending authorizations._ Thanks! Andre 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. [https://crt.sh/?q=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: www.notore.com.br I ran this command: sudo -S certbot certonly --webroot -w /mnt/nfs/stores/static/15505/ -d www.notore.com.br,notore.com.br --email [suporte@dlojavirtual.com](mailto:suporte@dlojavirtual.com) --agree-tos --no-eff-email --manual-public-ip-logging-ok --deploy-hook /etc/letsencrypt/renewal-hooks/deploy/deploy.sh --noninteractive It produced this output: { “type”: “urn:acme:error:rateLimited”, “detail”: “Error creating new authz :: too many currently pending authorizations: see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/)”, “status”: 429 } My web server is (include version): Apache/2.4.6 The operating system my web server runs on is (include version): Centos 7 My hosting provider, if applicable, is: None 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.25.1 ---
**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:** [December 11, 2019, 2:15pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/2 "2019-12-11T14:15:48Z")
Hi @afagund > [@afagund](#): > > The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): > certbot 0.25.1 first step: Update your certbot, that's too old. There are too much changes. Second step: If you have pending authorizations, you start new orders instead of finishing existing orders -\> that's wrong. But with such an old Certbot, that may be the result. You can create a new account. But that doesn't help if you don't fix the main problem -\> update your certbot. ---
**Author:** ![afagund](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@afagund](https://community.letsencrypt.org/u/afagund)\ **Post date:** [December 11, 2019, 3:07pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/3 "2019-12-11T15:07:04Z")
Sir, I understand your concern regarding my certbot version, however, the problem is that I have more than 5000 domains under this account. Actually, the pending authorizations are coming from the renew process, where there are domains from customers who left from our platform. I know this is something I have to fix. For now, I just need to clear those pending authorizations, so I can put my service back online, because my process have a integration with Letsencrypt. I would appreciate if you could help me with that, maybe making the letsdebug working as usual. Thanks in advance! Andre ---
**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:** [December 11, 2019, 3:20pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/4 "2019-12-11T15:20:21Z")
> [@afagund](#): > > For now, I just need to clear those pending authorizations Looks like you don't understand your problem. If your certbot is so old, you use ACME-v1. That's deprecated, no new registrations are possible. So you have to update your client to use ACME-v2. That's > [@afagund](#): > > Actually, the pending authorizations are coming from the renew process, where there are domains from customers who left from our platform. something you have to fix. > [@afagund](#): > > I would appreciate if you could help me with that, maybe making the letsdebug working as usual. Letsdebug isn't from Letsencrypt, that's a completely different tool. And I don't think @_az will fix a problem with a certbot 0.25 and ACME-v1, that's a completely deprecated setup. Switching to ACME-v2 -\> you should have done that last year. ---
**Author:** ![afagund](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@afagund](https://community.letsencrypt.org/u/afagund)\ **Post date:** [December 11, 2019, 7:01pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/5 "2019-12-11T19:01:50Z")
Ok got it! Problem fixed upgrading certbot. Thanks a lot! Andre ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [December 11, 2019, 8:54pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/6 "2019-12-11T20:54:13Z")
I recently removed support for ACME v1 which is why the tool was unable to detect any pending authorizations. ---
**Author:** ![afagund](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@afagund](https://community.letsencrypt.org/u/afagund)\ **Post date:** [December 11, 2019, 10:24pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/7 "2019-12-11T22:24:09Z")
@_az should we remove v1 logs prior using the tool again? ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [December 11, 2019, 10:50pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/8 "2019-12-11T22:50:13Z")
If you want. It doesn’t really matter, besides the speedup of scanning a significantly smaller number of authorizations. For your ACME v1 needs, my [old project](https://github.com/alexzorin/clear-authz) might still work. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [January 10, 2020, 10:50pm UTC](https://community.letsencrypt.org/t/letsdebug-problem/108402/9 "2020-01-10T22:50:14Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.