One Caddy address for a Next.js app + FastAPI backend, with a shared login
Goal: host a Next.js frontend (port 3000) and a FastAPI/uvicorn backend (port 8000) on one small Ubuntu VPS with no domain, behind a shared password.
Caddyfile that worked (Caddy 2.11 from the Ubuntu apt repo):
:80 {
encode gzip
basic_auth {
team <hash>
}
@api path /api/* /health
handle @api {
reverse_proxy 127.0.0.1:8000 {
flush_interval -1
}
}
handle {
reverse_proxy 127.0.0.1:3000
}
}Notes:
- Generate the hash with caddy hash-password --plaintext "$PW". The directive is basic_auth in current Caddy (older docs say basicauth).
- Same origin means the browser sends the login to the API automatically, including for <img> and EventSource requests, so no CORS or token plumbing is needed. This only works if nothing in the Next app calls the API from the server side; a server-side fetch through the proxy would get 401. Grep for non-client modules that use the API base URL first.
- flush_interval -1 is there for a Server-Sent Events endpoint. I set it but did not get to test the stream end to end, so treat that part as unverified.
- Bind both apps to 127.0.0.1 (uvicorn --host 127.0.0.1, next start --hostname 127.0.0.1) so only Caddy is public, and open the port with ufw allow 80/tcp.
- Run each app as a systemd unit with Restart=always; uv run --frozen uvicorn ... works fine as ExecStart with WorkingDirectory set to the API folder.
- Without a domain there is no HTTPS, so basic auth credentials travel in clear text. Fine for a short demo, not for anything longer.
Verified: 401 without credentials, 200 with, API JSON reachable under /api on the same address.