traefik VS Nginx Proxy Manager

Running Docker Container: AdGuard Home, HomeAssistant, Authelia, Traefik, Cloudflare-Tunnel, Flame

Currently I'm using Traefik as reverse proxy, directing web traffic via SNI. This suggests I wil run into problems having an automatically self-configuring reverse proxy the way docker allows.

I'm not sure if Traefik supports this. I see there's an issue here, but I can't find any PR.

Also, using nginx as a reverse proxy + letsencrypt is totally valid. I moved towards Traefik (https://github.com/traefik/traefik) which neatly integrates with containers and does all letsencrypt management for you (no need to maintain a separate letsencrypt service).

This is my first attempt at self-hosting. I currently own a Raspberry Pi 4 Model B and I would like to use that in order to self-host some software like Portainer, FireflyIII, Vikunja, Gitea etc. I intent to use Docker swarm in order to be able to spin up these software as I have a lot of experience with it and adding new nodes to the cluster is pretty straightforward. ## Use case RPi is going to keep running in my home network and I would like to be able to access it from any other network, not just my local one, from my mobile phone and my laptop. However, I am aware that this introduces a lot of security risks that I would like to properly defend against. ## Architecture Users (a handful of people, mainly myself and family members) will hit the IP of my house at 443. Home Router is going to forward the request to [Traefik](https://github.com/traefik/traefik), that is running on the RPi in Docker Swarm mode. Then, based on host rules, Traefik is going to forward the request to the appropriate Docker Swarm service that will handle the request. I have attached a diagram with the above architecture.

Traefik is a self-maintaining HTTP reverse proxy and load balancer that makes deploying microservices as simple as pointing it at your orchestrator. Integrates with your existing infrastructure components (Docker, Swarm mode, Kubernetes, Marathon, Consul, Etcd, Rancher, Amazon ECS, ...) and configures itself automatically and dynamically. A shout out to R8nbowhorse for the suggestion.

Look into external-dns, cert-manager and traefik or istio for ingress/service mesh to expose services from your cluster in a automated way.

But, when I discovered traefik, everything changed. As it has yaml supported configuration, easy to start-with behavior and fully docker support: it became my favorite service discovery tool.

K3s comes by default with traefik as the ingress controller. I heard great things about it, but I prefer to use ingress-nginx. This is simply because I'm more familiar with it. You can choose pretty much any ingress controller you want for Kubernetes, so pick one according to your own preferences.

I managed to fix the Nginx issue. Just changed my docker-compose.yml to match the one at the very bottom of this thread. Will update if I fix the other issue.

Yes, but if you can run docker. Use nginx proxy manager here

For easier setup I would highly recommend the usage of nginx-proxy-manager. Its docker-rized and the ui makes it really easy to configure. From this point on there are a few things we'll have to know about your situation: Do you plan on running these different web apps on different dubdomains (plex.amazingdomain.moe) or on different paths (amazingdomain.moe/plex). Since you already have a domain, different subdomains should be fairly easy to create. (Paths would be the better solution if you are using a ddns service with a very limited amount of 'domains')

I think you're getting the wrong nginx.... checkout this link https://nginxproxymanager.com/

NginxProxyManager might be of interest. I got tired of trying to get it to work predictably with more than one site in opnsense, and now just forward 80/443 to it to deal with the half-dozen internal sites I want access to, and secured with basic auth and SSLs that it takes care of.

If you're using Docker for your services, I can recommend Nginx Proxy Manager. It's a webUI for nginx, makes it easy to use nginx. I followed this guide to set my home server. The author uses Portainer to manage containers, but you can use docker-compose directly.

I just want to add that nginx proxy manager makes it exceptionally easy and doesn't require someone to directly configure nginx at all.