starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-11 22:30:44 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

After upgrade to v2, I cannot sign certs anymore. #526

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

Originally created by @jmgurney on GitHub (Apr 17, 2021).

I just recently upgrade to ACMEv2, and I'm now getting this error message when attempting to sign existing certs that worked under v1:

 + Valid till May 28 11:15:46 2021 GMT (Longer than 30 days). Ignoring because renew was forced!
 + Signing domains...
ERROR: Certificate authority doesn't allow certificate signing

I attempted to switch back to v1 to ensure that I'd have working certs, but now I get:

 + Generating signing request...
 + Requesting authorization for xxxx.yyyy...
EXPECTED value GOT EOF

This is w/ dehydrated 0.7.0.

Originally created by @jmgurney on GitHub (Apr 17, 2021). I just recently upgrade to ACMEv2, and I'm now getting this error message when attempting to sign existing certs that worked under v1: ``` + Valid till May 28 11:15:46 2021 GMT (Longer than 30 days). Ignoring because renew was forced! + Signing domains... ERROR: Certificate authority doesn't allow certificate signing ``` I attempted to switch back to v1 to ensure that I'd have working certs, but now I get: ``` + Generating signing request... + Requesting authorization for xxxx.yyyy... EXPECTED value GOT EOF ``` This is w/ dehydrated 0.7.0.
adam closed this issue 2025-12-29 01:26:48 +01:00
adam commented 2025-12-29 01:26:49 +01:00
Author
Owner
Copy Link

@lukas2511 commented on GitHub (Apr 18, 2021):

I'm really not sure what you are doing. You give no information about your configuration and expect your issues to be magically solved?

@lukas2511 commented on GitHub (Apr 18, 2021): I'm really not sure what you are doing. You give no information about your configuration and expect your issues to be magically solved?
adam commented 2025-12-29 01:26:50 +01:00
Author
Owner
Copy Link

@jmgurney commented on GitHub (Apr 19, 2021):

Can you please fix up the documentation/error messages wrt to switching to v2? It turns out that I have an old/original config file that has API=1 set in it and w/o any documentation or helpful error messages, I wasted hours of my time trying to figure it out.

https://twitter.com/encthenet/status/1383944449508601858?s=20

@jmgurney commented on GitHub (Apr 19, 2021): Can you please fix up the documentation/error messages wrt to switching to v2? It turns out that I have an old/original config file that has `API=1` set in it and w/o any documentation or helpful error messages, I wasted hours of my time trying to figure it out. https://twitter.com/encthenet/status/1383944449508601858?s=20
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 Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#526
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?