[PR #5114] [MERGED] Added logging for streams based on port #4062

New issue

Closed

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

kerem commented

2026-02-26 08:32:59 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/5114
Author: @Shotz5
Created: 12/31/2025
Status: ✅ Merged
Merged: 1/13/2026
Merged by: @jc21

Base: develop ← Head: develop

📝 Commits (1)

aeb4424 Added logging for streams based on port

📊 Changes

6 files changed (+19 additions, -7 deletions)

View changed files

📝 backend/templates/stream.conf (+7 -1)
📝 docker/rootfs/etc/nginx/conf.d/default.conf (+3 -3)
📝 docker/rootfs/etc/nginx/conf.d/include/log-proxy.conf (+1 -1)
➕ docker/rootfs/etc/nginx/conf.d/include/log-stream.conf (+3 -0)
📝 docker/rootfs/etc/nginx/nginx.conf (+4 -1)
📝 frontend/src/locale/src/ko.json (+1 -1)

📄 Description

I was looking at my service logs behind NPM and noticed some bad actors trying (and failing as I have it setup properly :D ) to access my service behind an NPM stream. I looked at the NPM logs and noticed that there was no place for stream-specific logs to grab the actors IPs and block them. So I've added it myself for contribution back. I'm sure I could have grabbed it from the NGINX logs within the container, but this is a much more NPM friendly way of logging imo.

_{🔄 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/5114 **Author:** [@Shotz5](https://github.com/Shotz5) **Created:** 12/31/2025 **Status:** ✅ Merged **Merged:** 1/13/2026 **Merged by:** [@jc21](https://github.com/jc21) **Base:** `develop` ← **Head:** `develop` --- ### 📝 Commits (1) - [`aeb4424`](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/aeb44244a720f453681648eff9c182a29aa62dcd) Added logging for streams based on port ### 📊 Changes **6 files changed** (+19 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `backend/templates/stream.conf` (+7 -1) 📝 `docker/rootfs/etc/nginx/conf.d/default.conf` (+3 -3) 📝 `docker/rootfs/etc/nginx/conf.d/include/log-proxy.conf` (+1 -1) ➕ `docker/rootfs/etc/nginx/conf.d/include/log-stream.conf` (+3 -0) 📝 `docker/rootfs/etc/nginx/nginx.conf` (+4 -1) 📝 `frontend/src/locale/src/ko.json` (+1 -1) </details> ### 📄 Description I was looking at my service logs behind NPM and noticed some bad actors trying (and failing as I have it setup properly :D ) to access my service behind an NPM stream. I looked at the NPM logs and noticed that there was no place for stream-specific logs to grab the actors IPs and block them. So I've added it myself for contribution back. I'm sure I could have grabbed it from the NGINX logs within the container, but this is a much more NPM friendly way of logging imo. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-26 08:32:59 +03:00

closed this issue
added the
pull-request
label

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#4062

No description provided.

Rows
Columns