Caddy

“it's written in go so probably listening on an mtcp socket meaning you are probably vulnerable”

“My main HTTP server, Caddy, has gained WebDAV support since I published this configuration, but I haven't used it in anger.”

“I can rely on gifts to the world like Linux, Debian, PostgreSQL, Apache, Nginx, Caddy, and Yggdrasil without any problems for decades.”

“The Caddy container handling certificates and reverse proxies for everything.”

“Nginx, Caddy, Apache, etc have found and fixed a million edge cases you'd never think of”

“I expose my services with a Caddy reverse proxy on a VPS”

“if you are routing over tailscale exclusively Caddy can't automatically validate the domain names over ACME”

“you can also use a reverse proxy like caddy or nginx where encryption and security are primary concerns”

“Mine uses caddy for the Web front, which automates letsencrypt certification.”

“Here's the entirety of the Caddy config to reverse proxy something with managed tls certs.”

“Caddy's admin interface is system-wide opened, any local user can inject configuration and take over everything.”

“simply add a tag/label to your docker compose files for each of self hosted services to get a real SSL, that auto renewed”

“Caddy, their developers and community refuse to believe Caddy is slow is a much bigger issue.”

“Caddy on that machine bottlenecks at 300MB/s despite using 100% of the CPU”

“Another benchmarks showing Caddy not performing on par with Nginx”

“Caddy had multiple vulnerabilities in its request parsing this year”

“Caddy will even do fully automated valid TLS certificates for private IP ranges via DNS ACME challenge for free”

“I reverse proxy everything through a Caddy instance running on the same machine”

“Automatic HTTPS, dead-simple config, and it proxies to your Go binary in about 4 lines.”

“Caddy runs on top of Go's excellent acme library that handles all of the cert acquisition and renewal process automatically.”

“if you're looking for something that "just works" and is widely used, have a look at caddy”

“Caddy checks a Rails endpoint before issuing any certificate, so random domains pointed at your IP won't trigger cert issuance.”

“Caddy trying to get certs by default is annoying”

“I fully understand and appreciate the gifts that things like Docker and systemd and even Caddy have brought to the table”

“Caddy lets you specify any number of ACME providers to try in sequence if the previous ones fail.”

“use its on_demand TLS to handle certificates for the upload and conference subdomains automatically”

“Adding Caddy as a proxy server is literally one line in Caddyfile, and I trust Caddy to do it right”

“Both require minimal configuration, and provide packages for many Linux distributions”

“My web apps aren't allowed to think about TLS, they sit behind Caddy and I'm secure as long as I keep it updated”

“It works, but as another comment mentioned there may be quirks with IP certs, specifically IPv6”

“You add a new app/site in caddy's config and everything else is completely automatic.”

“this works on my mobile devices as well with a dns record to point to this caddy instance”

“automation like Caddy server that does this for us while also being our ingress proxy for all those domains”

“I would probably use a centralized authorization service "authentication gateway" with something like forward_auth in Caddy”

“Thank you Let's Encrypt, together with the acme.sh, caddy and the whole ecosystem for TLS.”

“TLS only takes a few minutes to add to a self hosted solution, just plop caddy in front of your server”

“I am unstarring Caddy. That's absolutely wild.”

“putting ads in your servers via a `Caddy-Sponsors` header”

“there’s no indication from Caddy that you would only be able to renew the cert twice”

“For common web server scenarios, a Caddyfile is very short, much shorter than a typical Apache or nginx configuration.”