Overview
Automatic HTTPS is part of the Better-PaaS workflow for turning a VPS into a practical app platform. It reduces manual server work while keeping infrastructure, runtime data, and credentials under your control.
What it does
Issue and renew Let's Encrypt certificates through Caddy routing.
Why it matters
Small teams often lose time on repeated server tasks: editing proxy configs, watching logs over SSH, managing env vars, and recovering from bad deploys. Automatic HTTPS gives that workflow a predictable place in the dashboard.
How to use it well
Keep the setup simple, test with a small app first, and verify the operational path before relying on it for production workloads.
- Start with one app
- Check logs after each deployment
- Document environment variables
- Create backups for stateful services
Operator tip
Verify DNS before adding domains. Use Cloudflare DNS-only (grey cloud) during initial certificate issuance if redirects conflict.
FAQ
Does Automatic HTTPS require Kubernetes?
No. Better-PaaS is designed around Docker containers, Caddy routing, and a lightweight Go control plane.
Is Automatic HTTPS available for every app?
Most features apply broadly, but stateful apps, custom Docker images, and unusual networking setups may need extra configuration.