Repository files, collaboration, releases and project activity.
ARCHFORGE HISTORY
Blame · CHANGELOG-1.0.3.md
Branch main · the Commit author is not necessarily a verified ArchForge account.
c50a429023archadmin2026-10-11
1 # v1.0.3 — Dedicated VPS Caddy HTTPS recoveryc50a429023archadmin2026-10-11
2 c50a429023archadmin2026-10-11
3 - Add `fix-https.sh` and `scripts/fix-https.sh` to repair a Caddy instance stuck on HTTP :80.c50a429023archadmin2026-10-11
4 - Check the status backend before touching the proxy; create a persistent Caddyfile backup.c50a429023archadmin2026-10-11
5 - On the dedicated VPS, use a direct TLS domain site instead of the stock Debian Caddy landing page.c50a429023archadmin2026-10-11
6 - Verify that TCP 443 is listening; automatically restore the prior configuration if it is not.c50a429023archadmin2026-10-11
7 - Check for a verified TLS certificate without misrepresenting a pending ACME challenge as success.c50a429023archadmin2026-10-11
8 - Preserve the existing status database, configuration, admin credentials and main website.