But it's not invalid, it's just stuck on LE's side ( we have an issue open there for the domain in question )
Originally created by @Cyborgscode on GitHub (May 6, 2016).
This the the json that came back from LE:
{"type":"http-01","status":"pending","uri":"https://acme-v01.api.letsencrypt.org/acme/challenge/7ftGAV2gxxWnohIAl_Aq60JWZOSNhuR_4rQH5bRpUEA/74809467","token":"bDZxoGLIuz28jHDH0Ga5nDQ-erAKfXdUW9WWKeWLSd8","keyAuthorization":"bDZxoGLIuz28jHDH0Ga5nDQ-erAKfXdUW9WWKeWLSd8.e5FZjrnwb1SZURXTovcByAXqtydN8vSfcQLBNTs0yiM"}
The script says invalid :
- Challenge is invalid! (returned: invalid)
But it's not invalid, it's just stuck on LE's side ( we have an issue open there for the domain in question )
Did you check if you are running an old version of the script? The output on errors should be similar to Challenge is invalid! (returned: invalid) (result: [...]json here[...]).
Also "returned: invalid" actually gets parsed from the json response, it's impossible for the script to just invent a status "invalid" at that point. As long as the status is "pending" it tries again and again until it's no longer "pending".
Closing this bug as it doesn't seem like an actual bug in the script.
@lukas2511 commented on GitHub (May 6, 2016):
Did you check if you are running an old version of the script? The output on errors should be similar to `Challenge is invalid! (returned: invalid) (result: [...]json here[...])`.
Also "returned: invalid" actually gets parsed from the json response, it's impossible for the script to just invent a status "invalid" at that point. As long as the status is "pending" it tries again and again until it's no longer "pending".
Closing this bug as it doesn't seem like an actual bug in the script.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Cyborgscode on GitHub (May 6, 2016).
This the the json that came back from LE:
{"type":"http-01","status":"pending","uri":"https://acme-v01.api.letsencrypt.org/acme/challenge/7ftGAV2gxxWnohIAl_Aq60JWZOSNhuR_4rQH5bRpUEA/74809467","token":"bDZxoGLIuz28jHDH0Ga5nDQ-erAKfXdUW9WWKeWLSd8","keyAuthorization":"bDZxoGLIuz28jHDH0Ga5nDQ-erAKfXdUW9WWKeWLSd8.e5FZjrnwb1SZURXTovcByAXqtydN8vSfcQLBNTs0yiM"}
The script says invalid :
But it's not invalid, it's just stuck on LE's side ( we have an issue open there for the domain in question )
@lukas2511 commented on GitHub (May 6, 2016):
Did you check if you are running an old version of the script? The output on errors should be similar to
Challenge is invalid! (returned: invalid) (result: [...]json here[...]).Also "returned: invalid" actually gets parsed from the json response, it's impossible for the script to just invent a status "invalid" at that point. As long as the status is "pending" it tries again and again until it's no longer "pending".
Closing this bug as it doesn't seem like an actual bug in the script.