mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #1866] Add "comment" field to give a reverse proxy host a name #1364
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1364
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @christofkac on GitHub (Feb 18, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1866
Describe the solution you'd like
For my different services I created reverse proxy settings successfully. In the meantime I have 30 of those and used acrynoms like pt.mydoain.com for Portainer. After some time I keep forgetting this, therefore it would be great if there would be a comment or name column where I could add free text
Describe alternatives you've considered
N/A As I would like to keep my subdomain names short but need an ability to add custom text to name the associated service
@x4x commented on GitHub (Feb 23, 2022):
I think a comment feel for the hosts list would be very useful.
I would also like to have a comment feed for every IP address in a Access List rule. I have rules with up to 15 IPs. Deleting or changing one can become very tedious.
@github-actions[bot] commented on GitHub (Feb 24, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@CWempe commented on GitHub (Feb 25, 2024):
I think this request is still relevant.
@github-actions[bot] commented on GitHub (Dec 1, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 5, 2025):
Issue was closed due to inactivity.