For me it's https://nginxproxymanager.com/ it's just so easy to setup and use. One docker command and you're up and running with a nice webinterface to manage access to your docker instances with ssl. I heard good things about Traefik too but I have no personal experience with that one. NPM does everything I need and if it ain't broken... :)

Edit: because people love screenshots https://nginxproxymanager.com/screenshots/

Nginx, because it works well and most open-source projects provide good examples for it when setting up things.

nginx. Traefik is near unusable if you ever need something that isn't dockerized. Caddy seems neat, but I miss some options you get with nginx.

nginx is just... good in all aspects.

I use NGiNX and have ever since I started. It just works and is easy to configure.

For me it’s traefik. It’s took me a while to get it working, but it’s actually really easy now. Setting up container access with labels is very convenient!

Traefik, because I can configure it with labels on my containers and don't have to deal with the proxy config every time I add a new service.

Used nginx for years but it's starting to show the signs of its age, same as Apache did a few years before that.

Caddy, slapping essentially 2 lines into a config file and my reverse proxy is ready for my local network and websites? Can’t really beat that

When it comes to some services though like my openwrt router, I do use Nginx since it’s far more likely to be available in some places

HaProxy for most of the stuff and Nginx for very limited stuff. Or a combination between HaProxy and Nginx in some very special cases.

Apache.

I started my self hosted journey over a decade ago and from what I remember most of the guides were for apache so that's what I learned. Over the years Ive added so much that to re-do everything would take down my stuff while I figure it out and I just haven't found it worth it.

Although it's harder to keep it up these days, even setting up my Lemmy instance was a pain because nobody has apache guides anymore so you have to figure it out yourself

One more vote for Caddy, everything just works, simple things are simple but you have a lot of flexibility for more complex situations.

I use Caddy, but recently realising it's not good enough. Dealing with any traffic that's not HTTP/s puts you in a pickle.

Caddy for general reverse proxy stuff, works like magic and makes certs, routing, etc just work.

I also have a lot of my stuff subsequently reverse proxied behind Authentik for anything that shouldn't be exposed to the public internet

Depends ;)

Private: Traefik, as it was default on k3s and I just get used to it. Work: mostly Nginx

I made the switch from NGINX to Caddy. For me, configuring Caddy is much more simple than configuring NGINX. Also Caddy automatically obtains and renews SSL certificates.

So, Caddy's simplicity is what won me over. I don't care about speed since I'm the only user of my self-hosted services.

Of the three I've always used nginx. Easy to setup, and it works. Plus, on a docker based self-hosted instance nginx is preinstalled. The other bonus is it is well documented as a lot of people use it.

Swag container of linuxserver, it's a nginx reverse proxy

I've been a long proponent of nginx but I am currently in the process of migrating to Caddy because of the better presets.

I've switched from NginxProxyManager to Caddy as i don't like the fact that 2.10.3 has just broken the certificate side of things...

The thing i really miss is having a GUI to handle things but having cockpit on the same system makes a (poor) suitable replacement.

When Nginx (and I pushed it hard on others to use) to NPM to Traefik to Caddy. Caddy is just simple, easy setup for Certs, and integrates easily with Authelia.

Apache. My server is kinda stuck in 2018.

Every time something has an update I need to remember how I installed it to start with, a script? From source? By some other random method? I've got gitea waiting to update but I really can't remember how I installed it to start with 🤣🤣

So yeh, Apache, because it first works with my tangled mess

Caddy, the configs are usually pretty simple to get you started (specially the for free https in the standard setup).

Traefik as the ingress for my container hosts, and nginx as an additional layer for public facing stuff.

The nginx layer functions as an additional layer to set up access policies.

Let's see. At work it's a mix between apache (I'm slowly replacing with nginx as services are migrated) and aws's alb ingress controller (while I'm not a fan, it lets me use acm certs).

At home it's all nginx.

• almost everywhere: HAProxy. I like the syntax, ACLs, map files, stick-tables... there's too much to say in a single post, but I use it since 2012 and it never failed me, whatever the need, both at home and at work.
• kubernetes: ingress-nginx. Mostly because it's the first one I tried back in the days and it just works :). Although I should try one of the haproxy based ingresses, or Traefik, which seems interesting too.

Nginx for the old stuff that i configured years ago, caddy for new installs. I hate migrations...

nginx because I like how flexible it is, and I'd started using it as a webserver for normal file serving + PHP site hosting with php-fpm a good time ago anyways.

I'd tried Caddy once but the "quirky" flair included even in things like documentation was far too grating for me, plus I honestly just, don't really like using JSON.

Like some others have said, I use NGINX due to it's flexibility and ease of configuration. I want to be able to tweak performance and security settings to be exactly how I want them, and NGINX let's me do that.

I've been using caddy for a while. I've been really happy with it, it is very small learning curve especially for someone brand new to reverse proxies. Config file syntax is very simple.

However I've been thinking of moving to nginx. After I learned about OpenResty and the possibility to script nginx with Lua, nginx is very tempting. Sadly caddy has nothing similar.

I used to use Traefik but switched to Caddy. I like how easy it is to configure a new reverse proxy for one of my containers. Literally 3 new lines in my Caddyfile, restart the caddy container and away it goes getting certificates etc.