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:~ #
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.
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 @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:~ #
@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):
Sorry for being silly. I looked into code and deleted private_key.pem created for stage CA. Now it works.
@lukas2511 commented on GitHub (Feb 22, 2016):
@abishai yea this is a known issue, see #92