Troubleshooting Common Issues
Symptom-based fixes for the most frequent Automated Certificate Management Environment (ACME) automation problems reported by GeoCerts customers using the DigiCert ACME Client—validation failures, funding, organization validation (OV) delays, permissions, external account binding (EAB) credential loss, and unexpected new billable orders.
For log-driven diagnosis during enroll (EAB, domain control validation (DCV), installation), see Verify and Diagnose ACME Requests. For renewal timing, sandbox behavior, and CLI vs Tom’s Obvious, Minimal Language (TOML) questions, see Frequently Asked Questions. For CertCommand SSL/TLS order DCV (email, Persistent DNS TXT, HTTP file—not an ACME HTTP challenge (HTTP-01) or DNS challenge (DNS-01)), see Domain Control Validation.
Domain validation failures
Symptoms: Certificate request stays pending; DCV never completes; ACME client reports validation errors.
Common causes:
- DNS-01: TXT record missing, wrong host, or slow DNS propagation.
- HTTP-01: Port 80 blocked, wrong web root, or load balancer not routing
/.well-known/acme-challenge/to the validation host. - Wildcard certificates: DNS-01 is required; HTTP-01 will not work.
What to do:
- Confirm the validation method matches your environment.
- For HTTP-01, ensure DigiCert validation agents can reach port 80 from multiple network locations under Multi-Perspective Issuance Corroboration (MPIC) requirements.
- Re-run the request after fixing DNS or HTTP configuration.
- For OV certificates, confirm domain validation is current in CertCommand under Certificates > Domains.
- If you are still setting up ACME, use a Sandbox ACME Directory URL to debug DCV and DNS credentials without production charges or orders.
Account funding or billing issues
Symptoms: Renewal or issuance fails near expiration; orders fail in CertCommand without a clear validation error.
What to do:
- Check CertCommand for failed or unpaid orders.
- Confirm prepaid coverage or account balance supports a new issuance or renewal.
- Resolve billing issues, then allow the client to retry or trigger a manual request if needed.
Account funding or billing issues that prevent certificate issuance can block renewals as well as new requests.
OV validation not current
Symptoms: OV certificate requests hang or fail; instant issuance worked before but not on renewal.
What to do:
- Verify the organization is validated under Certificates > Organizations.
- Confirm domain validation has not expired for domains on the certificate.
- Revalidate organization or domains in CertCommand if reuse periods have lapsed.
For OV certificates, automated issuance and renewal require current organization and domain validation.
Permission and service errors
Symptoms: Permission denied when running dc-acme; service not running; configuration changes ignored.
What to do:
- Run
dc-acmewith appropriate privileges (sudoon Linux, Administrator on Windows). -
Confirm the service is running:
# Confirm DigicertAcmeClient service is running (Linux) sudo systemctl status DigicertAcmeClient# Confirm DigicertAcmeClient service is running (Windows) Get-Service -Name "DigicertAcmeClient" - Restrict but do not lock down
dc-acme.tomlso the service account cannot read EAB credentials. - After editing
dc-acme.toml, restart the service if changes are not picked up.
Unexpected new orders (instead of free reissues)
Symptoms: An intended “reissue” creates a new billable order; auto-detection did not match the prior certificate.
Common causes:
- The subject alternative name (SAN) list changed on a non-wildcard certificate (including trying to add names via forced
reissue—new--sansvalues are ignored; a different SAN set on re-enroll creates a new billable order). - Certificate was manually reissued outside ACME (breaks ACME renewal tracking).
- Explicit
action=enrollon the ACME Directory URL.
What to do:
- Review Auto-detection Rules and Subject Alternative Names (SANs).
- Avoid manual reissues in CertCommand for ACME-managed certificates when possible—use the ACME client instead.
- Use ACME Automation Actions only when you intentionally need to override detection.
EAB credentials lost or invalid
Symptoms: Authentication errors; client cannot enroll.
What to do:
- The EAB Key ID and hash-based message authentication code (HMAC) are shown once at ACME Directory URL creation. They cannot be retrieved later.
- Create a new ACME Directory URL in CertCommand and update
dc-acme.tomlor CLI flags. - Revoke the old ACME Directory URL if credentials may have been exposed.
Related topics
- Verify and Diagnose ACME Requests — Log-driven EAB, DCV, and install diagnosis
- Auto-detection Rules — Why a request became a new order
- Renewal Timing and Configuration
- Frequently Asked Questions
- Get Started — Confirm setup steps are complete
← Back to Troubleshooting & FAQs