mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2156] Populate Custom locations "custom Nginx configuration" reflecting file on disc #1545
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1545
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mattiaskagstrom on GitHub (Jul 15, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2156
Is your feature request related to a problem? Please describe.
I just spent 3 hours trying to set "proxy_set_header Host " in the "custom Nginx configuration"-section in Custom locations and kept getting "invalid header" from the server.
This was due to the config already having a line doing the same thing but with the (for me) wrong value.
I found this out here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1556
Describe the solution you'd like
The generated config should be populated in the custom config text area so it can be easily modified. There should also be a "reset to generated values" button.
autofill like this:

Describe alternatives you've considered
An alternative would be for the custom config to completely override the default configuration. but that would not be as easy for a beginner (like me)
this is the behaviour today:


this is what i have today after some manual editing:


@github-actions[bot] commented on GitHub (Feb 13, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 29, 2025):
Issue was closed due to inactivity.