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

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 Screenshot from 2024-04-03 21-03-36

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

Apr 04 '24 01:04 cirnoscodingclass

Same issue here

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

Bildschirmfoto 2024-04-04 um 19 21 37

Apr 04 '24 17:04 unixweb

@unixweb Did you tested in the version 2.11.1?

Apr 12 '24 12:04 delsonffilho

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

Apr 15 '24 14:04 barrelltitor

I tested on 2.10.4 and it works.

Apr 15 '24 16:04 delsonffilho

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.