Several Errors generating Certs

I am using dehydrated via le-godaddy-dns. I am a maintainer of the latter.

I had updated certs late last night and had a ton of issues getting through the scripts. My internal scripts generate 10 SAN certs covering approximately 50 domains in each.

Here are the various Lets Encrypt internal errors I saw last night in the several runs I had to execute to get it to complete:

date: Sun, 23 Aug 2020 00:34:55 GMT
url: https://acme-v02.api.letsencrypt.org/acme/authz-v3/6712194524
error: {
“type”: “urn:ietf:params:acme:error:serverInternal”,
“detail”: “Problem getting authorization”,
“status”: 500
}

date: Sun, 23 Aug 2020 00:41:52 GMT
url: https://acme-v02.api.letsencrypt.org/acme/chall-v3/6712193966/Z5SoxA
error: {
“type”: “urn:ietf:params:acme:error:serverInternal”,
“detail”: "Error retrieving account “https://acme-v02.api.letsencrypt.org/acme/acct/94634323"”,
“status”: 500
}

date: (not logged)
error: Problem connecting to server (post for https://acme-v02.api.letsencrypt.org/acme/authz-v3/6713236122; curl returned with 35)

date: Sun, 23 Aug 2020 02:41:50 GMT
url: https://acme-v02.api.letsencrypt.org/acme/authz-v3/6714410470
error: {
“type”: “urn:ietf:params:acme:error:serverInternal”,
“detail”: "Error retrieving account “https://acme-v02.api.letsencrypt.org/acme/acct/94639610"”,
“status”: 500
}

date: Sun, 23 Aug 2020 03:17:44 GMT
url: https://acme-v02.api.letsencrypt.org/acme/authz-v3/6714932808
error: {
“type”: “urn:ietf:params:acme:error:serverInternal”,
“detail”: "Error retrieving account “https://acme-v02.api.letsencrypt.org/acme/acct/94641013"”,
“status”: 500
}

1 Like

Hi,

I’m not exactly sure what this issue is, but it might not be from your end (Or maybe you are requesting it too quickly). Can you try that again?

From the Let’s Encrypt history, there isn’t any outage or maintaince yesterday.
https://letsencrypt.status.io/pages/history/55957a99e800baa4470002da

1 Like

@lestaff

multitudes of 500 errors here

1 Like

I should have mentioned in my OP that I was able to get my scripts to complete after I babysat and re-ran them for 3.5 hours last night. I had to run my scripts 18 times. Some issues of my issues were appear to be related to DNS propagation delays.

Due to the size of each certificate and the limitations of the Godaddy DNS API, it takes quite a bit of time to get through each certificate. A test run this morning shows 700 seconds per certificate! I suspect that this is a contributing factor to the various LE internal 500 errors.

2 Likes

Personally, I feel like you gave the servers some good exercise. :grin:

Another point, these errors have always occurred with my big SAN certs with LE but last night was extraordinary. I wonder if the LE servers were under a big load last night?

1 Like

Obviously they were. From you. :laughing:

I’m not exactly sure where to find that out though. One of the staff will probably chime-in eventually.

I agree, because there’s also another topic on similiar issue.

Not sure if Let’s Encrypt will ask any payments from you (a joke)

1 Like

@stevenzhu

Good eye brother. I had ignored that topic as not having enough info.