Free HTTPS Isn't New: What Caddy Really Does (and What the Viral Posts Get Wrong)

By Prahlad Menon 4 min read

A post is going around saying “You can now get HTTPS on your websites for FREE” with a screenshot of the Caddy README. Caddy is excellent, and we’d recommend it. But the framing is about ten years late, and it hides the part that’s actually interesting.

Part 1: What the viral post gets wrong

Free HTTPS has been around since 2015. Free certificates come from Let’s Encrypt, a non-profit certificate authority that went live in late 2015. It uses the ACME protocol, which lets software request and renew certificates with no human involved. Today most HTTPS sites on the web use a free, automatically renewed certificate.

Caddy isn’t new either. It was first released in 2015, and Caddy 2 (a full rewrite) came out in 2020. Since 2020 it’s been a ZeroSSL / apilayer project, which is why the README says “a ZeroSSL project”.

Caddy wasn’t the only way to get this. You could already get free, auto-renewing certificates with:

  • certbot with nginx or Apache, which has been the default for years
  • Traefik, which does automatic HTTPS for Docker and Kubernetes
  • Managed platforms such as Cloudflare, GitHub Pages, Netlify, Vercel and Railway, which add HTTPS for you

So what’s actually special about Caddy? It makes HTTPS the default, not an add-on. You don’t install certbot, set up a cron job for renewals, or edit TLS settings. You write a domain name, and Caddy does the rest:

  • Gets certificates from Let’s Encrypt or ZeroSSL, with automatic fallback between them
  • Renews them well before they expire
  • Redirects HTTP to HTTPS
  • Staples OCSP responses, uses modern TLS defaults and serves HTTP/2 and HTTP/3
  • Issues certificates on demand for many customer domains (useful for SaaS custom domains)
  • Runs a local CA for localhost and internal names, so you can use HTTPS in development too

It’s a single Go binary with no dependencies and a config file that’s often just a few lines long. That’s the real story: no new kind of free certificate, just very good defaults.

Part 2: The practical part — HTTPS for your self-hosted AI apps

This is where Caddy pays off for anyone running local LLMs, agents or internal tools on a VPS or home server. Most of these apps listen on plain HTTP ports: Open WebUI on 3000, Ollama on 11434, n8n on 5678, Qdrant on 6333 and so on. Caddy can put each one behind its own HTTPS subdomain.

1. Point DNS at the server. Create A records such as chat.example.com and n8n.example.com that point to the server’s IP. Open ports 80 and 443.

2. Write a Caddyfile:

chat.example.com {
    reverse_proxy localhost:3000
}

n8n.example.com {
    reverse_proxy localhost:5678
}

# Protect an API that has no auth of its own
ollama.example.com {
    basic_auth {
        prahlad $2a$14$REPLACE_WITH_HASH   # caddy hash-password
    }
    reverse_proxy localhost:11434
}

3. Run it:

caddy run --config Caddyfile
# or with Docker:
docker run -d --name caddy -p 80:80 -p 443:443 \
  -v $PWD/Caddyfile:/etc/caddy/Caddyfile \
  -v caddy_data:/data caddy:2

That’s it. Each subdomain gets a valid certificate the first time it’s requested, and renewals are automatic. Keep the /data volume persistent, or Caddy will request new certificates every restart and can hit Let’s Encrypt rate limits.

Things to watch

  • HTTPS is not authentication. It encrypts traffic, but it doesn’t stop strangers from using your Ollama or Qdrant endpoint. Add basic_auth, IP allowlists or an auth proxy in front of anything that has no login of its own.
  • Ports 80 and 443 must be reachable for the default HTTP challenge. Behind NAT or CGNAT, use the DNS challenge with a DNS-provider plugin, or a tunnel such as Cloudflare Tunnel or Tailscale.
  • For private-only services, Caddy’s tls internal option issues certificates from its local CA. That’s handy on a Tailscale network.
  • Streaming works. Caddy proxies WebSockets and server-sent events without extra config, so token streaming from chat UIs works out of the box.

Bottom line

The viral post is right that Caddy is worth using and wrong that it’s new. Free HTTPS has been standard since Let’s Encrypt. What Caddy adds is HTTPS by default, with zero setup. If you’re self-hosting AI tools, it’s one of the quickest ways to get a clean https:// URL in front of them. Just remember to add authentication, because encryption alone won’t keep anyone out.

Repo: github.com/caddyserver/caddy ¡ Docs: caddyserver.com/docs