I’m running a home server with 4 web apps in Docker containers. They’re all on the same network with Nginx Proxy Manager (NPM). I’ve got a domain on Cloudflare and want subdomains for each app.
I set up a Cloudflare Tunnel pointing to NPM (localhost:80). NPM then sends traffic to the right container based on the subdomain.
But now I’m wondering: why use NPM at all? Couldn’t I just point the Cloudflare Tunnel straight to each Docker container?
What extra security or benefits does NPM give me in this setup? It’s working fine, but I want to understand if NPM is really needed here or if I’m overcomplicating things.
As someone who’s been in your shoes, I can tell you that routing through NPM is definitely worth it. I started out connecting tunnels directly to containers, but quickly ran into issues as my setup grew.
NPM gives you a single point of control for all your apps. It’s a lifesaver when you need to tweak configs or troubleshoot issues. Plus, it handles SSL termination beautifully, which can be a pain to manage for each container individually.
One major benefit I’ve found is the ability to easily set up auth for certain apps. With NPM, I can require a login for my more sensitive services without touching the containers themselves.
That said, there’s a bit more complexity involved. You’ll need to keep NPM updated and ensure it’s configured correctly. But for me, the flexibility and control it offers far outweigh the minor hassle.
In the end, it really depends on your future plans. If you think you’ll be expanding your setup, NPM will save you headaches down the line.
Using Nginx Proxy Manager (NPM) with Cloudflare Tunnel offers several advantages over direct container routing. Firstly, it provides a centralized point for managing SSL certificates and domain configurations, simplifying maintenance. NPM also allows for easier implementation of custom headers, rate limiting, and access controls across all your apps.
Moreover, NPM acts as an additional layer of security, shielding your containers from direct exposure. It can handle tasks like URL rewriting and load balancing, which might be challenging to implement directly in your containers.
While routing directly to containers might seem simpler, using NPM gives you more flexibility and control. It’s particularly beneficial if you plan to scale your setup or add more services in the future. The slight performance overhead is usually negligible for home setups.
Ultimately, whether the added complexity is worth it depends on your specific needs and future plans for your home server setup.
routing thru NPM gives u more control over traffic. u can set up custom rules, handle ssl easier, and manage multiple apps from one place. it’s like a traffic cop for ur server.
direct to containers is simpler, but NPM adds flexibility. depends on wat u need. if ur happy with the current setup, stick with it