---
title: "Discussion on \"🧰 A Beginner's Guide to NGINX and NGINX Proxy Manager\" | Hashnode"
description: "Discussion on \"🧰 A Beginner's Guide to NGINX and NGINX Proxy Manager\". Whether you’re self-hosting applications or deploying websites in production, reverse proxies are one of the most powerful tools in your DevOps toolbox..."
url: "https://hashnode.com/posts/a-beginners-guide-to-nginx-and-nginx-proxy-manager/68502d3d3b418b1769e56b70"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [🧰 A Beginner's Guide to NGINX and NGINX Proxy Manager](https://blogs.arasharora.com/a-beginners-guide-to-nginx-and-nginx-proxy-manager?utm_source=hashnode&utm_medium=feed)

Whether you’re self-hosting applications or deploying websites in production, reverse proxies are one of the most powerful tools in your DevOps toolbox...

Jun 16, 2025 · 5 min read · blogs.arasharora.com  
Read the article

-   [#homelab](https://hashnode.com/tag/homelab)
-   [#nginx](https://hashnode.com/tag/nginx)
-   [#devops](https://hashnode.com/tag/devops)
-   [#server](https://hashnode.com/tag/server)
-   [#reverse-proxy](https://hashnode.com/tag/reverse-proxy)
-   [#web-development](https://hashnode.com/tag/web-development)

## Written by

[Arash Arora](https://hashnode.com/@arasharora)

@arasharora

  
[View profile](https://hashnode.com/@arasharora)

Student

## Responses 1

Markdown supported · ⌘↵ to post

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 5](https://hashnode.com/posts/a-beginners-guide-to-nginx-and-nginx-proxy-manager/68502d3d3b418b1769e56b70/comment/6aebf64bdbab450f512a3747)

Treat plain nginx and Nginx Proxy Manager as the same edge job with different control planes: one public listener pair on 80/443, Host-based routing to unpublished upstreams, and TLS terminated before any app container. With NPM, map each Proxy Host to the Compose service name and its internal listen port on a shared user-defined network; with raw nginx, do the same via proxy\_pass to that service DNS. Leave app ports off the host publish list so a forgotten -p cannot skip TLS or access lists, and keep the NPM admin UI on localhost or an internal-only network reached over an SSH tunnel.

After the first host is live I confirm the leaf SAN matches the advertised name, force-SSL is a single redirect hop, and the upstream still sees the original Host plus X-Forwarded-Proto. A fresh 502 is almost always reachability from the proxy container to the service name or a typo’d internal port — curl the upstream by service DNS from inside the proxy container first, then the same path through the public hostname, and compare status and Location before blaming the app process.
