starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-07-21 04:21:10 +02:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

ECDSA error #50

New Issue
Closed
opened 2025-12-29 00:23:31 +01:00 by adam · 2 comments
adam commented 2025-12-29 00:23:31 +01:00
Owner
Copy Link
Copy Source

Originally created by @Remonli on GitHub (Feb 7, 2016).

Hello, ECDSA is now supported , but I got error message as below,could you pls check where
is problem ?
xxx@xxx[14:50:22]:~/ssl$./letsencrypt.sh -c -a secp384r1

WARNING !! No main config file found, using default config!

Processing sectun.com with alternative names: www.xxx.com

  • Signing domains...
  • Creating new directory /home/lisheng/ssl/certs/sectun.com ...
  • Generating private key...
  • Generating signing request...
  • Requesting challenge for xxx.com...
  • Requesting challenge for www.xxx.com...
  • Responding to challenge for xxx.com...
  • Challenge is valid!
  • Responding to challenge for xxx.sectun.com...
  • Challenge is valid!
  • Requesting certificate...

Details:
{"type":"urn:acme:error:malformed","detail":"Invalid key in certificate request :: ECDSA curve P-384 not allowed","status":400}

Originally created by @Remonli on GitHub (Feb 7, 2016). Hello, ECDSA is now supported , but I got error message as below,could you pls check where is problem ? xxx@xxx[14:50:22]:~/ssl$./letsencrypt.sh -c -a secp384r1 # WARNING !! No main config file found, using default config! # Processing sectun.com with alternative names: www.xxx.com - Signing domains... - Creating new directory /home/lisheng/ssl/certs/sectun.com ... - Generating private key... - Generating signing request... - Requesting challenge for xxx.com... - Requesting challenge for www.xxx.com... - Responding to challenge for xxx.com... - Challenge is valid! - Responding to challenge for xxx.sectun.com... - Challenge is valid! - Requesting certificate... - ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/new-cert (Status 400) Details: {"type":"urn:acme:error:malformed","detail":"Invalid key in certificate request :: ECDSA curve P-384 not allowed","status":400}
adam closed this issue 2025-12-29 00:23:31 +01:00
adam commented 2025-12-29 00:23:32 +01:00
Author
Owner
Copy Link
Copy Source

@germeier commented on GitHub (Feb 7, 2016):

I believe EC-384 is still not available on the production servers:

https://community.letsencrypt.org/t/problem-issuing-ec-384-certificate/9982

@germeier commented on GitHub (Feb 7, 2016): I believe EC-384 is still not available on the production servers: https://community.letsencrypt.org/t/problem-issuing-ec-384-certificate/9982
adam commented 2025-12-29 00:23:33 +01:00
Author
Owner
Copy Link
Copy Source

@Remonli commented on GitHub (Feb 7, 2016):

It looks they are testing now,but I'm not sure if they are ready

https://community.letsencrypt.org/t/ecdsa-testing-on-staging/8809/54

@Remonli commented on GitHub (Feb 7, 2016): It looks they are testing now,but I'm not sure if they are ready https://community.letsencrypt.org/t/ecdsa-testing-on-staging/8809/54
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#50