move advanced_config section of /app/templates/_location.conf to top of default config

[clhey]

I found that custom configurations cannot override the default configurations because nginx prioritizes the configurations appearing earlier. Therefore, I moved the advanced_config section of /app/templates/_location.conf to top of default config。

config：

before nginx proxy file:

after nginx proxy file:

see this issue:
#2675 (comment)

[nginxproxymanagerci]

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-3729

Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes.

[whc2001]

Are you sure that the config entry on the top will take precedence in Nginx? I have tried myself and the result is the opposite.

The line where the red arrow points to has proxy_set_header Host $host; originally, and I was not able to get my override config of $http_host work until I manually delete the auto generated line below.

[Erzbir]

Why do that? It is no work well if I want set Host header. The nginx will accept the last one, I want to override some configs

[dgm]

Unfortunately, @Erzbir , It seems to me that I get an error with two line lines setting the Host header, no matter which order they are. I have to delete the $host one by hand in order to override the Host header in a custom location.

Why would someone do this?

Server A hosts a mail program, and server B embeds it under b/mail/ ...
Or maybe you are in the process of migrating a service and need to intercept a partial path and send it somewhere else ...