[GH-ISSUE #3678] Location directive ( location /{ ) causing proxy host to land at openresty landing page

kerem commented

2026-02-26 07:35:33 +03:00

Owner

Originally created by @cirnoscodingclass on GitHub (Apr 4, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3678

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

Originally created by @cirnoscodingclass on GitHub (Apr 4, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3678 **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](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/156504723/aad4948c-e5e5-4445-8e1e-0e4330beb0a6) **Operating System** Debian 12 Bookworm **Additional context** I am trying run [danbooru](https://github.com/danbooru/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 ```

kerem added the

bug

label

2026-02-26 07:35:33 +03:00

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@unixweb commented on GitHub (Apr 4, 2024):

Same issue here

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

@unixweb commented on GitHub (Apr 4, 2024): 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](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/12023025/fa4d0a90-e438-46e7-8cd1-d6466c5c26ef) ![Bildschirmfoto 2024-04-04 um 19 17 12](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/12023025/77da9360-ae91-4174-b457-bf7ea0f3b2cc) ![Bildschirmfoto 2024-04-04 um 19 17 45](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/12023025/435658b7-fb2a-4e49-ad2e-a8e5cf9509f8)

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@delsonffilho commented on GitHub (Apr 12, 2024):

@unixweb Did you tested in the version 2.11.1?

@delsonffilho commented on GitHub (Apr 12, 2024): @unixweb Did you tested in the version 2.11.1?

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@barrelltitor commented on GitHub (Apr 15, 2024):

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

@barrelltitor commented on GitHub (Apr 15, 2024): @delsonffilho I can confirm this also happens on 2.11.1. I was pulling my hairs out trying to figure out what I broke

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@delsonffilho commented on GitHub (Apr 15, 2024):

I tested on 2.10.4 and it works.

@delsonffilho commented on GitHub (Apr 15, 2024): I tested on 2.10.4 and it works.

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@thebodzio commented on GitHub (Apr 17, 2024):

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.

@thebodzio commented on GitHub (Apr 17, 2024): 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.

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@unixweb commented on GitHub (Apr 17, 2024):

@unixweb Did you tested in the version 2.11.1?

Yes ...

@unixweb commented on GitHub (Apr 17, 2024): > @unixweb Did you tested in the version 2.11.1? Yes ...

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@s0mm3rb commented on GitHub (Apr 25, 2024):

can confirm 2.10.4 works

custom location in 2.11.1 seems to be broken

@s0mm3rb commented on GitHub (Apr 25, 2024): can confirm 2.10.4 works custom location in 2.11.1 seems to be broken

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@masterwishx commented on GitHub (Apr 26, 2024):

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

@masterwishx commented on GitHub (Apr 26, 2024): > 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

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@irrwitzer42 commented on GitHub (May 2, 2024):

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

@irrwitzer42 commented on GitHub (May 2, 2024): At least for me, 2.11.2 seems to have fixed the issues with custom locations!

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@tosolini commented on GitHub (May 4, 2024):

2.11.2 not working, send me to openresty

@tosolini commented on GitHub (May 4, 2024): 2.11.2 not working, send me to openresty

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@Babyyoda777 commented on GitHub (May 7, 2024):

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.

@Babyyoda777 commented on GitHub (May 7, 2024): 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.

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@StuFrankish commented on GitHub (May 29, 2024):

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

@StuFrankish commented on GitHub (May 29, 2024): Can confirm, also having this issue. Running on v2.11.2

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@wakawakaaa commented on GitHub (Nov 19, 2024):

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.

@wakawakaaa commented on GitHub (Nov 19, 2024): 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.

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 23, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (May 23, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@barrelltitor commented on GitHub (May 23, 2025):

👍

@barrelltitor commented on GitHub (May 23, 2025): 👍

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@barrelltitor commented on GitHub (May 23, 2025):

The stale bot is probably the silliest thing people do on github. No developer wants to tackle fixing it, so let's just close it huh?

@barrelltitor commented on GitHub (May 23, 2025): The stale bot is probably the silliest thing people do on github. No developer wants to tackle fixing it, so let's just close it huh?

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@wolicape commented on GitHub (Jun 16, 2025):

Anything new about it ? I had to downgrade my security level by removing headers so it's a real concern.

@wolicape commented on GitHub (Jun 16, 2025): Anything new about it ? I had to downgrade my security level by removing headers so it's a real concern.

kerem commented

2026-02-26 07:35:34 +03:00

Author

Owner

@AjianNie commented on GitHub (Sep 21, 2025):

2025.09 this bug is still affecting everyone, unbelievably.

@AjianNie commented on GitHub (Sep 21, 2025): 2025.09 this bug is still affecting everyone, unbelievably.

Rows
Columns

[GH-ISSUE #3678] Location directive ( location /{ ) causing proxy host to land at openresty landing page #2435