HTTPS with Caddy and Let's Encrypt
Serve any application over HTTPS with Caddy and free Let's Encrypt certificates: how automatic HTTPS works, installing Caddy, a two-line reverse proxy Caddyfile, several sites and services, Docker Compose, headers, compression and logs, what DNS and firewall settings it needs, rate limits, and troubleshooting certificate errors.
CodexBash, , 5 min read
Every site should use HTTPS, and certificates are free thanks to Let's Encrypt. Yet setting up TLS has traditionally meant installing a client, configuring a web server, wiring up renewal and hoping the cron job keeps working. Caddy is a modern web server that removes all of that: give it a domain name, and it obtains a certificate, configures TLS securely, redirects HTTP to HTTPS and renews the certificate automatically, with no extra tools. This guide puts an application behind Caddy with HTTPS in a few minutes and covers what can go wrong.
Sign in to read the rest
The whole 5 minute article is free with an account, along with every problem, lesson and tutorial. No card.