mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3682] Support running nginx proxy manager under a subpath #2434
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#2434
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 @carylewis on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3682
I need to run nginx proxy manager (npm) on a VM that only I can reach only via ports 80 and 443 due to very restrictive firewall rules in place
I would like to be able to run npm with a subpath, so that I can create a custom location for it, e.g. https://www.example.com/npm
I created a custom location to map /npm to localhost port 81, but when I try to access http://www.example.com/npm, the assets, etc. all use "/" instead of "/npm"
Is there a way to configure npm to use a default_url, so that all links that it emits will use the desired subpath?
@Junt62 commented on GitHub (Apr 16, 2024):
please use custom location.
@carylewis commented on GitHub (Apr 16, 2024):
That isn’t sufficient, as the links that npm generates, won’t have the right path.
@github-actions[bot] commented on GitHub (Oct 25, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@carylewis commented on GitHub (Oct 25, 2024):
Anyone also facing this issue?
@github-actions[bot] commented on GitHub (Jul 4, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@carylewis commented on GitHub (Jul 4, 2025):
This issue still exists. It’s possible to workaround it with ssh tunnels but having a configuration to al the default url to include a path would be very useful.
@github-actions[bot] commented on GitHub (Feb 13, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍