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

Certificate invalid? #1

New Issue
Closed
opened 2025-12-29 00:21:28 +01:00 by adam · 6 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).

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:

-----BEGIN CERTIFICATE-----
eyJ0eXBlIjoidXJuOmFjbWU6ZXJyb3I6dW5hdXRob3JpemVkIiwiZGV0YWlsIjoi
RXJyb3IgY3JlYXRpbmcgbmV3IGNlcnQgOjogQXV0aG9yaXphdGlvbnMgZm9yIHRo
ZXNlIG5hbWVzIG5vdCBmb3VuZCBvciBleHBpcmVkOiB2ZXJibGVyLmNvbSB3d3cu
dmVyYmxlci5jb20iLCJzdGF0dXMiOjQwM30=
-----END CERTIFICATE-----

Am I supposed to be doing something else with the final cert.pem file once I the script finishes to make it a valid certificate?

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: ``` -----BEGIN CERTIFICATE----- eyJ0eXBlIjoidXJuOmFjbWU6ZXJyb3I6dW5hdXRob3JpemVkIiwiZGV0YWlsIjoi RXJyb3IgY3JlYXRpbmcgbmV3IGNlcnQgOjogQXV0aG9yaXphdGlvbnMgZm9yIHRo ZXNlIG5hbWVzIG5vdCBmb3VuZCBvciBleHBpcmVkOiB2ZXJibGVyLmNvbSB3d3cu dmVyYmxlci5jb20iLCJzdGF0dXMiOjQwM30= -----END CERTIFICATE----- ``` Am I supposed to be doing something else with the final `cert.pem` file once I the script finishes to make it a valid certificate?
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

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

@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): Mh no actually this should work. I don't know what is going on here.
adam commented 2025-12-29 00:21:30 +01:00
Author
Owner
Copy Link
Copy Source

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

Should work now.

@lukas2511 commented on GitHub (Dec 5, 2015): Should work now.
adam commented 2025-12-29 00:21:30 +01:00
Author
Owner
Copy Link
Copy Source

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

@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...
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 still working on error handling, so yea at some point this will be detected.

@lukas2511 commented on GitHub (Dec 5, 2015): I'm still working on error handling, so yea at some point this will be detected.
adam commented 2025-12-29 00:21:31 +01:00
Author
Owner
Copy Link
Copy Source

@rudis commented on GitHub (Dec 8, 2015):

Error handling should be good enough now to handle all error messages from ACME.

@rudis commented on GitHub (Dec 8, 2015): Error handling should be good enough now to handle all error messages from ACME.
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#1