-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot update challenge with status valid, only status pending #133
Comments
Hi @iftahbe, thank you for the very detailed bug report! I appreciate it :-)
Based on the Fiddler trace & Pebble output it looks like you are:
It sounds like you wanted to be polling the authorization to see when it has changed from "pending" to "valid". This should be done by sending a GET request to the authorization URL. Instead, it seems like you are POSTing the challenge over and over - each time it returns E.g. I'd expect the flow for a single identifier order to be more like:
I don't think there is a bug here. The error you are getting from Pebble is the one I would expect to be delivered to a client that behaved like yours did in the logs :-) Does that make sense? |
FWIW: Starting Pebble with |
@cpu Thanks a lot for the explanation. |
@iftahbe Great :-)
Just to clarify quickly: you can get the individual authorization's statuses as well but you should do so with a GET request and not a POST. |
Testing our ACME v2 client against Pebble.
During the challenge authorization stage, pebble completes the challenge and the authorization status is changed to "valid" (according to the Pebble console output) but in the HTTP response we still get the "pending" status.
After several retries, we get the following error:
HTTP/1.1 400 Bad Request
{
"type": "urn:ietf:params:acme:error:malformedRequest",
"detail": "Cannot update challenge with status valid, only status pending",
"status": 400
}
Output of the Pebble console:
And the network traffic capture by Fiddler:
The text was updated successfully, but these errors were encountered: