No registration exists matching provided key #69

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

Originally created by @abishai on GitHub (Feb 21, 2016).

I have a problem signing certificate using live CA, stage CA works.

Details:
{"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}root@proxy:~ #

Originally created by @abishai on GitHub (Feb 21, 2016). I have a problem signing certificate using live CA, stage CA works. - Signing domains... - Generating private key... - Generating signing request... - Requesting challenge for xxxxxxxxxxxxxxxxxxx... - ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/new-authz (Status 403) Details: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}root@proxy:~ #
adam closed this issue 2025-12-29 00:24:03 +01:00
Author
Owner

@abishai commented on GitHub (Feb 21, 2016):

Also, I copied existing letsencrypt certificate from another server and tried to renew it using this client - I've got the same error.

@abishai commented on GitHub (Feb 21, 2016): Also, I copied existing letsencrypt certificate from another server and tried to renew it using this client - I've got the same error.
Author
Owner

@abishai commented on GitHub (Feb 21, 2016):

Sorry for being silly. I looked into code and deleted private_key.pem created for stage CA. Now it works.

@abishai commented on GitHub (Feb 21, 2016): Sorry for being silly. I looked into code and deleted private_key.pem created for stage CA. Now it works.
Author
Owner

@lukas2511 commented on GitHub (Feb 22, 2016):

@abishai yea this is a known issue, see #92

@lukas2511 commented on GitHub (Feb 22, 2016): @abishai yea this is a known issue, see #92
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#69