# v1.0.3 — Dedicated VPS Caddy HTTPS recovery

- Add `fix-https.sh` and `scripts/fix-https.sh` to repair a Caddy instance stuck on HTTP :80.
- Check the status backend before touching the proxy; create a persistent Caddyfile backup.
- On the dedicated VPS, use a direct TLS domain site instead of the stock Debian Caddy landing page.
- Verify that TCP 443 is listening; automatically restore the prior configuration if it is not.
- Check for a verified TLS certificate without misrepresenting a pending ACME challenge as success.
- Preserve the existing status database, configuration, admin credentials and main website.