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/
I second that. Amazing easy to use, configure, supports (LetsEncrypt) certificates via DNS-01 challenge and integrates with ease with most DNS providers.
Paired with authentication providers (keycloak, authelia, authentik), the “advanced” textbox lets you do forward proxying really easy, or customize your “basic proxy”.
I’m not sure how many of these features are present in Traefik, it would be really nice if any of you know if any of these are easily supported in it:
- Forward proxying
- Custom rewrites (nginx
internal;
rewrites) - Unattended DNS-01 support with ACME (LetsEncrypt)
I used NPM for a very long time, but after I switched to podman, DNS name resolution for containers stopped working in NPM, they work fine in every other container. Switched to caddy and it’s okay, it only supports HTTP transports so I can’t use it as a gateway for my DoH/DoT server, but that’s not a huge deal. Once NPM works properly on podman I may switch back
Depends ;)
Private: Traefik, as it was default on k3s and I just get used to it. Work: mostly Nginx
HaProxy for most of the stuff and Nginx for very limited stuff. Or a combination between HaProxy and Nginx in some very special cases.
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.
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.
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.
Traefik across 3 nodes internally for its Nomad service discovery. HAProxy for my non-Nomad stuff.
Another nomad person! There are dozens of us!
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!
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.
I’m not a Caddy expert (nor a Traefik one) but with Traefik I didn’t even have to add any line to its config. I just use a template docker-compose and set the domain and the port.
Yeah from memory (was a while ago), Traefik hooks into the docker socket to auto-discover containers that have a specific label? Might not be remembering that correctly.