Hello,
I'm having problem implementing ACME client. The challenge does not leave "Pending" and does not reach the domain's web server! I'm using the acme-staging-v02.api.letsencrypt.org url.ending!
1 Like
Welcome to the Let's Encrypt Community, Cícero 
Did you activate the challenge (by submitting a POST-as-GET to the challenge URL with an empty object as the payload)?
2 Likes
Thank you Grifo,
Yes. returning status pending. is need send all chalenges? dns1, http-01 and tls?
2 Likes
Grifo? 
2 Likes
No. Just the one you want to activate.
1 Like
Is your payload string this?
{}
then Base64-encoded?
Should result in this string:
e30
1 Like
Sorry me! the Translate of page failed!
2 Likes
Yes. all requests successfully placed! But the challenge only returns pending
1 Like
I am Brazilian, my english is very bad
1 Like
Are you polling the authorization associated with the challenge or the challenge itself?
challenge
1 Like
If you have correctly triggered a challenge, the associated authorization should transition to either "valid" or "invalid" in under a minute.
1 Like
My challenge return codehttp 200: body: "type": "http-01",
"status": "pending",
More monitor log apache is not received request
1 Like
You should be repeatedly polling the authorization about every one second after triggering the challenge. Just looking at one response from triggering the challenge is useless.
1 Like
OK! I will try to do this! How many requests should I limit?
1 Like
I cut it after 10. Be certain to delay by a second between each.
1 Like
thank you!
2 Likes
If the authorization stays pending, you didn't trigger the challenge correctly. This is obvious if you look at authorization numbers in subsequent orders and see that they are the same as in previous orders. Authorizations (and challenges) get reused if they're pending.
1 Like
OK! I will try to do this!
1 Like
Make sure to do all of your testing using the staging environment!
1 Like