mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #4454] Custom Location list #2851
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#2851
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 @bailianhua on GitHub (Mar 27, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4454
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Right now the Proxy Hosts tab in the UI list the domain name of the source and destination which we want to forward it to. Which are working great just like we expected. But we have a condition to use the subdirectory for each app behind the proxy. ie. test.com/app1 for app1. , test.com/app2 for app2. and so on. I add it to custom location and it works like we need.
But it became a bit messy when we add like 20 or 30 custom location under the same source->destination item.
Describe alternatives you've considered
The list of all custom locations group by source/destination. Just like the Host tab but for each custom location instead. And the tile of all the custom locations.
Additional context
If there's already a way to accomplish this can anyone direct me to the document or a screen. Or if the way I config NPM is wrong please let me know
Thank you.
@github-actions[bot] commented on GitHub (Oct 19, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍