mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #5214] Allow us to give the Proxy Host a Custom Name #3144
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#3144
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 @jlar0che on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5214
Issue Details:
I used to use Synology's built-in reverse proxy and just migrated everything over to Nginx Proxy Manager! I currently have 86 Proxy hosts set up in Nginx Proxy Manager. For some hostnames I use something generic like "books.myhostname.xyz". In Synology's built-in Reverse Proxy Manager I could give each host a unique name (separate from the hostname used). So on Synology for my example of "books.myhostname.xyz" I did something like "Books (Booklore)".
Proposed Solution:
It would be very helpful if we could give each entry a distinct name!
@crivchri commented on GitHub (Feb 5, 2026):
+1