# Difficulty issuing for shintajim.ir **URL:** \ **Category:** Help\ **Created:** [March 3, 2020, 6:52am UTC](https://community.letsencrypt.org/t/difficulty-issuing-for-shintajim-ir/114920 "2020-03-03T06:52:33Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![bruncsak](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruncsak/32/18414_2.png) [@bruncsak](https://community.letsencrypt.org/u/bruncsak)\ **Post date:** [March 5, 2020, 8:40pm UTC](https://community.letsencrypt.org/t/difficulty-issuing-for-shintajim-ir/114920/11 "2020-03-05T20:40:33Z")
> [@poopesh](#): > > _It produced this output:_ > Requesting new certificate order... > Processing [https://acme-v02.api.letsencrypt.org/acme/authz-v3/3146088983](https://acme-v02.api.letsencrypt.org/acme/authz-v3/3146088983)... > Processing authorization for shintajim.ir... > Waiting for domain verification... > Let's Encrypt was unable to verify the challenge. Unable to update challenge :: authorization must be pending. Exiting... I quickly looked at the source code of your ACME client, just before the error message _Let's Encrypt was unable to verify the challenge. ..._, there is the keyword `"keyAuthorization"` used in the generated jws. That keyword is not in use in the ACME v2 protocol, it is part only the ACME v1. As a consequence the ACME client must be buggy. It is important to fix the client, before going forward. (here is my client: [GitHub - bruncsak/ght-acme.sh: Get publicly trusted certificate via ACME protocol from LetsEncrypt or from BuyPass](https://github.com/bruncsak/ght-acme.sh) ) --- _[View the full topic](https://community.letsencrypt.org/t/difficulty-issuing-for-shintajim-ir/114920)._