starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2516] Support other ports (non 80/443) configuration in headers via UI settings #1754

New issue

Open

opened 2026-02-26 07:32:20 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 07:32:20 +03:00

Owner

Originally created by @GAS85 on GitHub (Jan 3, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2516

Is your feature request related to a problem? Please describe.
If my Application runs on different ports, e.g. 907X it will cause a bunch of trouble - port will not be forwarded to the service and at the end redirect happens on port 80 or 443 that are not configured by npm.
Docker-compose

version: "3.6"
services:
  nginx-proxy-manager:
    image: jc21/nginx-proxy-manager:latest
    container_name: npm
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - DB_SQLITE_FILE=/config/database.sqlite
      - DISABLE_IPV6=true
    ports:
      # Public HTTP Port. Port Forwarding on Router is ON.
      - 9070:80
      # Public HTTPS Port. Port Forwarding on Router is ON.
      - 9071:443
      # Admin Web Port. Port Forwarding on Router is OFF. Internal Home Network Access only - 192.168.89.254:81.
      - 9072:81
    volumes:
      - ${WORKINGDIR}/docker/npm/config:/config
      - ${WORKINGDIR}/docker/npm/letsencrypt:/etc/letsencrypt
      - ${WORKINGDIR}/docker/npm/data:/data

On a 1st line Service was found and it tells us to follow url http://jackett.fritz.box:9070/UI/Dashboard.
On a 2nd line Service would like to authorize user, but do not know port, so it skip it in a answer and ended up with wrong URL (no port) http://jackett.fritz.box/UI/Login?ReturnUrl=/UI/Dashboard and 404.

Describe the solution you'd like
Configure port in a proxy_set_header Host $host:PORT; will solve this issue.

Unlike current solution it is only proxy_set_header Host $host;. Add Possibility to enable and add custom port to the header Host.

Describe alternatives you've considered
I tried to use "Custom Location" and set it to the root so I can add proxy_set_header Host $host:PORT; but this will cause this entry twice: without port and at the end with port that cause an error.

Alternative 2 is to mount proxy.conf to the host machine:

    volumes:
      - ${WORKINGDIR}/docker/npm/data/nginx/include/proxy.conf:/etc/nginx/conf.d/include/proxy.conf

and update it:

add_header       X-Served-By $host;
#proxy_set_header Host $host:9070;
# Forward host and port
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Scheme $scheme;
proxy_set_header X-Forwarded-Proto  $scheme;
proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP          $remote_addr;
proxy_pass       $forward_scheme://$server:$port$request_uri;

Additional context
There is no need to modify listen 80; part of the configuration and bind nginx to some other ports, it shall remains untouched. But underlining services need to know the Port.

Originally created by @GAS85 on GitHub (Jan 3, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2516  **Is your feature request related to a problem? Please describe.** If my Application runs on different ports, e.g. `907X` it will cause a bunch of trouble - port will not be forwarded to the service and at the end redirect happens on port `80` or `443` that are not configured by npm. Docker-compose ```yaml version: "3.6" services: nginx-proxy-manager: image: jc21/nginx-proxy-manager:latest container_name: npm environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - DB_SQLITE_FILE=/config/database.sqlite - DISABLE_IPV6=true ports: # Public HTTP Port. Port Forwarding on Router is ON. - 9070:80 # Public HTTPS Port. Port Forwarding on Router is ON. - 9071:443 # Admin Web Port. Port Forwarding on Router is OFF. Internal Home Network Access only - 192.168.89.254:81. - 9072:81 volumes: - ${WORKINGDIR}/docker/npm/config:/config - ${WORKINGDIR}/docker/npm/letsencrypt:/etc/letsencrypt - ${WORKINGDIR}/docker/npm/data:/data ``` ![изображение](https://user-images.githubusercontent.com/6813635/210354844-69443697-f9e7-459b-b688-ceb9cb91d89f.png) On a 1st line Service was found and it tells us to follow url `http://jackett.fritz.box:9070/UI/Dashboard`. On a 2nd line Service would like to authorize user, but do not know port, so it skip it in a answer and ended up with wrong URL (no port) `http://jackett.fritz.box/UI/Login?ReturnUrl=/UI/Dashboard` and 404. **Describe the solution you'd like** Configure port in a `proxy_set_header Host $host:PORT;` will solve this issue. ![изображение](https://user-images.githubusercontent.com/6813635/210356619-0e2202f3-45d5-42fb-980b-6fe5127a99e8.png) Unlike current solution it is only `proxy_set_header Host $host;`. Add Possibility to enable and add custom port to the header Host. **Describe alternatives you've considered** I tried to use "Custom Location" and set it to the root so I can add `proxy_set_header Host $host:PORT;` but this will cause this entry twice: without port and at the end with port that cause an error. Alternative 2 is to mount `proxy.conf` to the host machine: ```yaml volumes: - ${WORKINGDIR}/docker/npm/data/nginx/include/proxy.conf:/etc/nginx/conf.d/include/proxy.conf ``` and update it: ```nginx add_header X-Served-By $host; #proxy_set_header Host $host:9070; # Forward host and port proxy_set_header Host $http_host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_pass $forward_scheme://$server:$port$request_uri; ``` **Additional context** There is no need to modify `listen 80;` part of the configuration and bind nginx to some other ports, it shall remains untouched. But underlining services need to know the Port.

kerem added the

enhancement

label

2026-02-26 07:32:20 +03:00

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@lerra commented on GitHub (Feb 12, 2023):

I have the similar need, to be able to set a custom listening port for a specific domain/vhost/proxy host

@lerra commented on GitHub (Feb 12, 2023): I have the similar need, to be able to set a custom listening port for a specific domain/vhost/proxy host

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@etonline commented on GitHub (May 31, 2023):

Same here, adding proxy_set_header Host $host in the custom setting of the "/" location will cause entry duplicate in the config file 😢

@etonline commented on GitHub (May 31, 2023): Same here, adding` proxy_set_header Host $host` in the custom setting of the "/" location will cause entry duplicate in the config file 😢

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@YUJX19 commented on GitHub (Oct 29, 2023):

The same issue

@YUJX19 commented on GitHub (Oct 29, 2023): The same issue

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 12, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Jun 12, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@GAS85 commented on GitHub (Jun 12, 2024):

👍

@GAS85 commented on GitHub (Jun 12, 2024): 👍

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 17, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 17, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@GAS85 commented on GitHub (Mar 17, 2025):

👍

@GAS85 commented on GitHub (Mar 17, 2025): 👍

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 28, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Dec 28, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@lerra commented on GitHub (Dec 28, 2025):

I would love to see this feature

@lerra commented on GitHub (Dec 28, 2025): I would love to see this feature

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1754

No description provided.

Rows
Columns