max / makenotwork

Check htpy where htpy actually listens The health check pointed at http://100.99.153.68:8080/archive/S_2 on both instances. htpy-web listens on 3200, and /archive/<name> answers 308 to /viewer/<name>, so the check failed on connect and both instances reported the target unreachable with an open incident, hetzner's since 2026-03-29 and astra's since 2026-05-01. htpy.app served fine throughout, which is the tell: the check was watching an address, not the site. Verified before changing: /viewer/S_2 on 3200 returns 200 with "htpy" in the body from fw13, astra and hetzner, and 3200 is already in the tailnet ACL's inter-server port list, so no policy change is needed. Worth noting what this cost. Four months of a target sitting red is four months of the rollup being wrong about production, and a surface that is always wrong about one target is one people stop reading.