Certificate management becomes confusing when a filename, an application hostname and a certificate's subject alternative names are treated as interchangeable. Build an inventory that records the names inside each certificate, the challenge owners used to validate them and the services that consume the resulting files. This reveals where a single-domain registration is sufficient and where wildcard coverage is intentional. It also makes replacements and incident response much less dependent on memory.
This guide addresses a problem raised in a public r/selfhosted discussion. The discussion identifies the question; the runbook below is our own explanation, not a claim that the original poster used or endorsed SimpleACME. Read the source discussion for its historical context and compare it with the current client documentation linked below.

Follow the whole renewal chain
Trace a renewal as a sequence: scheduler, client configuration, DNS presentation, CA authorization, certificate storage, deployment and the final TLS listener. Write down the first failing stage. Later messages often say only that issuance failed and can conceal the specific error that explains the incident. Preserve a currently valid certificate while making a controlled repair.
A restart is not an end-to-end test. Recreate the relevant client process in its normal unattended environment, verify that persistent files remain available and inspect its actual exit status. Keep an independent expiration check on the served endpoint so a broken scheduler does not remain invisible until users complain. If several machines participate, record the handoff between them and give each operation a clear owner. That reduces the chance of one successful step hiding a failure further along.
Start with these three checks
- Record SANs rather than relying on filenames or friendly labels.
- Map every challenge owner to its specific delegated registration.
- Track application bindings separately from certificate storage paths.
Work through the checks against the running system, not only the configuration you expected to deploy. Save a short record of the observed answer, the client version and the first failing log message. Make one relevant change at a time so you can tell whether it corrected the original failure. Keep real credentials and private-key contents out of that record.

Configure Your ACME client with a stable delegation
Prepare the intended name in your SimpleACME account and copy its exact challenge CNAME. A free account can prepare one single-domain demo, but DNS updates are blocked until paid access is active. Paid single-domain and wildcard registrations follow accepted payment. Choose the required coverage deliberately; a registration or a plan label is not proof that every certificate identifier is included.
Add the CNAME at your existing authoritative DNS provider. Preserve it for later renewals, and configure the client to update the existing registration it points to. You do not need to share the normal DNS provider's API credentials with the renewal host. Your existing website and email DNS stay where they are. A CNAME is needed per distinct challenge owner, rather than one record for an unrelated collection of hostnames.
Choose a maintained client that supports the delegated workflow you intend to use. The important compatibility question is whether it can update an existing registration and wait for the resulting DNS proof. A generic provider dropdown is not evidence that this behavior is supported. Read the current integration guide, keep the client version in your runbook and separate validation from installation.
Store the registration mapping in a protected persistent location. Match the requested name to the assigned account, and make the updater stop on a rejected request rather than reporting a false success. Select an appropriate renewal schedule using the client's supported mechanism. Keep the certificate authority's account state and certificate private keys on the client side; they do not belong in a public DNS record, blog comment or support screenshot.
Test the result at all three boundaries
Begin with a staging validation using a separate test certificate configuration where the client supports it. Check the final public DNS answer before asking the CA to validate. These read-only examples use illustrative names; replace them with the exact challenge owner and hostname from your own setup:
dig +short CNAME _acme-challenge.app.example.com
dig +short TXT _acme-challenge.app.example.com
openssl s_client -connect app.example.com:443 -servername app.example.com </dev/nullThen inspect the client result to confirm that the CA actually issued a certificate. Finally, inspect the certificate served by the target application from the relevant user network. Compare its names and expiration with the issued object. Test the unattended job again after a controlled restart or container recreation. Record how you would recover if the validation host or deployment target became unavailable.
Know the service boundary before relying on it
A wildcard covers matching first-level names, not every possible hostname in a zone. Inventory the apex and deeper labels explicitly.
SimpleACME records TXT authorization changes and can send optional DNS-change notifications. That timeline is useful evidence, but it cannot confirm issuance or installation performed by your independent client. Keep a separate served-certificate expiry check and review update entitlement before the paid-through date. Yearly subscription billing is not the certificate validity period; let the ACME client renew when its authority and renewal policy require it.
Frequently asked questions
Does SimpleACME fix this entire problem automatically?
A wildcard covers matching first-level names, not every possible hostname in a zone. Inventory the apex and deeper labels explicitly. The delegated workflow removes the normal-zone API dependency from DNS presentation. The diagnosis, client configuration and application verification described above still matter. Use the three concrete checks in this guide to identify which part of the system needs repair before changing unrelated infrastructure.
What should stay unchanged after the first successful setup?
Keep the assigned challenge CNAME, the existing registration mapping and the supported client workflow persistent. The authorization TXT value changes for new validations; the delegation normally does not. If you replace a registration, migrate the corresponding mapping and DNS record together. Recheck the public answer and complete an unattended staging test before depending on the replacement.
How do I know renewal is complete?
Treat a successful TXT update, successful CA issuance and correct application deployment as separate results. Inspect client logs, validate the issued certificate and probe the endpoint using the correct hostname. A browser showing an old certificate is a reason to inspect routing, bindings and reload behavior, even when DNS presentation worked. Maintain an independent expiry alert for the service users actually reach.
References and the next step
Use the SimpleACME Your ACME client guide for supported setup details and the subscriber how-to library for the reviewed configuration and script examples. Consult the primary references below for the installed client's current options. If this matches your constraints, create an account and prepare your domain, verify the CNAME, then activate the required update access before a production validation.