Error when requesting ceritficate...

[dehydrated-io]

Error when requesting ceritficate...

[taylorotwell]

Also curious how to use the staging setup for LetsEncrypt so I can issue test certificates. Changing the CA to the typical "https://acme-staging.api.letsencrypt.org/directory" I use with the official LetsEncrypt client results in 404s.

[lukas2511]

Yea this still is missing some error handling.
To use the staging environment you should set the CA to "https://acme-staging.api.letsencrypt.org", without the "/directory" at the end, it should work.

[taylorotwell]

Yeah I gave that shot when I was experimenting and that turned the 404 into a 403 Forbidden:

  + Generating private key...
  + Generating signing request...
  + Requesting challenge for verbler.com...
curl: (22) The requested URL returned error: 403 Forbidden

[lukas2511]

I'm not sure what's going on there, maybe it requires the usage of a different agreement url on registration.

[taylorotwell]

Error after latest commits with https://acme-staging.api.letsencrypt.org as CA

  + Requesting challenge for verbler.com...
  + ERROR: An error occured while sending post-request to https://acme-staging.api.letsencrypt.org/acme/new-authz (curl: (22) The requested URL returned error: 403 Forbidden)

[taylorotwell]

Is there a way for me to receive the full error response body? Would that contain anymore info?

[taylorotwell]

Modified the script a bit and got the real error:

• Error: Can't retrieve challenges ({"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403})

[taylorotwell]

Resolved by deleting my privatekey.pem and letting it regenerate.

[connaryscott]

I am stuck here here as well.

{"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}

Continually got this error until i ran it with just -c, then I got:
Then i got this:

{"type":"urn:acme:error:malformed","detail":"Provided agreement URL [https://testca.kurz.pw/terms/v1] does not match current agreement URL [https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf]","status":400}

After setting my LICENSE to that value, which was a complete guess on my part, i then got that same 403 error....

[connaryscott]

I was able to get around it by just using the -c option and removing my private key which I believe others did as well. I am moving forward now.

[sztyler]

Is there any solution to use my own private key? -Its really annoying -I have to use one of my private keys due to HPKP otherwise I cannot switch my certificate....