Why need to set Custom Headers?

[afzl-wtu]

This Proxy does not forward real ip of the client to listening service. I need manually set custom location these headers:

   proxy_set_header X-Forwarded-Host $host:$server_port;
   proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
   proxy_set_header X-Forwarded-Proto $scheme;

But on orignal Nginx Proxy Manager we do not need to set headers instead it automatically forward the real ip in request to listening interface.

[Zoey2936]

https://github.com/ZoeyVid/nginx-proxy-manager/blob/develop/rootfs/usr/local/nginx/conf/conf.d/include/proxy.conf they are set

[afzl-wtu]

Is there any way or method we can see if Proxy is including those headers in http request to listener?
Are there any Docker container that can show real ip received in http headers to it?

[Zoey2936]

no idea at the moment

[Zoey2936]

did you maybe made other changes in the advanced tab?

[afzl-wtu]

No Advanced Tab is empty. Also I am using latest version. And MeshCentral container do not boot if I do not put those lines there.

[afzl-wtu]

MeshCentral requires these lines to get real ip of Request sender in order to drop tls and trust proxy. But If I remove those lines and save Then I get 502 bad gateway error. Also this error is presend when using Orignal jc21 NPM. I also add these lines there too for proper working of Meshcentral.

[Zoey2936]

and try again

[afzl-wtu]

Sure I will verify it later. But at the moment I have moved back to JC21 origanl NPM. It is working flawlessly and working without Custom section. It automatically forwards Header of real ip. echoip or meshcentral are working great.

[Zoey2936]

ok, but i thought it also does not work without the settings in the advanced tab on the original?

[afzl-wtu]

It was my mistake as I told you earlier that it does not work on orignal NPM too. But after Reinstalling I see it is working till now.

[Zoey2936]

but did you checked, if that helps?