NginxProxyManager / NginxProxyManager/nginx-proxy-manager
proxy_set_header Host $http_host setting does not take effect
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
Nginx Proxy Manager Version
2.11.3
To Reproduce
Steps to reproduce the behavior:
After proxy_set_header Host $http_host is set, it will be placed at the front of "location", resulting in the configuration not being effective. For details, please see the figure
My configuration on the page is as follows:
The configuration information seen in conf is as follows:
As shown in the figure, since proxy_set_header Host $host; is generated by default and is after proxy_set_header Host $http_host;, proxy_set_header Host $host; will take effect.
Expected behavior
Custom configuration should be placed at the end, not at the beginning, to ensure that the custom configuration can take effect normally, as shown in the following figure
Operating System
Additional context
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
Start by reproducing the issue with the nginx-proxy-manager:latest Docker image and inspect the generated nginx configuration for the order of proxy_set_header directives. Trace where the default Host header and custom configuration are assembled; done means custom directives appear after the defaults and the generated configuration uses the custom Host value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100