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... :)

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

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

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.

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!

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.

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

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.

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

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

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

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.

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

Depends ;)

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

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 across 3 nodes internally for its Nomad service discovery. HAProxy for my non-Nomad stuff.

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.

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.

Went from 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.

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.

In the past I've used SWAG and NPM and then later traefik when I was using Docker, but now that I've switched to Kubernetes I only use Traefik which oddly is an altogether different beast than Traefik for Docker which I find odd. On K8S traefik is pretty straightforward to use while on Docker it's a bit of a mess so much so that I made a github repo about how to set it up

- This somehow got posted even though I had only clicked Preview, don't know how that happened -

so that others in the future could figure out how to get Traefik working in docker because the documentation was kinda terrible.

I also tried Caddy (2 I think) but couldn't get it to work because the documentation was awful and in order to use DNS based authentication for LE certs you have to make your own docker container which is nuts; and there's no documentation for that either (at least none that I could find)

caddy for not having to think about TLS

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.

Nginx, more specifically lsio's SWAG container. I like using it because of it's flexibility, relative ease of use and integration with authelia/authentik

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

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.

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.