SimpleACME
Sign inCreate account →
Certificate troubleshooting

win-acme renewals fail after port 80 is blocked

win-acme renewals fail after port 80 is blocked. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME.

Blocking port 80 can break an otherwise healthy win-acme renewal that still uses HTTP validation. An existing certificate continues working until expiry, so the failure may be hidden for weeks. Inspect the saved renewal's validation plugin rather than assuming that HTTPS traffic on port 443 proves the challenge can run. Migrate the intended renewal to an unattended DNS hook, then test under the task identity before relying on the new firewall policy.

This guide addresses a problem raised in a public r/letsencrypt 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.

win-acme renewals fail after port 80 is blocked: a permanent challenge CNAME connects normal DNS to SimpleACME TXT updates while the ACME client retains issuance and private keys.
win-acme renewals fail after port 80 is blocked: 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. Inspect the validation plugin stored in the affected win-acme renewal.
  2. Test the DNS hook with the same Windows account used by the scheduled task.
  3. Check IIS binding deployment after successful certificate issuance.

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.

win-acme renewals fail after port 80 is blocked: diagnostic checklist covering inspect the validation plugin stored in the affected win-acme renewal, test the DNS hook with the same Windows account used by the scheduled task, check IIS binding deployment after successful certificate issuance.
win-acme renewals fail after port 80 is blocked: diagnostic checklist covering inspect the validation plugin stored in the affected win-acme renewal, test the DNS hook with the same Windows account used by the scheduled task, check IIS binding deployment after successful certificate issuance.

Configure win-acme on Windows 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.

With win-acme, select a supported DNS script-validation workflow and use the reviewed PowerShell example for an existing SimpleACME registration. The create hook needs the current challenge value, an explicit account mapping and a failure path when the API request or visibility check fails. Keep the credential file outside public web content and grant access only to the intended renewal identity.

Test under the scheduled task's account, not only an administrator's interactive session. That identity may have different environment variables, certificate-store access and network permissions. Save the renewal with the intended installation step; for IIS, check the supported installation plugin and the precise SNI binding. Review logs from the task and probe the resulting service after replacement. DNS validation, certificate-store import and application binding updates are three distinct checkpoints, even when one client orchestrates them.

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

Switching challenge methods does not change the HTTPS listener's firewall requirements for actual users. It removes the separate inbound HTTP validation dependency.

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?

Switching challenge methods does not change the HTTPS listener's firewall requirements for actual users. It removes the separate inbound HTTP validation dependency. 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 win-acme on Windows 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