Repository files, collaboration, releases and project activity.
ARCHFORGE HISTORY
Blame · CHANGELOG-1.0.4.md
Branch main · the Commit author is not necessarily a verified ArchForge account.
6b0b538dd6archadmin2026-10-11
1 # v1.0.4 — Fix false website outage on HTTP 3026b0b538dd6archadmin2026-10-11
2 6b0b538dd6archadmin2026-10-11
3 - 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.6b0b538dd6archadmin2026-10-11
4 - The result explicitly says `reachability only` because a redirected login page does not prove all site features work.6b0b538dd6archadmin2026-10-11
5 - Redirect loops, cross-origin redirects, HTTPS downgrades, and broken endpoints still fail. API and Git Smart HTTP redirects are **never** accepted.6b0b538dd6archadmin2026-10-11
6 - 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.6b0b538dd6archadmin2026-10-11
7 - Existing incidents resolve after two succeeding website checks. Historical failed measurements are intentionally retained.6b0b538dd6archadmin2026-10-11
8 - No changes to the primary ArchForge website, Caddy, DNS, passwords or admin setup.