mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
Error when requesting ceritficate... #2
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @taylorotwell on GitHub (Dec 5, 2015).
When requesting a certificate for a domain... I get through all steps successfully, even challenges; however, I get a curl error when requesting the actual certificate:
@taylorotwell commented on GitHub (Dec 5, 2015):
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 commented on GitHub (Dec 5, 2015):
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 commented on GitHub (Dec 5, 2015):
Yeah I gave that shot when I was experimenting and that turned the 404 into a 403 Forbidden:
@lukas2511 commented on GitHub (Dec 5, 2015):
I'm not sure what's going on there, maybe it requires the usage of a different agreement url on registration.
@taylorotwell commented on GitHub (Dec 5, 2015):
Error after latest commits with
https://acme-staging.api.letsencrypt.orgas CA@taylorotwell commented on GitHub (Dec 5, 2015):
Is there a way for me to receive the full error response body? Would that contain anymore info?
@taylorotwell commented on GitHub (Dec 5, 2015):
Modified the script a bit and got the real error:
@taylorotwell commented on GitHub (Dec 5, 2015):
Resolved by deleting my privatekey.pem and letting it regenerate.
@connaryscott commented on GitHub (Mar 27, 2016):
I am stuck here here as well.
Continually got this error until i ran it with just -c, then I got:
Then i got this:
After setting my LICENSE to that value, which was a complete guess on my part, i then got that same 403 error....
@connaryscott commented on GitHub (Mar 27, 2016):
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 commented on GitHub (Apr 3, 2016):
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....