Request: Insert affected domain in error message for unsuccessful API call #492

New Issue

adam · 2025-12-29T01:26:08+01:00

adam commented

2025-12-29 01:26:08 +01:00

Originally created by @movd on GitHub (Aug 20, 2020).

It would be useful if the affected FQDN would also be printed if an error message was issued due to an unsuccessful API call "ERROR: An error occurred while sending...".

https://github.com/dehydrated-io/dehydrated/blob/master/dehydrated#L718

Originally created by @movd on GitHub (Aug 20, 2020). It would be useful if the affected FQDN would also be printed if an error message was issued due to an unsuccessful API call "ERROR: An error occurred while sending...". https://github.com/dehydrated-io/dehydrated/blob/master/dehydrated#L718

adam closed this issue

2025-12-29 01:26:08 +01:00

adam commented

2025-12-29 01:26:09 +01:00

@danimo commented on GitHub (Sep 18, 2020):

Do you have a case where it fails for one domain and not for another? Currently dehydrated always communicates with the same CA for all domains. It should always fail and if not, it should be due to an unreliable network, not due the domain.

@danimo commented on GitHub (Sep 18, 2020): Do you have a case where it fails for one domain and not for another? Currently dehydrated always communicates with the same CA for all domains. It should always fail and if not, it should be due to an unreliable network, not due the domain.

adam commented

2025-12-29 01:26:10 +01:00

@movd commented on GitHub (Nov 5, 2020):

Hi, thanks for getting back to me. It took a while for the problem to reappear in production. Last night dehydrated took care of renewing 156 certificates with 398 challenge responses (often multiple SANs). The whole process took around one hour (which is fine by me).

From this quite big batch, there was one error:

  + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/chall-v3/8365901279/LW-JSQ (Status 500)

Details:
HTTP/1.1 100 Continue

HTTP/1.1 500 Internal Server Error
Server: nginx
Date: Wed, 04 Nov 2020 21:55:13 GMT
Content-Type: application/problem+json
Content-Length: 174
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 00036cdHAqT4YhEVvs1JabTxSQjc3cKR_XVw5VH9SbTzAVY

{
  "type": "urn:ietf:params:acme:error:serverInternal",
  "detail": "Error retrieving account \"https://acme-v02.api.letsencrypt.org/acme/acct/21979153\"",
  "status": 500
}

This is not a pressing issue, but it would be nice to know where this problem appeared. Also, we should create smaller renewal batches...

@movd commented on GitHub (Nov 5, 2020): Hi, thanks for getting back to me. It took a while for the problem to reappear in production. Last night dehydrated took care of renewing 156 certificates with 398 challenge responses (often multiple SANs). The whole process took around one hour (which is fine by me). From this quite big batch, there was one error: ```sh + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/chall-v3/8365901279/LW-JSQ (Status 500) Details: HTTP/1.1 100 Continue HTTP/1.1 500 Internal Server Error Server: nginx Date: Wed, 04 Nov 2020 21:55:13 GMT Content-Type: application/problem+json Content-Length: 174 Connection: keep-alive Cache-Control: public, max-age=0, no-cache Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index" Replay-Nonce: 00036cdHAqT4YhEVvs1JabTxSQjc3cKR_XVw5VH9SbTzAVY { "type": "urn:ietf:params:acme:error:serverInternal", "detail": "Error retrieving account \"https://acme-v02.api.letsencrypt.org/acme/acct/21979153\"", "status": 500 } ``` This is not a pressing issue, but it would be nice to know where this problem appeared. _Also, we should create smaller renewal batches..._

adam commented

2025-12-29 01:26:10 +01:00

@lukas2511 commented on GitHub (Dec 10, 2020):

I'm not really seeing what's missing here? Just read up 3 lines of your logfile where it states "Responding to challenge for $fqdn authorization..." just before the error occurs?

@lukas2511 commented on GitHub (Dec 10, 2020): I'm not really seeing what's missing here? Just read up 3 lines of your logfile where it states "Responding to challenge for $fqdn authorization..." just before the error occurs?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#492