[GH-ISSUE #678] Streams names / notes #571

Closed
opened 2026-02-26 06:33:27 +03:00 by kerem · 6 comments
Owner

Originally created by @Wadera on GitHub (Oct 27, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/678

Is your feature request related to a problem? Please describe.
I'm always frustrated when I need to check one of dozens of Steams on my Nginx Proxy Manager panel..
I need to keep separate wiki page to get described which port is streamed where and why or do additional investigations.

Describe the solution you'd like
Let's just add simple, not required "name" field which can appear on the list. Additional "note field" would be additional benefit.

Example Stream list:

streams

Example Stream edit field:

Edit-streams

Originally created by @Wadera on GitHub (Oct 27, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/678 **Is your feature request related to a problem? Please describe.** I'm always frustrated when I need to check one of dozens of Steams on my Nginx Proxy Manager panel.. I need to keep separate wiki page to get described which port is streamed where and why or do additional investigations. **Describe the solution you'd like** Let's just add simple, not required "name" field which can appear on the list. Additional "note field" would be additional benefit. **Example Stream list:** ![streams](https://user-images.githubusercontent.com/407236/97344829-30974580-1881-11eb-8831-229ac84fcbc4.PNG) **Example Stream edit field:** ![Edit-streams](https://user-images.githubusercontent.com/407236/97344836-32f99f80-1881-11eb-9bc6-f509be8b876d.PNG)
kerem 2026-02-26 06:33:27 +03:00
Author
Owner

@diwu1989 commented on GitHub (Jan 1, 2021):

+1 I really need to be able to put a single non-unique label to name the streams please, just for organization purposes

<!-- gh-comment-id:753257464 --> @diwu1989 commented on GitHub (Jan 1, 2021): +1 I really need to be able to put a single non-unique label to name the streams please, just for organization purposes
Author
Owner

@github-actions[bot] commented on GitHub (Mar 24, 2024):

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

<!-- gh-comment-id:2016661922 --> @github-actions[bot] commented on GitHub (Mar 24, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@Wadera commented on GitHub (Mar 24, 2024):

I'm still hoping to get that feature

<!-- gh-comment-id:2016738596 --> @Wadera commented on GitHub (Mar 24, 2024): I'm still hoping to get that feature
Author
Owner

@github-actions[bot] commented on GitHub (Dec 17, 2024):

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

<!-- gh-comment-id:2547348183 --> @github-actions[bot] commented on GitHub (Dec 17, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Jan 3, 2026):

Issue was closed due to inactivity.

<!-- gh-comment-id:3706609358 --> @github-actions[bot] commented on GitHub (Jan 3, 2026): Issue was closed due to inactivity.
Author
Owner

@Wadera commented on GitHub (Jan 4, 2026):

That's so sad :(
I was really hope to see this function developed some day!

<!-- gh-comment-id:3708246852 --> @Wadera commented on GitHub (Jan 4, 2026): That's so sad :( I was really hope to see this function developed some day!
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#571
No description provided.