NginxProxyManager / NginxProxyManager/nginx-proxy-manager
It seems that custom location port forwarding is being ignored (or is it my fault but I hope not)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?
=> Yes - Are you sure you're not using someone else's docker image?
=> Yes - Have you searched for similar issues (both open and closed)?
=> Yes
Describe the bug
Here is what I did:
- Set a proxy Host with following parameters:
- Set a custom location with following parameters:
- Note that the adresse masked in red is always the same.
Here is the behaviour:
- http://sample.test.relis/sandbox redirects to http://sample.test.relis/ on port 80 instead of 4001
- If I switch proxy host port to 4001, whatever the port in custom location, it goes to 4001
=> My conclusion is that custom location port forwarding is being ignored and using proxy host port instead.
Nginx Proxy Manager Version
2.11.3
Operating System
Just NPM running in docker image
And many thanks for this amazing and very useful project!
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
Reproduce the reported custom-location setup with Nginx Proxy Manager 2.11.3 using the latest Docker image. Compare requests to the custom-location port with requests to the proxy host port, then trace how the generated Nginx proxy configuration selects the upstream. Done means the custom location forwards to its configured port instead of the proxy host port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx, typescript
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100