31-Aug-2026 — show a dead www redirect as broken and make it repairable ref #372

build 870 — commit 4f53df4

What's new

A custom-domain www address could fail to open while the apex site worked. The admin Hostnames screen showed a green Redirecting badge because a Cloudflare rule existed, even though DNS was still a leftover Fly CNAME and visitors never reached Cloudflare. The list now uses the mintcake sortable table, flags that case as Redirect not live, and offers Repair redirect on the row so the unused half of the pair actually sends people to the live site. Hostnames then leads with one verdict for the whole set of addresses, so after Repair you see that the site is live and the redirect is finishing, rather than a list of probe details to decode. An unused free NGX host is marked optional, not as a problem.

Before adding www: Hostnames says the site is live on the apex. www has no DNS and is unused. The unused free NGX host is optional. Apex / www redirect at the bottom is the form that creates the missing half of the pair.

Just after Set up redirect: one banner for the whole set of addresses. The site is live, the redirect is still finishing, and www is Waiting (proxied placeholder, HTTPS not up yet). The session log shows the proxied A record and the 302 rule.

At a glance

• www is shown as broken instead of healthy when a Cloudflare redirect exists but DNS is not proxied
• Repair redirect on that row replaces the leftover DNS-only CNAME so the existing rule can fire
• Hostnames leads with one recommendation for every address on the environment, not a row-by-row dump
• After Repair, a proxied redirect that has not finished HTTPS yet is Waiting, with Re-check, not Unreachable
• The unused free NGX host is optional when a custom domain already serves, with Remove still on that row
• Hostname and custom-domain lists use the mintcake sortable table, with sort kept in the URL
• Change existing environment uses framed sections for details, what to do, and hostnames

After Re-check, once Cloudflare HTTPS is up: the banner is The site is live, and www is Redirecting with HTTPS 302. Visitors who type the www address are sent to the live apex.

The unused free NGX host can be taken off from its row. That deletes its DNS records and Fly certificate. The custom domain that already serves the site is left as it is.

Remove subdomain on the unused free NGX host asks you to confirm. That deletes its DNS and Fly certificate, not the live custom domain.

After Remove: Hostnames reports NGX subdomain removed. The site is still live on the custom domain, www still redirects, and the free host stays listed as optional and not created.