# v1.0.4 — Fix false website outage on HTTP 302

- The **Main Website** reachability probe follows at most three HTTP 301/302/303/307/308 redirects on the **same HTTPS origin**. It requires a successful final HTTP 200 before marking the site reachable.
- The result explicitly says `reachability only` because a redirected login page does not prove all site features work.
- Redirect loops, cross-origin redirects, HTTPS downgrades, and broken endpoints still fail. API and Git Smart HTTP redirects are **never** accepted.
- Adds `apply-monitor-fix.sh` for VPS 2 installations cloned and updated via ArchForge Git. It invokes the existing deployment with automatic backup and code rollback if startup fails; it never removes SQLite data or env secrets.
- Existing incidents resolve after two succeeding website checks. Historical failed measurements are intentionally retained.
- No changes to the primary ArchForge website, Caddy, DNS, passwords or admin setup.