search

dehydrated-io / dehydrated

letsencrypt/acme client implemented as a shell-script – just add water
https://dehydrated.io
MIT License
5.95k stars 715 forks source link

unauthorized error #166

Closed RobertSchuster closed 8 years ago

RobertSchuster commented 8 years ago

After getting perfect san certifivates from the stating CA I've tried to switch to the letsencrypt productive area. Unfortunately I'got a: ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/new-authz (Status 403) followed by: Details: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}

Any idea is welcome - couldn't find any help at google...

regards

lukas2511 commented 8 years ago

duplicate, see #163 or #2 or #92 or ...

deleting account key solves the problem.

RobertSchuster commented 8 years ago

Hm… How to do that?

I’ve got a valid certificate for the domain by the ACMESharp scripts for windows. Therefor I’ve thougt is has something to do with this already created registration. Unfortunately same thing happens with an other never used togehter with letsencrypt domain.

So, please can you tell me which key ist to delete and how?

regards

Von: Lukas Schauer [mailto:notifications@github.com] Gesendet: Samstag, 12. März 2016 23:40 An: lukas2511/letsencrypt.sh letsencrypt.sh@noreply.github.com Cc: Robert Schuster robert.schuster@compulab-consult.de Betreff: Re: [letsencrypt.sh] unauthorized error (#166)

Closed #166https://github.com/lukas2511/letsencrypt.sh/issues/166.

— Reply to this email directly or view it on GitHubhttps://github.com/lukas2511/letsencrypt.sh/issues/166#event-587559280.

RobertSchuster commented 8 years ago

just stupid – or it was too late… I was always looking for keys at the certs directory – deleting the private_key.pem from the base-dir it worked perfectely.

Von: Lukas Schauer [mailto:notifications@github.com] Gesendet: Samstag, 12. März 2016 23:40 An: lukas2511/letsencrypt.sh letsencrypt.sh@noreply.github.com Cc: Robert Schuster robert.schuster@compulab-consult.de Betreff: Re: [letsencrypt.sh] unauthorized error (#166)

Closed #166https://github.com/lukas2511/letsencrypt.sh/issues/166.

— Reply to this email directly or view it on GitHubhttps://github.com/lukas2511/letsencrypt.sh/issues/166#event-587559280.

lukas2511 commented 8 years ago

@RobertSchuster great you got this solved. hoping this issue will be fully solved in the near future as from time to time a few people fall into this trap (it actually also happens to me, like all the time, only difference is that i already know how to fix it)...

michielbdejong commented 8 years ago

Would it be an idea to store the key in private_key-$HASH_OF_CA_URL.json instead of in private_key.json? That would resolve this confusing behavior.