NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Change NPM Listen port based on Proxy Host

Open
#2,969 10 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

Hi, I have two proxy hosts in my NPM docker container:
I.) Public Website and therefore Port 80 and 443 should be used for NPM to listen on and forward to port 80 of the target HTTP Joomla app. I want that this app is accessible with port 80 and 443
II.) Private self build web app that only I will access. I want that this second proxy host is ONLY accessible via Port 8443

In my docker compose file I created a Host:Container Mapping for all three ports:

    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      - '8443:8443' # Private HTTPS Port
      - '81:81' # Admin Web Port

What I can do so far is add listen 8443 ssl http2; to the Advanced Tab in the target proxy host number II
image

That opens up Port 8443 for the proxy host number I and II.
and Port 443 is still open for proxy host number I and II.

Is there a way to change the default 443/80 listen ports of NPM ONLY for proxy host number II ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the proxy host's Advanced Tab configuration and the docker-compose port mappings described in the issue. Trace how NPM turns per-host listen directives into nginx configuration; done means one proxy host can use 80/443 while another is reachable only on 8443 without changing the other host's listeners.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, nginx
Domain
devops, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.