Open Treverr opened 2 years ago
Hi have your same problem !
I have some host that don't work if you don't set proxy_set_header Host
with the called fqdn hostname.
Have you found any solution ?
I had to manually go in and edit to remove that $host line that NPM adds only keeping my custom one.
Depending on your set up, You'll need to go into the docker itself 'docker exec -it nginsproxymanager sh' and and navigate to '/data/.../proxy_hosts' and edit the item manually.
Hi !
What you suggested solved the problem !
Thanks
@jc21 Is there no way to override this line, without resorting to this?
same issue. Trying to proxy s3 through NPM and having this issue.
Thanks!
Hi, there, I had found a way to solve that. You can delete all your custom location in custom location tab, and add all location code in the advance tab. It works for me to add my 'proxy_set_header Host xxxxxxx', hope you too.
Issue is now considered stale. If you want to keep it open, please comment :+1:
For posterity due to the complete lack of documentation of NPM:
Details
, use http
, 0.0.0.0
, 80
to show that settings on this page have no effectAdvanced
, set
location / {
proxy_pass "https://source.com";
proxy_set_header Host "source.com";
}
Issue is now considered stale. If you want to keep it open, please comment :+1:
I have a use case where I am proxying from my server to another hosted website. I found an issue where npm adds the
proxy_set_header Host $host
automatically, and I cannot override it manually, which I need to in this case because the $host is wrong and I needed to manually set it to the upstream host for CDN's to recognize it.$host
is not defined so its nullI tried to do
set $host
in advanced but it just took my proxy offline.For example, I need it to look like this:
but NPM does not let that happen, it makes the configuration like this:
Which does not work upstream.