mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
Certificate invalid? #1
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).
Once I get a certificate using the production LetsEncrypt CA, the certificate doesn't seem valid and doesn't seem complete. For example, here is one I just created:
Am I supposed to be doing something else with the final
cert.pemfile once I the script finishes to make it a valid certificate?@lukas2511 commented on GitHub (Dec 5, 2015):
This is an error message encoded in base64 m)
"{"type":"urn:acme:error:unauthorized","detail":"Error creating new cert :: Authorizations for these names not found or expired: verbler.com www.verbler.com","status":403}"
I think this has to do with issue #3, i'll fix that now.
@lukas2511 commented on GitHub (Dec 5, 2015):
Mh no actually this should work. I don't know what is going on here.
@lukas2511 commented on GitHub (Dec 5, 2015):
Should work now.
@taylorotwell commented on GitHub (Dec 5, 2015):
Ah OK, is it possible to error out if we get a base64 encoded error message? I recently ran into another one where I had hit the production limit for a domain name and got the base64 encoded error message in the "certificate" file...
@lukas2511 commented on GitHub (Dec 5, 2015):
I'm still working on error handling, so yea at some point this will be detected.
@rudis commented on GitHub (Dec 8, 2015):
Error handling should be good enough now to handle all error messages from ACME.