NAS owners often want a public browser-trusted certificate while keeping the management interface off the internet. Use a controlled public hostname and DNS validation, then deploy through the NAS version's supported certificate import or integration workflow. Check which NAS services use the certificate, because importing a replacement does not necessarily reassign every service. Protect the automation account and avoid exposing the administrative API broadly just to make deployment convenient.
This guide addresses a problem raised in a public r/synology 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.

Issuance and installation are different results
When the CA has issued a new certificate, the remaining work happens in your infrastructure. Confirm where the files or certificate-store entry were written, how the consumer receives them and which supported action makes it load the replacement. Validate the certificate and key pairing without exposing private-key material. Keep a recoverable working configuration while testing deployment changes.
Probe the service using the hostname users actually request, including SNI when a listener serves multiple names. Compare the served certificate's fingerprint and validity with the issued object. A management console, a reverse proxy and a backend application may each terminate a separate TLS connection. Check the intended boundary instead of assuming they all use one shared store. Report partial deployment explicitly when one destination updates and another does not.
Start with these three checks
- Check DSM's current supported certificate import and service assignment workflow.
- Keep management access private while publishing the challenge owner in public DNS.
- Verify the certificate presented by each relevant NAS application after replacement.
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 An external ACME client and your appliance 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.
Start with the appliance's installed version and its documented certificate integrations. Do not assume a generic DNS-provider list contains a native SimpleACME integration. Where a supported script or ACME-DNS path exists, configure the existing assigned registration. Otherwise, use a maintained external ACME client and a supported certificate import or deployment mechanism for the appliance.
Keep appliance management access limited to the network and identity that need it. Determine which service terminates TLS, which certificate format it accepts and which reload action is supported. The renewal host can handle DNS validation while a separate deployment step imports the resulting certificate and key. Record both results. If the target service still presents the old certificate, investigate its assignment and reload rather than repeatedly creating new CA orders. The precise import commands depend on the appliance release and should come from its current vendor documentation.
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
The workflow requires both an ACME client and a supported NAS deployment method. SimpleACME supplies the DNS proof, not NAS administration.
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?
The workflow requires both an ACME client and a supported NAS deployment method. SimpleACME supplies the DNS proof, not NAS administration. 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 An external ACME client and your appliance 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.