urn:ietf:params:acme:error:badPublicKey

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: grandecomunicacao.com, herus.world, photosea.eu

I ran this command: finalize order

It produced this output:

My web server is (include version): NA

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

My hosting provider, if applicable, is:

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

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

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

We do not use certbot. We use acmephp and are a service provider for many domains. During order finalization the client library reaches out to get the account before finalizing order. We get this error: { “type”: “urn:ietf:params:acme:error:badPublicKey”, “detail”: “sa.StorageAuthority.KeyBlocked timed out after 5000 ms”, “status”: 400 }

Is there something we’re doing wrong on our end? I see a fix related to the error messaging here but not sure if it’s deployed yet: https://github.com/letsencrypt/boulder/pull/4932

Also, is there anything we can do better so we don’t timeout when LE is checking the key?

We first noticed this 8/20 and it has continued

1 Like

Hi @chthomas,

I believe this error basically says “the Let’s Encrypt database was overloaded”.

I don’t think there’s anything you can do about it except try again later.

If it keeps happening for an extended period of time, reply once more with your CSR and we can look at it more closely.

1 Like