-
-
Notifications
You must be signed in to change notification settings - Fork 716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing with curl error 35 leaves invalid PEM file #901
Comments
Same problem, but with retry during authorization handling;
Update: It looks like the retry logic works for the
Same result, invalid PEM file. Curl version output;
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I suspect the error is an issue on the Let's Encrypt API side;
but dehydrated then leaves us with a PEM file that contains nothing except some script output;
This happens when using dehydrated with
--signcsr
,--alias
, and--out
to write the file to a specific directory that also contains the CSR and the private key.The retry logic mentioned in #792 works well while handling authorizations, but fails here? Hoping this will clear up once the Let's Encrypt API resolves whatever is causing this, but it's probably a good idea to not write a PEM file in this situation?
The text was updated successfully, but these errors were encountered: