Location directive ( location /{ ) causing proxy host to land at openresty landing page

[cirnoscodingclass]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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
When working under the Advanced tab of Edit Proxy Host I place the following addition to the config dialogue box

location / {
   proxy_set_header Host $http_host;
   proxy_set_header X-Forwarded-Host $http_host;
   proxy_set_header X-Forwarded-Port $server_port;
   proxy_set_header X-Forwarded-Proto $scheme;
   proxy_set_header X-Forwarded-For $remote_addr;
}

When this is added my sites redirects me to this screen

I have also tried to use =/ in front of the location directive but none of my changes appear to register. Also tried to add this configuration in the Custom locations tab but this shuts down the proxy host.

Adding the lines directly to the proxy_host .conf file causes the proxy_host to go offline.

Nginx Proxy Manager Version
2.11.1

Expected behavior
For the headers to be applied to the location directive without redirecting traffic to the openresty page.

Screenshots

Operating System
Debian 12 Bookworm

Additional context
I am trying run danbooru, the SSL certificate is DNS challenged by cloudflare

Docker Engine - Community
 Version:           26.0.0
 API version:       1.45
 Go version:        go1.21.8
 Git commit:        2ae903e

[unixweb]

Same issue here

• image: 'jc21/nginx-proxy-manager:2.10.4'. Works
• image: 'jc21/nginx-proxy-manager:2.11.0' Don't works

[delsonffilho]

@unixweb Did you tested in the version 2.11.1?

[barrelltitor]

@delsonffilho I can confirm this also happens on 2.11.1. I was pulling my hairs out trying to figure out what I broke

[delsonffilho]

I tested on 2.10.4 and it works.

[thebodzio]

I can confirm the problem with version > 2.10.x (running container from official image on Arch with rootless podman)

Hint: I noticed that whenever I tried to set up a custom location for a proxy host in 2.11.x, the config file associated with the edited host was removed from nginx/proxy_hosts. At the same time entry in database appears to be intact, since the host is still listed and remains editable with no data loss, but goes “Offline” as some previous commenters indicated.

[unixweb]

@unixweb Did you tested in the version 2.11.1?

Yes ...

[s0mm3rb]

can confirm 2.10.4 works

custom location in 2.11.1 seems to be broken

[masterwishx]

can confirm 2.10.4 works

custom location in 2.11.1 seems to be broken

Confirm, same issue with latest version goes back to 2.10.4

[irrwitzer42]

At least for me, 2.11.2 seems to have fixed the issues with custom locations!

[tosolini]

2.11.2 not working, send me to openresty

[Babyyoda777]

Broken for 2.11.1 and 2.11.2 whilst 2.11.1 was fully broken, 2.11.2 now just sends to blank page.

[StuFrankish]

Can confirm, also having this issue.
Running on v2.11.2

[wakawakaaa]

same issue. nginx proxy manager is broken v2.12.1

Error "Could not delete file:" occurs only when setting ssl for a domain in the gui.