[PR #4127] Support for chaning the HTTP and HTTPS port that hosts will listen on #3824

Open
opened 2026-02-26 08:32:05 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/4127
Author: @snordmann
Created: 10/31/2024
Status: 🔄 Open

Base: developHead: configurable-ports


📝 Commits (4)

  • 9844df2 Support for chaning the HTTP and HTTPS port that hosts will listen on
  • c377db5 ups, forgot eslint
  • 8d0ed27 Process folder /etc/nginx/conf.d for HTTP/HTTPS port migration
  • 2a9e573 Adjust log message format

📊 Changes

6 files changed (+127 additions, -9 deletions)

View changed files

📝 backend/internal/nginx.js (+44 -3)
📝 backend/templates/_listen.conf (+6 -6)
📝 docker/docker-compose.dev.yml (+2 -0)
📝 docker/rootfs/etc/s6-overlay/s6-rc.d/prepare/00-all.sh (+1 -0)
docker/rootfs/etc/s6-overlay/s6-rc.d/prepare/55-http-https-port.sh (+62 -0)
📝 docs/src/advanced-config/index.md (+12 -0)

📄 Description

I have seen a few issues that mention that changing the port that nginx listens on is important (especially when using hostNetwork).

I am not totally convinced that NPM should allow these use-cases but I was bored enough to implement it anyway.

Related Issue: #4122


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/NginxProxyManager/nginx-proxy-manager/pull/4127 **Author:** [@snordmann](https://github.com/snordmann) **Created:** 10/31/2024 **Status:** 🔄 Open **Base:** `develop` ← **Head:** `configurable-ports` --- ### 📝 Commits (4) - [`9844df2`](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/9844df27de4845bdb8589d4c10913566c8f50cce) Support for chaning the HTTP and HTTPS port that hosts will listen on - [`c377db5`](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/c377db5d62dd110697d3834c21a05a7432d28be6) ups, forgot eslint - [`8d0ed27`](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/8d0ed27851e18fbc8a3d108a4eefd8d9ba9e1503) Process folder /etc/nginx/conf.d for HTTP/HTTPS port migration - [`2a9e573`](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/2a9e573c61fe6d1a0907ab9b204403b393c9caf1) Adjust log message format ### 📊 Changes **6 files changed** (+127 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `backend/internal/nginx.js` (+44 -3) 📝 `backend/templates/_listen.conf` (+6 -6) 📝 `docker/docker-compose.dev.yml` (+2 -0) 📝 `docker/rootfs/etc/s6-overlay/s6-rc.d/prepare/00-all.sh` (+1 -0) ➕ `docker/rootfs/etc/s6-overlay/s6-rc.d/prepare/55-http-https-port.sh` (+62 -0) 📝 `docs/src/advanced-config/index.md` (+12 -0) </details> ### 📄 Description I have seen a few issues that mention that changing the port that nginx listens on is important (especially when using hostNetwork). I am not totally convinced that NPM should allow these use-cases but I was bored enough to implement it anyway. Related Issue: #4122 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
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#3824
No description provided.