Broken ACME account

twhiting9275

twhiting9275

Verified User
Joined
Apr 10, 2004
Messages
74
Location
Cedar Falls, IA
Failed to issue a TLS certificate for blahblahblah DNS names.
--- Command output
2026-08-21T04:36:39.069442383-05:00 INFO Trying to resolve the account by key
2026-08-21T04:36:39.214970767-05:00 WARN retry: acme: error: 400 :: urn:ietf:params:acme:error:accountDoesNotExist :: No account exists with the provided key
2026-08-21T04:36:39.215409260-05:00 ERROR Error error="registration: resolve account by key: unable to communicate with the API server: error: Post \"https://acme-v02.api.letsencrypt.org/acme/new-acct\": POST https://acme-v02.api.letsencrypt.org/acme/new-acct giving up after 1 attempt(s): acme: error: 400 :: urn:ietf:params:acme:error:accountDoesNotExist :: No account exists with the provided key"
---
Click to expand...

Adding to this, the *.domain default is broken. Go figure

So, you take a working system and break it. Customers cannot renew certificates, because, well, hey, "we decided to play with things"

Come on... Get it together
 
Last edited:
This problem has nothing to do with wildcard certificates. And also not related to DA.

This is a lego error, you can get it it if you mess up with lego ACME account credentials directory. It is /usr/local/directadmin/data/lego for lego v5 or /usr/local/directadmin/data/.lego for lego v4. You can fix it by removing the invalid ACME accounts from the lego data directory.

:)
 
fln said:
This problem has nothing to do with wildcard certificates. And also not related to DA.

This is a lego error, you can get it it if you mess up with lego ACME account credentials directory. It is /usr/local/directadmin/data/lego for lego v5 or /usr/local/directadmin/data/.lego for lego v4. You can fix it by removing the invalid ACME accounts from the lego data directory.

:)
Click to expand...
LOL

When everything works fine before an update, but everything fails, afterwards..... It's the update

Try to dismiss it all you want, but your software caused issues with an update
 
If you think the problem is not caused by your actions and you have a valid license, then please open a support ticket.

I can only say, that this happens when you tamper with ACME accounts. Thinking about external factors that could cause it - maybe it has something to do with Let's Encrypt deleting old or inactive ACME accounts.
 
You must log in or register to reply here.
Back
Top