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

E-Mail from buypass informing about changes, dehydrated stopped working immediately #618

New Issue
Open
opened 2025-12-29 01:27:52 +01:00 by adam · 1 comment
adam commented 2025-12-29 01:27:52 +01:00
Owner
Copy Link

Originally created by @Sommerwiesel on GitHub (Jan 4, 2024).

Yesterday, I received an email from buypass informing about changes to their certificates and that all buypass certs will be revoked as of 01-08-2024.
They recommend renewing all the certs manually to prevent outage.

I tried doing that with dehydrated but that doesn't work anymore:

+ Responding to challenge for **** authorization...
  + ERROR: An error occurred while sending post-request to https://api.buypass.com/acme-v02/authz/*****/1 (Status 400)

Details:
HTTP/1.1 400 Bad Request
Cache-Control: no-store
Content-Language: en
Content-Length: 194
Content-Type: application/problem+json
Date: Thu, 04 Jan 2024 10:28:53 GMT
Mdc-Correlationid: *****
Replay-Nonce: *****
Vary: Accept-Encoding
X-Buypass-Internal-Error-Detail-Code: MALFORMED_BAD_REQUEST
Strict-Transport-Security: max-age=63072000

{"type":"urn:ietf:params:acme:error:malformed","detail":"Unable to process challenge, authorization is not pending","code":400,"message":"MALFORMED_BAD_REQUEST","details":"HTTP 400 Bad Request"}

EXPECTED value GOT EOF

Can you please look into this until 01-08-2024.
I use ocsp stapling with buypass chain-of-trust and I really don't want to switch to letsencrypt because that is a little bit harder to setup.

Thanks :)

Originally created by @Sommerwiesel on GitHub (Jan 4, 2024). Yesterday, I received an email from buypass informing about changes to their certificates and that all buypass certs will be revoked as of 01-08-2024. They recommend renewing all the certs manually to prevent outage. I tried doing that with dehydrated but that doesn't work anymore: ```shell + Responding to challenge for **** authorization... + ERROR: An error occurred while sending post-request to https://api.buypass.com/acme-v02/authz/*****/1 (Status 400) Details: HTTP/1.1 400 Bad Request Cache-Control: no-store Content-Language: en Content-Length: 194 Content-Type: application/problem+json Date: Thu, 04 Jan 2024 10:28:53 GMT Mdc-Correlationid: ***** Replay-Nonce: ***** Vary: Accept-Encoding X-Buypass-Internal-Error-Detail-Code: MALFORMED_BAD_REQUEST Strict-Transport-Security: max-age=63072000 {"type":"urn:ietf:params:acme:error:malformed","detail":"Unable to process challenge, authorization is not pending","code":400,"message":"MALFORMED_BAD_REQUEST","details":"HTTP 400 Bad Request"} EXPECTED value GOT EOF ``` Can you please look into this until 01-08-2024. I use ocsp stapling with buypass chain-of-trust and I really don't want to switch to letsencrypt because that is a little bit harder to setup. Thanks :)
adam commented 2025-12-29 01:27:52 +01:00
Author
Owner
Copy Link

@Sommerwiesel commented on GitHub (Jan 6, 2024):

Update
Received another mail from buypass, they somehow managed to screw up their API for the past days.

First they only give us 7 working days before they revoke all certificates, then they break their API for the first 4 days...

TLDR: Not dehydrated fault.

Anyone else encountering this problem, you need to deactivate and register a new buypass account before the API works again.

Leaving this open for people to see.

@Sommerwiesel commented on GitHub (Jan 6, 2024): **Update** Received another mail from buypass, they somehow managed to screw up their API for the past days. First they only give us 7 working days before they revoke all certificates, then they break their API for the first 4 days... TLDR: Not dehydrated fault. **Anyone else encountering this problem, you need to deactivate and register a new buypass account before the API works again.** Leaving this open for people to see.
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#618
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?