Responding to challenge fails with "Provided key authorization was incorrect" #141

Closed
opened 2025-12-29 00:25:43 +01:00 by adam · 3 comments
Owner

Originally created by @virgoparna on GitHub (Sep 6, 2016).

I'm trying to use letsencrypt.sh to generate certificates, but I'm getting an error always.
I initially used Debian packaged version, but I then also tried the version from git.
Error is:

ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/challenge/CENSORED/CENCORED (Status 400)
Details:
{
"type": "urn:acme:error:malformed",
"detail": "Unable to update challenge :: Provided key authorization was incorrect",
"status": 400
}

Originally created by @virgoparna on GitHub (Sep 6, 2016). I'm trying to use letsencrypt.sh to generate certificates, but I'm getting an error always. I initially used Debian packaged version, but I then also tried the version from git. Error is: ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/challenge/CENSORED/CENCORED (Status 400) Details: { "type": "urn:acme:error:malformed", "detail": "Unable to update challenge :: Provided key authorization was incorrect", "status": 400 }
adam closed this issue 2025-12-29 00:25:43 +01:00
Author
Owner

@virgoparna commented on GitHub (Sep 6, 2016):

And Apache logs show no attempt to access ".well-known/acme-challenge"

@virgoparna commented on GitHub (Sep 6, 2016): And Apache logs show no attempt to access ".well-known/acme-challenge"
Author
Owner

@virgoparna commented on GitHub (Sep 13, 2016):

Since I got it working with official cerbot client I will not be able to do additional verification. Just for information.

@virgoparna commented on GitHub (Sep 13, 2016): Since I got it working with official cerbot client I will not be able to do additional verification. Just for information.
Author
Owner

@lukas2511 commented on GitHub (Jan 29, 2017):

Not sure what was causing this, closing this ticket since it seemed to be a one-off issue.

@lukas2511 commented on GitHub (Jan 29, 2017): Not sure what was causing this, closing this ticket since it seemed to be a one-off issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#141