1. With the recent benchmarks from 35 hotdogs I wouldn't hesitate to recommend Caddy in place of Nginx for a proxy or webserver.

  2. Simple , when your using the default let's encrypt SSL cert, a tad less so when you need to install a more well known CA cert.

  3. I’ve found caddy’s “automatic” ssl to be absolutely obnoxious if you use a cdn like cloudflare, where your server is expected to answer for a host name that doesn’t resolve to it. You can give your backend a different host name, but then caddy won’t properly route proxied requests. Nginx is much more capable of handling this common configuration.

  4. Everybodys saying to use caddy because its simple but if you're learning I'd recommend using Nginx. Its really no that hard at all to make a conf file and it actually teaches you how a reverse proxy works. If you learn how to use nginx you can use all other reverse proxy managers easily. Furthermore nginx can be compiled with a bunch of different features and its not just a reverse proxy, its a bunch of things. Nginx is very very versatile.

  5. I know I’m late to the party but I never understand why learning something more complicated is more beneficial than just getting started. Stay easy and apply the lessons learnt to something more complex, no?

  6. I’m gonna side with the caddy folks here. I don’t see the point in learning nginx just for learning’s sake. It’s just a tool. Use the best tool for the job. Same reason you don’t use a jackhammer to replace the tile in your bathroom: a sledgehammer is easier to use

  7. For me this is the best answer I have found. I was hooked on comments about "simplicity of Caddy" and it being a new generation server, and so on. But, as someone who will learn from start for the first time it seems more appropriate to learn an industry standard package, even if it takes more time, and when done, to be able to use it at some point maybe even in some professional environment, then later maybe move to Caddy2, then to learn Caddy2, and then at some point learn again and again the same thing.

  8. Caddy has an API and it's extensible thus having hundreds of modules that you can compile as you wish. I fail to see how much better off a homelab user or anyone not in enterprise or millions of users territory would gain from Nginx.

  9. If you’re looking for a reverse proxy, Traefik is fantastic. Simple to add new services via docker labels and takes care of the ssl certs and such.

  10. I am a bit surprised that nobody talks about HAproxy. Fair enough, it doesn't handle static files, but AFAIR, it beats nginx hands down. I really like how it jails itself.

  11. Caddy is so much easier to use than nginx. It just works, unlike nginx which I struggled with to serve a static site and enabling SSL.

  12. Will Caddy handle SSL for a server that runs on LAN only? That was the hardest part of the work I did to get NGINX to work properly (and I forget if I documented it properly!)

  13. Nginx is a full blown web server with tons of features and scaling well. Caddy for me is 2 T-shirt sizes smaller and fits well into more limited usecases like „tls reverse proxy for a couple of Docker delivered http services“.

  14. I'm getting really annoyed with Traefik's overly complicated, Kubernetes-as-an-afterthought configuration and useless error logging. I'm liking what I read about Caddy and will be trying it soon.

  15. Honestly, I was very confused about reverse proxies in general and wanted to move away from nginx to caddy . Just the first page of your guide cleared my doubts and made me aure to move. Cheers mate!

  16. I was using nginx because it's what I was the most familiar with. However a couple of months ago I switched everything both docker services and non docker services to two Traefik services. One for internal and one for external. Initially it was just a learning exercise, but now that I'm intimate with it. I like it, and will keep with it for a while.

  17. I used to write a proprietary module for Nginx and having looked at their code, honestly I would get off it.

  18. I started with nginx and spent hours figuring out how to get everything working including SSL and Authelia authentication. When I couldn't figure out how to get websockets working correctly I tried Caddy, and it worked with just the standard reverse_proxy config, zero effort. Switched everything else over in less than an hour, it's so much simpler to use.

  19. It's great the direction that web servers are going in. Ten years ago we would have been comparing apache with the new nginx and saying the same things!

  20. My limited noob experience is that Caddy is relatively intuitive (as in, I was able to follow a tutorial with errors in and still quickly figure it out) So for usability at least, Caddy.

  21. Are you able to share the tutorials for Caddy with me? Trying to set up reverse proxy and I'm having some trouble.

  22. I ran all of my servers on Apache for 15 years. Then I ran them on NGINX for 15. This year I switched to Caddy and it's so good in every way that I'll never go back.

  23. I had a great experience moving from Nginx to Caddy 1. A huge simplification in my software stack. I had a miserable experience moving from Caddy 1 to Caddy 2, and eventually regressed to Nginx. My problem is with caching, the cache-handler software. It is way way too complex. And the documentation is rather limited. The caddy 1 caching was quite simple and worked great. It is now called cdp-cache, but it has not been upgraded to the current version.

  24. Nginx, because that's what's best supported on NixOS and was what I used before anyway. And it's as easy as

  25. I’m gonna be the odd 3rd wheel and suggest traefik. Super powerful, yeah can be a pain to configure, but works wonderfully.

  26. I really like nginx since it's kind of the de facto standard of reverse proxies however when I started using a lot of docker containers I started integrating traefik. Just depends on your use case. I wouldn't downgrade to npm however.

  27. I've used them all and switched to Cloudflare tunnels for all my apps, no fuss, minimal config, web interface to tweak addresses. It just works. New zero trust dashboard configs everything, you don't even have to tweak a local folder anymore.

  28. I use Apache and Nginx. Apache works, I've been using it for 10ish years, while it might not be the absolute best performing solution it's more than adequate for most of my self-hosting needs. And I've used Nginx professionally so it makes a lot of sense for me to run and understand. Haproxy appeals to me too though I don't currently run it.

  29. I have been using Caddy from last 3-4 years on my VPS and home server for reverse proxy. Its dead simple, I was using npm before this.

  30. +1 for caddy as a reverse proxy. It’s so easy you wouldn’t think of using something else. And it just works, also the renewal of the ssl certificate is flawless

  31. I use NGINX proxy manager. I started with plain NGINX for local only, then switched to NPM as it got complicated when I started exposing stuff and needed SSL.

  32. nginx config seem familiar for me Pretty much copy the previous config as template and finetuned the new one

  33. I've been using Caddy for my personal sites and for a bunch of domain redirectors for a couple years now, and it's been absolutely great. I haven't used nginx much at all beyond playing. My production stuff is all on Apache and haproxy.

  34. Traefik. I use it for couple years now after leaving nginx for most parts behind. I Switches because back then docker discovery with nginx was only possible with nginx plus and also Auto renew for Let‘s encrypt was more of a DIY when not using nginx plus. I belive that changed with nginx proxy manager but not sure.

  35. Any tutorial for me to learn how to config and install caddy? I'm very amateur, I started with homelab this week.

  36. Caddy all the way for me. I run about 8 small web services via Docker on a Pi and Caddy made it ridiculously easy to reverse-proxy them to different subdomains and I have never once had to think about SSL certs. It's a genuine case of 'just works'.

  37. I am using NPM alongside Authelia for all my apps and quite happy with it. However, I've decide to give a test run for Caddy + Authelia today and I found it much easier in terms of amount of config needed to be added compared to NPM. I still need to figure out the configuration to bypass certain paths from reverse proxies such as /api from authelia in the Caddyfile though.

Leave a Reply

Your email address will not be published. Required fields are marked *

News Reporter