starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-08-28 14:37:22 +02:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Error when requesting ceritficate... #2

New Issue
Closed
opened 2025-12-29 00:21:28 +01:00 by adam · 11 comments
adam commented 2025-12-29 00:21:28 +01:00
Owner
Copy Link
Copy Source

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:

  + Requesting certificate...
curl: (22) The requested URL returned error: 403 Forbidden
  + Done!
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: ``` + Requesting certificate... curl: (22) The requested URL returned error: 403 Forbidden + Done! ```
adam closed this issue 2025-12-29 00:21:28 +01:00
adam commented 2025-12-29 00:21:29 +01:00
Author
Owner
Copy Link
Copy Source

@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.

@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.
adam commented 2025-12-29 00:21:29 +01:00
Author
Owner
Copy Link
Copy Source

@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.

@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.
adam commented 2025-12-29 00:21:30 +01:00
Author
Owner
Copy Link
Copy Source

@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:

  + Generating private key...
  + Generating signing request...
  + Requesting challenge for verbler.com...
curl: (22) The requested URL returned error: 403 Forbidden
@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: ``` + Generating private key... + Generating signing request... + Requesting challenge for verbler.com... curl: (22) The requested URL returned error: 403 Forbidden ```
adam commented 2025-12-29 00:21:31 +01:00
Author
Owner
Copy Link
Copy Source

@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.

@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.
adam commented 2025-12-29 00:21:32 +01:00
Author
Owner
Copy Link
Copy Source

@taylorotwell commented on GitHub (Dec 5, 2015):

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 commented on GitHub (Dec 5, 2015): 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) ```
adam commented 2025-12-29 00:21:32 +01:00
Author
Owner
Copy Link
Copy Source

@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): Is there a way for me to receive the full error response body? Would that contain anymore info?
adam commented 2025-12-29 00:21:33 +01:00
Author
Owner
Copy Link
Copy Source

@taylorotwell commented on GitHub (Dec 5, 2015):

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 commented on GitHub (Dec 5, 2015): 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})
adam commented 2025-12-29 00:21:33 +01:00
Author
Owner
Copy Link
Copy Source

@taylorotwell commented on GitHub (Dec 5, 2015):

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

@taylorotwell commented on GitHub (Dec 5, 2015): Resolved by deleting my privatekey.pem and letting it regenerate.
adam commented 2025-12-29 00:21:33 +01:00
Author
Owner
Copy Link
Copy Source

@connaryscott commented on GitHub (Mar 27, 2016):

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 commented on GitHub (Mar 27, 2016): 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....
adam commented 2025-12-29 00:21:34 +01:00
Author
Owner
Copy Link
Copy Source

@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.

@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.
adam commented 2025-12-29 00:21:35 +01:00
Author
Owner
Copy Link
Copy Source

@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....

@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....
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#2