{"id":"6aa5cbe7c042c4906008a9f8","title":"2026 09 12 Issue 319","path":"how-to/committee/release-notes/2026-09-12-issue-319","contentMarkdown":"# 12-Sep-2026 — Environments Monitoring checks the public site URL [ref #319](https://github.com/nbarrett/ngx-ramblers/issues/319)\n\n## [build 938](https://github.com/nbarrett/ngx-ramblers/actions/runs/34715724735) — [commit d3e0575](https://github.com/nbarrett/ngx-ramblers/commit/d3e05750c19e072ebe7229c688d06a1facfa3f23)\n\n_____\n\n## What's new\n\nEnvironments Monitoring used to ask only whether the Fly machine answered. A group site could be down, for example a Cloudflare SSL failure, and still show as healthy. The check now uses each environment's configured Site URL, the address people actually visit, and that is what decides Unreachable versus Healthy.\n\n## At a glance\n\n- Unreachable means the public site URL failed, not that Fly was silent\n- A visitable site stays healthy even when Fly has no certificate of its own for that hostname\n- A certificate that expires within 14 days shows as degraded, with the date\n- Problem rows sort first, and warnings are amber rather than looking like a site that is down","contentHtml":"

12-Sep-2026 — Environments Monitoring checks the public site URL ref #319

\n

build 938 — commit d3e0575

\n
\n

What's new

\n

Environments Monitoring used to ask only whether the Fly machine answered. A group site could be down, for example a Cloudflare SSL failure, and still show as healthy. The check now uses each environment's configured Site URL, the address people actually visit, and that is what decides Unreachable versus Healthy.

\n

At a glance

\n\n"}