{"id":"6a5c96cbef317779435d46d9","title":"2026 07 19 Issue 319","path":"how-to/committee/release-notes/2026-07-19-issue-319","contentMarkdown":"# 19-Jul-2026 — Environment Management — show live hostname health so a broken web address is visible [ref #319](https://github.com/nbarrett/ngx-ramblers/issues/319)\n\n## [build 780](https://github.com/nbarrett/ngx-ramblers/actions/runs/29680933358) — [commit 2abae87](https://github.com/nbarrett/ngx-ramblers/commit/2abae8781d21d98885dab94d55bc428815962544)\n\n_____\n\n## What's new\n\nOn `admin/platform/environment-management/health`,  a site's web address could stop working without anything on the admin screens showing it. The environment screen only ever checked one internal hostname, so a site served on its own domain could have a dead address indefinitely and still look completely healthy — the problem was only ever found by someone happening to type the address without the www. Environment Management now checks every hostname a site actually answers on, live, and says plainly which are serving, which are redirecting and which are broken.\n\n## At a glance\n\n- A new Hostname health panel shows every hostname for the selected environment, with its DNS record, redirect target and HTTPS response\n- Anything needing attention is called out in a warning above the table rather than left for someone to notice\n- The Environments Monitoring grid gains a Hostnames column, so a broken address is visible across every environment at once instead of only when that environment is selected\n- A misconfigured redirect that would return a 522 timeout is identified as exactly that, rather than failing silently when someone visits\n- Selections on the setup page (mode, environment, action) are held in the URL, so a view can be linked to or restored on refresh","contentHtml":"<h1>19-Jul-2026 — Environment Management — show live hostname health so a broken web address is visible <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/319\">ref #319</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/29680933358\">build 780</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/2abae8781d21d98885dab94d55bc428815962544\">commit 2abae87</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>On <code>admin/platform/environment-management/health</code>,  a site&#39;s web address could stop working without anything on the admin screens showing it. The environment screen only ever checked one internal hostname, so a site served on its own domain could have a dead address indefinitely and still look completely healthy — the problem was only ever found by someone happening to type the address without the www. Environment Management now checks every hostname a site actually answers on, live, and says plainly which are serving, which are redirecting and which are broken.</p>\n<h2>At a glance</h2>\n<ul>\n<li>A new Hostname health panel shows every hostname for the selected environment, with its DNS record, redirect target and HTTPS response</li>\n<li>Anything needing attention is called out in a warning above the table rather than left for someone to notice</li>\n<li>The Environments Monitoring grid gains a Hostnames column, so a broken address is visible across every environment at once instead of only when that environment is selected</li>\n<li>A misconfigured redirect that would return a 522 timeout is identified as exactly that, rather than failing silently when someone visits</li>\n<li>Selections on the setup page (mode, environment, action) are held in the URL, so a view can be linked to or restored on refresh</li>\n</ul>\n"}