SimpleACME
Sign inCreate account →
Certificate troubleshooting

Nginx Proxy Manager and Tailscale: keep validation separate

Nginx Proxy Manager and Tailscale: keep validation separate. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal.

Reaching a proxy over Tailscale does not make its HTTP challenge reachable by a public CA. A private overlay network and public DNS validation solve different problems. Use a public domain name you control, resolve the application privately for your users, and publish the challenge delegation in public DNS. Check Nginx Proxy Manager's supported DNS provider integrations for the installed release; an external Certbot workflow is an alternative when the required hook is unavailable.

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.

Nginx Proxy Manager and Tailscale: keep validation separate: a permanent challenge CNAME connects normal DNS to SimpleACME TXT updates while the ACME client retains issuance and private keys.
Nginx Proxy Manager and Tailscale: keep validation separate: a permanent challenge CNAME connects normal DNS to SimpleACME TXT updates while the ACME client retains issuance and private keys.

Reachability is the design decision

Separate the validation plane from the application plane. Your users may reach a service through a VPN, private DNS or an internal reverse proxy, while the certificate authority sees only the public challenge record. The application does not need a public HTTP listener solely to prove the requested DNS name. The issuing machine still needs its required outbound network connections and a reliable DNS view.

Use a publicly registrable domain you control for a public CA certificate. An invented internal suffix is a different trust problem, often better addressed by a private CA and managed trust distribution. Public certificate issuance may reveal identifiers through transparency logs, so avoid assuming that a private application implies a secret hostname. For a simple website that already has a reliable public challenge path, retaining native HTTP validation may be the smaller operational change.

Start with these three checks

  1. Keep the overlay application's private routing separate from public challenge resolution.
  2. Verify the proxy release supports the selected DNS integration before entering credentials.
  3. If importing externally renewed files, automate the supported import and reload path.

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.

Nginx Proxy Manager and Tailscale: keep validation separate: diagnostic checklist covering keep the overlay application's private routing separate from public challenge resolution, verify the proxy release supports the selected DNS integration before entering credentials, if importing externally renewed files, automate the supported import and reload path.
Nginx Proxy Manager and Tailscale: keep validation separate: diagnostic checklist covering keep the overlay application's private routing separate from public challenge resolution, verify the proxy release supports the selected DNS integration before entering credentials, if importing externally renewed files, automate the supported import and reload path.

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/null

Then 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

SimpleACME is not a Tailscale relay and does not make an unsupported Nginx Proxy Manager provider appear automatically.

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?

SimpleACME is not a Tailscale relay and does not make an unsupported Nginx Proxy Manager provider appear automatically. 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.

KEEP EXPLORING

A little more clarity.

ONE CNAME. A REPEATABLE WORKFLOW.

Your next certificate. A little less complicated.

Keep your DNS provider and your ACME client.
Prepare your domain before activating paid updates.

Create your account →Explore the integrations