ACME 404 errors for existing end-to-end tests: “No such authorization” / “Certificate not found”

Help
22 
# INFO: Using main config file ./config
Processing openmindamir.ir with alternative names: *.openmindamir.ir
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 2 authorizations URLs from the CA
 + Handling authorization for openmindamir.ir
 + Handling authorization for openmindamir.ir
 + 2 pending challenge(s)
 + Deploying challenge tokens...
 - Deploying challenge for openmindamir.ir
 - Deploying challenge for openmindamir.ir
 + Responding to challenge for openmindamir.ir authorization...
 + Validation is pending...
 + Validation is pending...
 + Challenge is valid!
 + Responding to challenge for openmindamir.ir authorization...
 + Validation is pending...
 + Validation is pending...
 + Challenge is valid!
 + Cleaning challenge tokens...
 - Cleaning challenge for openmindamir.ir
 - Cleaning challenge for openmindamir.ir
 + Requesting certificate...
 + Checking certificate...
 + Done!
 + Creating fullchain.pem...
 - Deploying cert openmindamir.ir
 + Done!
23

Curious to hear from LE what was the issue here.

24

I'm seeing the exact same problem on GitLab (Omnibus installation) using its built-in Let’s Encrypt integration.

gitlab-ctl reconfigure fails with:

[2026-06-03T09:27:51+00:00] FATAL: Acme::Client::Error::AccountDoesNotExist: letsencrypt_certificate[gitlab.duckburnincense.com] (letsencrypt::http_authorization line 6) had an error: Acme::Client::Error::AccountDoesNotExist: acme_certificate[production] (letsencrypt::http_authorization line 83) had an error: Acme::Client::Error::AccountDoesNotExist: Unable to validate JWS :: Account "https://acme-v02.api.letsencrypt.org/acme/acct/3398741366" not found

We've completely cleared all local LE state (account keys, challenge files), yet the error persists. The client registers a new account, then immediately gets a 404 when trying to use it – exactly matching the inconsistent server‑side behaviour you’re all reporting.

Thanks for raising this – hopefully the Let’s Encrypt team can take a look soon.

25

They already are. See:

26

Hi everybody, early this morning we started getting alerted about intermittent network issues between datacenters. We had shifted API traffic away from the affected datacenter (meaning it contains only database replicas and we can shun them until such a time when the transient network issues end). I've opened a status.io which put a banner up on the community forum. Sorry, I know this is a pain.

27

Thanks. I posted this reply ~7 hours ago, and it just got approved.

29

Got the same 404 responses multiple times.