Error: urn:ietf:params:acme:error:serverInternal :: The server experienced an internal error :: Error retrieving account

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:wpapi.greyphin.com

I ran this command: sudo certbot --apache -d wpapi.greyphin.com

It produced this output:

2020-08-01 13:54:16,423:DEBUG:acme.client:Received response:
HTTP 500
Server: nginx
Date: Sat, 01 Aug 2020 13:54:16 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: 01010wNFutX50FzfleAn7iTGRpFjLOvp2t4P9ztidbEEUiQ

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

My web server is (include version): Apache 2.4.29

The operating system my web server runs on is (include version): Ubuntu 18

My hosting provider, if applicable, is: Digital ocean

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0

Could be a temporary hickup or some kind of serious problem at Let’s Encrypts end. Could you please try again and see if it was just a hickup?

It actually was a hiccup. I had a subdomain the other day refuse to renew / recreate so I was thinking it was something more. All good now. Thanks.

1 Like