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.
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.
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.
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/
deleted by creator
I use NGiNX and have ever since I started. It just works and is easy to configure.
Same. I know it’s more work than caddy etc, but I’ve been doing it for eons now so it’s muscle memory at this point.