Infrastructure
Caddy
Fast, extensible web server with automatic HTTPS. No manual certificate handling.
Release notes / v2.11.7
Released 2026-10-03. Snapshot from the included release data, not a live check.
This patch release fixes regressions from 2.11.6, including a crash when proxying over HTTP/2 and streams that were cut off after a minute. **If you're on 2.11.6, we recommend upgrading.** It also adds support for the brand new `Incremental` header field (RFC 10036). **Huge thank you to our sponsors for keeping the project alive with resources, and for our maintainers who triage and assist tirelessly in this relentless new age of AI.** ## Highlights - **Fixed: crash and dropped streams caused by the new idle timeouts.** 2.11.6 introduced default idle read/write timeouts, which caused…
Read the full release notes on GitHub ↗Caddy is an open-source web server written in Go. Its headline feature is automatic HTTPS: it obtains and renews TLS certificates from Let’s Encrypt without any configuration, which removes one of the most error-prone parts of running a site. It serves static files, reverse-proxies to apps, and handles HTTP/2 and HTTP/3 out of the box.
Quick start on NixOS
A Caddy reverse proxy is a few lines in configuration.nix:
services.caddy = {
enable = true;
virtualHosts."example.com".extraConfig = ''
reverse_proxy localhost:8080
'';
};
Why it’s listed
The short configuration is easy to review. Automatic certificates remove a manual maintenance step.
Want help running it? Ask FOSSadmin about hosting and maintenance ↗