Anybody using Caddy as a reverse proxy or a webserver?

eva2000

@ptreja said:
There's a good comparison of Caddy vs NGINX performance here: https://blog.tjll.net/reverse-proxy-hot-dog-eating-contest-caddy-vs-nginx/

I prefer the configuration syntax and auto SSL convenience for Caddy and use it as a reverse proxy for most smaller sites (< 200req/s) but for high traffic sites I still use NGINX for now due to the improved reverse proxy performance.

My follow up reply on their forums for additional tests that can better highlight real usage better https://forum.tjll.net/t/tyblog-35-million-hot-dogs-benchmarking-caddy-vs-nginx/256/5

Thanks for sharing your benchmarks. In the past I’ve done some Nginx vs Caddy benchmarks and noticed as you add more response headers to requests, Caddy’s performance drops more than Nginx does (see links below). As as I’ve been always mindful to test with real world used response headers/equivalent for both web servers.

• Any performance overhead as you add more headers under HTTP/2? - Help - Caddy Community
• GitHub - centminmod/centminmod-caddy-v2
  So I’m curious if in your proxy testing for latest Caddy versions, does the same performance overhead happen with Caddy still exist as you add more response headers?

Looking forward to more of your tests in future :slight_smile:

For performance and scalability Nginx > Caddy. One thing Caddy is better at though is managing SSL certificate storage once you have 10000s of vhosts on the server. Nginx resource usage at 10000s of vhosts for SSL isn't handled as nicely.

For me personally, I'm more likely to have a few Nginx vhosts with higher concurrent traffic than many vhost sites on the same server. So don't see a need for Caddy given my past Caddy vs Centmin Mod Nginx benchmark comparisons.

sreekanth850

@tuc said:
nginx is the best!
a 512mb-ram VPS running certbot can support a hundred of vps for that many number of domains. A path unit systemd service on these vps can help to reload nginx whenever new ssl keys received from the 512mb-ram one.

Yes, We use Nginx. Bu i was looking to replace my bunny service used for custom hostnames and ssl issue for hostnames.

sreekanth850

@akhfa said:

@ehab said:

@tentor said:
Generally I prefer nginx, but for containerized infrastructure Caddy with https://github.com/lucaslorentz/caddy-docker-proxy much more convenient comparing to nginx.

isnt this like https://traefik.io/traefik/ much older and production ready?

I think so. Using traefik since version 1.5 iirc. No usability issue so far. I use it for any reverse-proxy in container needs, in production also. Works great including on kubernetes. It also have clear business model as a company.

What I hate about it is when migrating kubernetes ingress from version 1 to version 2. It is like learning new things because they rewrite the software design. But for docker compose use, no problem.

The documentation can be complicated at first, but after getting used about how traefik works, it is pretty good enough.

Will try this looking much better than caddy in terms of usability.

sreekanth850

@buyserver said:
Nginx Proxy Manager . Does SSL etc... It is mostly used for home labs but can be used for other things. It is free and super easy to use.

Mainly for personal uses it can be good not for production i think. never tried this.

ehab

@eva2000 said:

cab you please recommend/gits some post for nginx conf to serve in production static/php/stream/limit/filter/use inline lua

all those goodies

thanks
ehab

tjn

NGINX is amazing, but I love Caddy.
I find it easier to issue SSL certs, integrate with CloudFlare and automate with Ansible.

lukehebb

I don't personally but I know Fathom Analytics uses Caddy

labrax

I use it for my jellyfin server for https and cloudflare workers reverse proxy.