NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Support running nginx proxy manager under a subpath
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating how the web interface generates asset and link URLs, then reproduce the application behind /npm; done means the interface and its assets resolve correctly under that subpath.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- devops, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100