
Nginx Proxy Manager is an open-source, Docker-based tool that provides a clean, web-based user interface for managing Nginx reverse proxy hosts.
NPM Proxy host is like a digital receptionist. It's job is to look at specific requests and decide which specific container or IP address on your internal network should handle it.
When you create a host in Nginx Proxy Manager (NPM), you are essentially filling out a routing slip.
This is the "Address" written on the envelope. When a request hits your server, Nginx looks at the Header. If the header says wiki.mehefko.io, it follows the rules you set for that specific host. If it says site.mehefko.io, it follows a different set of rules.
This is how Nginx talks to your container.
Most common for homelabs. Nginx talks to your container in "plain text" internally.
Only used if the container itself is already running its own SSL certificate.
This is the "Destination."
If the container is on the same Docker network as NPM, you can just use the Container Name.
If the application is on a different machine, you use that machine’s Local IP (e.g., 192.168.1.xx).
The specific "Internal Door" the application is listening on. For Wiki.js, it’s usually 3000. For WordPress, it’s usually 80.