[GH-ISSUE #1785] Disable default headers set by nginx-proxy-manager #1318

Open
opened 2026-02-26 07:30:29 +03:00 by kerem · 11 comments
Owner

Originally created by @SamuelNitsche on GitHub (Jan 21, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1785

Is your feature request related to a problem? Please describe.
I have a case where the proxied application stops working if the default Host header (proxy_set_header Host $host) is set. This is done automatically by nginx-proxy-manager.

Describe the solution you'd like
Add a checkbox (unchecked by default) to create a "raw" proxy where only the proxy_pass directive is set in the configuration file.

Describe alternatives you've considered
No alternatives I can think of.

Originally created by @SamuelNitsche on GitHub (Jan 21, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1785 **Is your feature request related to a problem? Please describe.** I have a case where the proxied application stops working if the default Host header (`proxy_set_header Host $host`) is set. This is done automatically by nginx-proxy-manager. **Describe the solution you'd like** Add a checkbox (unchecked by default) to create a "raw" proxy where only the `proxy_pass` directive is set in the configuration file. **Describe alternatives you've considered** No alternatives I can think of.
Author
Owner

@vivedo commented on GitHub (Feb 10, 2022):

I faced the exact same issue and solved it by removing the proxy_set_header lines from the config template file and adding them in frontend/js/models/proxy-host-location.js as a default value for the advanced_config field, thus maintaining the default behaviour while allowing maximum configurability.

cb28f98

<!-- gh-comment-id:1034715301 --> @vivedo commented on GitHub (Feb 10, 2022): I faced the exact same issue and solved it by removing the ```proxy_set_header``` lines from the config template file and adding them in ```frontend/js/models/proxy-host-location.js``` as a default value for the ```advanced_config``` field, thus maintaining the default behaviour while allowing maximum configurability. [cb28f98](https://github.com/vivedo/nginx-proxy-manager/commit/cb28f983ee1b264ccdc93d8c28f0712622e6c3e7)
Author
Owner

@SamuelNitsche commented on GitHub (Feb 10, 2022):

Seems like a good solution. Could you make create a PR with these changes?

<!-- gh-comment-id:1034725063 --> @SamuelNitsche commented on GitHub (Feb 10, 2022): Seems like a good solution. Could you make create a PR with these changes?
Author
Owner

@vivedo commented on GitHub (Feb 10, 2022):

Here it is #1844

<!-- gh-comment-id:1034741589 --> @vivedo commented on GitHub (Feb 10, 2022): Here it is #1844
Author
Owner

@jpdsc commented on GitHub (Dec 12, 2022):

I'm facing the same issue when adding Authelia in the custom locations instead of advanced tab.
Due to 1 or more proxy_set_header which is added as default causes the login to not work.

Is there news on when this PR will be released?

<!-- gh-comment-id:1346570663 --> @jpdsc commented on GitHub (Dec 12, 2022): I'm facing the same issue when adding Authelia in the custom locations instead of advanced tab. Due to 1 or more proxy_set_header which is added as default causes the login to not work. Is there news on when this PR will be released?
Author
Owner

@CrazyFluffyPony commented on GitHub (Dec 18, 2022):

+1

<!-- gh-comment-id:1356881132 --> @CrazyFluffyPony commented on GitHub (Dec 18, 2022): +1
Author
Owner

@manuelmanhart commented on GitHub (Aug 29, 2023):

I have the same issue for some testing purposes, sadly the PR got deleted / closed :-(

<!-- gh-comment-id:1697486182 --> @manuelmanhart commented on GitHub (Aug 29, 2023): I have the same issue for some testing purposes, sadly the PR got deleted / closed :-(
Author
Owner

@github-actions[bot] commented on GitHub (May 5, 2024):

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

<!-- gh-comment-id:2094546346 --> @github-actions[bot] commented on GitHub (May 5, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@peschee commented on GitHub (Aug 28, 2024):

This issue still persists… The configuration added in the advanced_config section is being added before the defaults.

See also https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2675#issuecomment-2298429185

<!-- gh-comment-id:2315931870 --> @peschee commented on GitHub (Aug 28, 2024): This issue still persists… The configuration added in the `advanced_config` section is being added before the defaults. See also https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2675#issuecomment-2298429185
Author
Owner

@rafael-manochio commented on GitHub (Jan 31, 2025):

Can confirm, this issue still exists in version v2.12.2.
Someone found a workaround?

<!-- gh-comment-id:2628457638 --> @rafael-manochio commented on GitHub (Jan 31, 2025): Can confirm, this issue still exists in version v2.12.2. Someone found a workaround?
Author
Owner

@KevinMitchell commented on GitHub (Apr 24, 2025):

Am I correct in thinking that at present if I have any service that requires the Host header to be set to anything other than $host then I can't use Nginx proxy manager and must use "raw" Nginx? What was the logic behind loading additional headers BEFORE the predefined ones? It seems bizarre so I'm curious what the reasoning was.

<!-- gh-comment-id:2828488470 --> @KevinMitchell commented on GitHub (Apr 24, 2025): Am I correct in thinking that at present if I have any service that requires the Host header to be set to anything other than $host then I can't use Nginx proxy manager and must use "raw" Nginx? What was the logic behind loading additional headers BEFORE the predefined ones? It seems bizarre so I'm curious what the reasoning was.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 8, 2025):

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

<!-- gh-comment-id:3505602256 --> @github-actions[bot] commented on GitHub (Nov 8, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1318
No description provided.