kerem commented

Owner

Originally created by @DaFlowah on GitHub (Apr 8, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1003

Describe the bug
Hi, I need to override the default proxy_set_header Host $host to proxy_set_header Host $http_host for a specific Proxy Host, since it's required by the app I'm trying to Proxy (more info here)

To Reproduce
Create a Proxy Host
Go to Advanced and add proxy_set_header Host $http_host;
The value is not applied and the application throws an error.

Expected behavior
I am expecting this value to be added.

Screenshots

Operating System

Nginx Proxy Manager on Home Assistant OS running on Pi4

Additional context
If on the host I edit /etc/nginx/conf.d/include/proxy.conf and change the default value, it works, but it's a temporary change.

Originally created by @DaFlowah on GitHub (Apr 8, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1003 **Describe the bug** Hi, I need to override the `default proxy_set_header Host $host` to `proxy_set_header Host $http_host` for a specific Proxy Host, since it's required by the app I'm trying to Proxy (more info [here](https://github.com/vabene1111/recipes/issues/518)) **To Reproduce** Create a Proxy Host Go to Advanced and add `proxy_set_header Host $http_host;` The value is not applied and the application throws an error. **Expected behavior** I am expecting this value to be added. **Screenshots** ![immagine](https://user-images.githubusercontent.com/33235583/114058043-06fc3480-988b-11eb-8c9a-b98916f5f901.png) **Operating System** - Nginx Proxy Manager on Home Assistant OS running on Pi4 **Additional context** If on the host I edit `/etc/nginx/conf.d/include/proxy.conf` and change the default value, it works, but it's a temporary change.

kerem added the

bug

label

2026-02-26 06:34:38 +03:00

kerem commented

2026-02-26 06:34:38 +03:00

Author

Owner

@ananiasfilho commented on GitHub (Jul 4, 2021):

Any update? I have same issue running flask and odoo behind NPM. I cant see client IP and others headers

@ananiasfilho commented on GitHub (Jul 4, 2021): Any update? I have same issue running flask and odoo behind NPM. I cant see client IP and others headers

kerem commented

2026-02-26 06:34:38 +03:00

Author

Owner

@Nate-09 commented on GitHub (Jul 27, 2021):

Same here, got the same issue with another docker image running remotely.one. I'm also having additional issues with NPM not setting additional configuration under the custom config, wondering if this is an issue with the custom configuration in UI itself.

I've tried to also set additional header info as seen below but when I test for the CSP - these come back as fail from external testing on top of the Client IP and other headers

add_header Content-Security-Policy "upgrade-insecure-requests";
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block" always;
add_header X-Content-Type-Options "nosniff" always;
add_header Referrer-Policy no-referrer always;
add_header X-Robots-Tag none;
proxy_hide_header Upgrade;
proxy_hide_header X-Powered-By;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_cache_bypass $http_upgrade; proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

@Nate-09 commented on GitHub (Jul 27, 2021): Same here, got the same issue with another docker image running remotely.one. I'm also having additional issues with NPM not setting additional configuration under the custom config, wondering if this is an issue with the custom configuration in UI itself. I've tried to also set additional header info as seen below but when I test for the CSP - these come back as fail from external testing on top of the Client IP and other headers add_header Content-Security-Policy "upgrade-insecure-requests"; add_header X-Frame-Options "SAMEORIGIN"; add_header X-XSS-Protection "1; mode=block" always; add_header X-Content-Type-Options "nosniff" always; add_header Referrer-Policy no-referrer always; add_header X-Robots-Tag none; proxy_hide_header Upgrade; proxy_hide_header X-Powered-By; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_cache_bypass $http_upgrade; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme;

kerem commented

2026-02-26 06:34:38 +03:00

Author

Owner

@netstx commented on GitHub (Aug 26, 2022):

There's a warning about this right underneath the text box where you add these custom configs:

Please note, that any add_header or set_header directives added here will not be used by nginx. You will have to add a custom location '/' and add the header in the custom config there.

@netstx commented on GitHub (Aug 26, 2022): There's a warning about this right underneath the text box where you add these custom configs: ` Please note, that any add_header or set_header directives added here will not be used by nginx. You will have to add a custom location '/' and add the header in the custom config there.`

kerem commented

2026-02-26 06:34:38 +03:00

Author

Owner

@a18ccms commented on GitHub (Oct 25, 2022):

add a custom location '/' and add the header in the custom config :proxy_set_header Host $http_host;
web is 400 Bad Request

bash-5.1# pwd
/data/nginx/proxy_host
bash-5.1# cat 12.conf 
# ------------------------------------------------------------
# xxx.xxx.xxx
# ------------------------------------------------------------


server {
  set $forward_scheme http;
  set $server         "192.168.2.19";
  set $port           8806;

  listen 8080;
listen [::]:8080;

listen 4443 ssl http2;
listen [::]:4443 ssl http2;


  server_name xxx.xxx.xxx;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-3/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-3/privkey.pem;


proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


  access_log /data/logs/proxy-host-12_access.log proxy;
  error_log /data/logs/proxy-host-12_error.log warn;

  location / {
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto  $scheme;
    proxy_set_header X-Forwarded-For    $remote_addr;
    proxy_set_header X-Real-IP		$remote_addr;
    proxy_pass       http://192.168.2.19:8806;

    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    
    proxy_set_header Host $http_host;

  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

@a18ccms commented on GitHub (Oct 25, 2022): add a custom location '/' and add the header in the custom config :proxy_set_header Host $http_host; web is 400 Bad Request ``` bash-5.1# pwd /data/nginx/proxy_host bash-5.1# cat 12.conf # ------------------------------------------------------------ # xxx.xxx.xxx # ------------------------------------------------------------ server { set $forward_scheme http; set $server "192.168.2.19"; set $port 8806; listen 8080; listen [::]:8080; listen 4443 ssl http2; listen [::]:4443 ssl http2; server_name xxx.xxx.xxx; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-3/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-3/privkey.pem; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; access_log /data/logs/proxy-host-12_access.log proxy; error_log /data/logs/proxy-host-12_error.log warn; location / { proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://192.168.2.19:8806; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; proxy_set_header Host $http_host; } # Custom include /data/nginx/custom/server_proxy[.]conf; } ```

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@jschlatow commented on GitHub (Dec 29, 2022):

I have walked the same road when I just noticed that a possible solution has been suggested in #1477.

@jschlatow commented on GitHub (Dec 29, 2022): I have walked the same road when I just noticed that a possible solution has been suggested in #1477.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@GAS85 commented on GitHub (Feb 21, 2023):

Basically you have to edit /data/nginx/custom/server_proxy.conf that is designed for such a changes.
I agree that UI management should be add here. As also that those settings are common for all proxies that you will create.

P.S. you do not need to set add_header X-Frame-Options "SAMEORIGIN"; this could be managed via Docker Envs.

@GAS85 commented on GitHub (Feb 21, 2023): Basically you have to edit [`/data/nginx/custom/server_proxy.conf`](https://github.com/NginxProxyManager/nginx-proxy-manager/blob/b9a6b5d4f5a192d390c3695a464ef2b5991e0914/docs/advanced-config/README.md?plain=1#L155) that is designed for such a changes. I agree that UI management should be add here. As also that those settings are common for all proxies that you will create. P.S. you do not need to set `add_header X-Frame-Options "SAMEORIGIN";` this could be [managed via Docker Envs](https://github.com/NginxProxyManager/nginx-proxy-manager/blob/b9a6b5d4f5a192d390c3695a464ef2b5991e0914/docs/advanced-config/README.md#x-frame-options-header).

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 14, 2024):

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

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

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@GAS85 commented on GitHub (Mar 14, 2024):

👍

@GAS85 commented on GitHub (Mar 14, 2024): 👍

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@jschlatow commented on GitHub (Mar 14, 2024):

👍

@jschlatow commented on GitHub (Mar 14, 2024): :+1:

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@whc2001 commented on GitHub (Jul 6, 2024):

I think even adding the config into custom location won't work, since the directives will be added above the default config and get overriden

@whc2001 commented on GitHub (Jul 6, 2024): I think even adding the config into custom location won't work, since the directives will be added above the default config and get overriden ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/16266909/9ae20189-4fe3-482e-b4af-7d99feb4142f)

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@ConfidentKeyboard commented on GitHub (Oct 17, 2024):

I've tried everything here, and it still doesn't seem to work. On Unraid with nginx-proxy-manager-official. Any suggestions?

@ConfidentKeyboard commented on GitHub (Oct 17, 2024): I've tried everything here, and it still doesn't seem to work. On Unraid with nginx-proxy-manager-official. Any suggestions?

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@whc2001 commented on GitHub (Oct 17, 2024):

I've tried everything here, and it still doesn't seem to work. On Unraid with nginx-proxy-manager-official. Any suggestions?

Someone pushed a bugged commit which broke the behaviour of custom directions. You need to edit the config file in data dir and never touch the WebUI again.

@whc2001 commented on GitHub (Oct 17, 2024): > I've tried everything here, and it still doesn't seem to work. On Unraid with nginx-proxy-manager-official. Any suggestions? Someone pushed a bugged commit which broke the behaviour of custom directions. You need to edit the config file in data dir and never touch the WebUI again.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@ConfidentKeyboard commented on GitHub (Oct 17, 2024):

I've tried everything here, and it still doesn't seem to work. On Unraid with nginx-proxy-manager-official. Any suggestions?

Someone pushed a bugged commit which broke the behaviour of custom directions. You need to edit the config file in data dir and never touch the WebUI again.

I assume an update would then overwrite any changes I make as well?

@ConfidentKeyboard commented on GitHub (Oct 17, 2024): > > I've tried everything here, and it still doesn't seem to work. On Unraid with nginx-proxy-manager-official. Any suggestions? > > Someone pushed a bugged commit which broke the behaviour of custom directions. You need to edit the config file in data dir and never touch the WebUI again. I assume an update would then overwrite any changes I make as well?

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 26, 2025):

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

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

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@GAS85 commented on GitHub (Apr 30, 2025):

👍

@GAS85 commented on GitHub (Apr 30, 2025): 👍

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@gazanfarus commented on GitHub (Jun 11, 2025):

any updates?

@gazanfarus commented on GitHub (Jun 11, 2025): any updates?

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@spansu commented on GitHub (Jul 17, 2025):

i have workaround

/data/nginx/custom/http_top.conf

map $host $my_host {
    default $host;
}

mount custom /etc/nginx/conf.d/include/proxy.conf

volumes:
      - ./data:/data
      - ./data/nginx/custom/_proxy.conf:/etc/nginx/conf.d/include/proxy.conf
      - ./letsencrypt:/etc/letsencrypt

./data/nginx/custom/_proxy.conf
with content

add_header       X-Served-By $host;
proxy_set_header Host $my_host;
proxy_set_header X-Forwarded-Scheme $scheme;
proxy_set_header X-Forwarded-Proto  $scheme;
proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP          $remote_addr;
proxy_pass       $forward_scheme://$server:$port$request_uri;

in advanced settings of proxy_host add
where you need it

set $my_host example.co;

@spansu commented on GitHub (Jul 17, 2025): i have workaround 1) /data/nginx/custom/http_top.conf ``` map $host $my_host { default $host; } ``` 2) mount custom /etc/nginx/conf.d/include/proxy.conf ``` volumes: - ./data:/data - ./data/nginx/custom/_proxy.conf:/etc/nginx/conf.d/include/proxy.conf - ./letsencrypt:/etc/letsencrypt ``` ./data/nginx/custom/_proxy.conf with content ``` add_header X-Served-By $host; proxy_set_header Host $my_host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_pass $forward_scheme://$server:$port$request_uri; ``` 3) in advanced settings of proxy_host add where you need it ``` set $my_host example.co; ```

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@maxpowernz commented on GitHub (Aug 10, 2025):

Thought I would give NPM a try, mucked around with the other flaky settings then this comes up, pass for me. I don't get why so many people use and recommend it, it actually makes things harder.

@maxpowernz commented on GitHub (Aug 10, 2025): Thought I would give NPM a try, mucked around with the other flaky settings then this comes up, pass for me. I don't get why so many people use and recommend it, it actually makes things harder.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@whc2001 commented on GitHub (Aug 11, 2025):

Thought I would give NPM a try, mucked around with the other flaky settings then this comes up, pass for me. I don't get why so many people use and recommend it, it actually makes things harder.

The only reason I use it before is because the WebUI. I switched to Caddy and never looked back as I need to edit config directly nevertheless because the bug.

@whc2001 commented on GitHub (Aug 11, 2025): > Thought I would give NPM a try, mucked around with the other flaky settings then this comes up, pass for me. I don't get why so many people use and recommend it, it actually makes things harder. The only reason I use it before is because the WebUI. I switched to Caddy and never looked back as I need to edit config directly nevertheless because the bug.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@felipewnp commented on GitHub (Aug 21, 2025):

It's really sad that a problem like this is still around since 2021.

It's been over 4 years. It was very needed then, and still is now.

@jc21 How can we help? Could you point us to where the problem should/could be?

I don't know anything about JavaScript, but maybe I/we can try something.

@felipewnp commented on GitHub (Aug 21, 2025): It's really sad that a problem like this is still around since 2021. It's been over 4 years. It was very needed then, and still is now. @jc21 How can we help? Could you point us to where the problem should/could be? I don't know anything about JavaScript, but maybe I/we can try something.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@gudge25 commented on GitHub (Aug 27, 2025):

👍

i done it by commenting in conf file but it is a temporary solution

proxy_ssl_server_name on;
proxy_ssl_name ipv4.cloudns.net;
proxy_set_header Host ipv4.cloudns.net;

    # proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto  $scheme;
    proxy_set_header X-Forwarded-For    $remote_addr;
    proxy_set_header X-Real-IP          $remote_addr;

@gudge25 commented on GitHub (Aug 27, 2025): 👍 i done it by commenting in conf file but it is a temporary solution ``` proxy_ssl_server_name on; proxy_ssl_name ipv4.cloudns.net; proxy_set_header Host ipv4.cloudns.net; # proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Real-IP $remote_addr; ```

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@Janhouse commented on GitHub (Sep 13, 2025):

i done it by commenting in conf file but it is a temporary solution

Nothing temporary about it, this issue has been open since 2021.

To be honest, I'm not even sure why would you use the nginx-proxy-manager in the first place in 2025 if such a basic thing requires mounting custom config files. Might as well just configure nginx from scratch without the limited UI bloat. Especially now when Nginx supports acme for certificate retrieval natively.

@Janhouse commented on GitHub (Sep 13, 2025): > > i done it by commenting in conf file but it is a temporary solution > Nothing temporary about it, this issue has been open since 2021. To be honest, I'm not even sure why would you use the nginx-proxy-manager in the first place in 2025 if such a basic thing requires mounting custom config files. Might as well just configure nginx from scratch without the limited UI bloat. Especially now when Nginx supports acme for certificate retrieval natively.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@GrahamJenkins commented on GitHub (Oct 23, 2025):

I could have sworn I was able to do this in the past. Here's my experience:

I need to set some headers. I can do that under the advanced nginx settings tab, easy peasy.
Oh, I'm not allowed to because they'll be ignored. That's...annoying. I don't like messing with custom locations. But whatever, I just have to do it once and things will work.
I create a custom location for / and can add the settings. It also wants an ip/port. So...I guess I copy the same ip/port I'm proxying. Right....I think? This is exactly why I don't mess with custom locations. But since they're mandatory, sure. I'll add them.
And now nothing works.

400 Bad Request

Your browser sent a request that this server could not understand.

If I remove the custom location it works again, but no headers. If I can't handle these things inside npm easily via the GUI, I don't know why I'm even using it at this point, said as someone who has used it for more years than I can recall, because it's cleaner than hand mangling config files.

I don't know what caused this regression or why we can no longer be trusted to handle headers in the advanced section (I'm fairly certain I have done that in the past before "Enable websockets" was a feature) but this needs to be fixed. Not to be overly critical of open source software, but this feels like a significant regression/bug under the guise of a feature somewhere.

@GrahamJenkins commented on GitHub (Oct 23, 2025): I could have sworn I was able to do this in the past. Here's my experience: 1. I need to set some headers. I can do that under the advanced nginx settings tab, easy peasy. 2. Oh, I'm not allowed to because they'll be ignored. That's...annoying. I don't like messing with custom locations. But whatever, I just have to do it once and things will work. 3. I create a custom location for / and can add the settings. It also wants an ip/port. So...I guess I copy the same ip/port I'm proxying. Right....I think? This is exactly why I don't mess with custom locations. But since they're mandatory, sure. I'll add them. 4. And now nothing works. # 400 Bad Request Your browser sent a request that this server could not understand. If I remove the custom location it works again, but no headers. If I can't handle these things inside npm easily via the GUI, I don't know why I'm even using it at this point, said as someone who has used it for more years than I can recall, _because_ it's cleaner than hand mangling config files. I don't know what caused this regression or why we can no longer be trusted to handle headers in the advanced section (I'm fairly certain I have done that in the past before "Enable websockets" was a feature) but this needs to be fixed. Not to be overly critical of open source software, but this feels like a significant regression/bug under the guise of a feature somewhere.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@felipewnp commented on GitHub (Oct 24, 2025):

Not to be overly critical of open source software, but this feels like a significant regression/bug under the guise of a feature somewhere.

Don't bother, this project died long ago.

I'm going to try traefik or something else to replace npm.

Open to suggestions.

Maybe we can start a how-to move away from npm and what your options are.

@felipewnp commented on GitHub (Oct 24, 2025): > Not to be overly critical of open source software, but this feels like a significant regression/bug under the guise of a feature somewhere. Don't bother, this project died long ago. I'm going to try traefik or something else to replace npm. Open to suggestions. Maybe we can start a how-to move away from npm and what your options are.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@gudge25 commented on GitHub (Oct 24, 2025):

Not to be overly critical of open source software, but this feels like a significant regression/bug under the guise of a feature somewhere.

Don't bother, this project died long ago.

I'm going to try traefik or something else to replace npm.

Open to suggestions.

Maybe we can start a how-to move away from npm and what your options are.

i noticed there are forks like https://github.com/ZoeyVid/NPMplus

@gudge25 commented on GitHub (Oct 24, 2025): > > Not to be overly critical of open source software, but this feels like a significant regression/bug under the guise of a feature somewhere. > > Don't bother, this project died long ago. > > I'm going to try traefik or something else to replace npm. > > Open to suggestions. > > Maybe we can start a how-to move away from npm and what your options are. i noticed there are forks like https://github.com/ZoeyVid/NPMplus

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@felipewnp commented on GitHub (Oct 24, 2025):

I will absolutely try it out this weekend!

Thanks!

Em sex., 24 de out. de 2025, 09:59, Anton @.***>
escreveu:

gudge25 left a comment (NginxProxyManager/nginx-proxy-manager#1003)
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1003#issuecomment-3443042342

Not to be overly critical of open source software, but this feels like a
significant regression/bug under the guise of a feature somewhere.

Don't bother, this project died long ago.

I'm going to try traefik or something else to replace npm.

Open to suggestions.

Maybe we can start a how-to move away from npm and what your options are.

i noticed there are forks like https://github.com/ZoeyVid/NPMplus

—
Reply to this email directly, view it on GitHub
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1003#issuecomment-3443042342,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEQPKWCGM4S3H4GWFDOH433ZIPETAVCNFSM6AAAAAB343HRTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBTGA2DEMZUGI
.
You are receiving this because you commented.Message ID:
@.***>

@felipewnp commented on GitHub (Oct 24, 2025): I will absolutely try it out this weekend! Thanks! Em sex., 24 de out. de 2025, 09:59, Anton ***@***.***> escreveu: > *gudge25* left a comment (NginxProxyManager/nginx-proxy-manager#1003) > <https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1003#issuecomment-3443042342> > > Not to be overly critical of open source software, but this feels like a > significant regression/bug under the guise of a feature somewhere. > > Don't bother, this project died long ago. > > I'm going to try traefik or something else to replace npm. > > Open to suggestions. > > Maybe we can start a how-to move away from npm and what your options are. > > i noticed there are forks like https://github.com/ZoeyVid/NPMplus > > — > Reply to this email directly, view it on GitHub > <https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1003#issuecomment-3443042342>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIEQPKWCGM4S3H4GWFDOH433ZIPETAVCNFSM6AAAAAB343HRTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBTGA2DEMZUGI> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@Janhouse commented on GitHub (Oct 24, 2025):

I am working on something similar for Traefik. The purpose is slightly different but the result is similar. https://github.com/Janhouse/traefik-proxy-admin
It's a bit early development there and I don't have the easy setup (docker compose up) ready yet, because I use it with my existing Traefik instance, but that could be done rather quickly.

@Janhouse commented on GitHub (Oct 24, 2025): I am working on something similar for Traefik. The purpose is slightly different but the result is similar. https://github.com/Janhouse/traefik-proxy-admin It's a bit early development there and I don't have the easy setup (docker compose up) ready yet, because I use it with my existing Traefik instance, but that could be done rather quickly.

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@Stejsi commented on GitHub (Nov 4, 2025):

Same issue here. I cant rewrite Host in advanced tab & not even location tab.
v2.13.0 just have been released https://github.com/NginxProxyManager/nginx-proxy-manager/releases
but they said "No changes to Nginx/Openresty". Any thoughts?

@Stejsi commented on GitHub (Nov 4, 2025): Same issue here. I cant rewrite Host in advanced tab & not even location tab. v2.13.0 just have been released https://github.com/NginxProxyManager/nginx-proxy-manager/releases but they said "No changes to Nginx/Openresty". Any thoughts?

kerem commented

2026-02-26 06:34:39 +03:00

Author

Owner

@felipewnp commented on GitHub (Nov 4, 2025):

Same issue here. I cant rewrite Host in advanced tab & not even location tab. v2.13.0 just have been released https://github.com/NginxProxyManager/nginx-proxy-manager/releases but they said "No changes to Nginx/Openresty". Any thoughts?

nginxProxyManager plus (https://github.com/ZoeyVid/NPMplus) , suggested above, is a good solution.

But I recommend that you migrate your hosts manually from npm to npm-plus, because it deploys modsecurity automatically for each host.

And modsecurity eats RAM like crazy the way it is implemented on npm-plus.

@felipewnp commented on GitHub (Nov 4, 2025): > Same issue here. I cant rewrite Host in advanced tab & not even location tab. v2.13.0 just have been released https://github.com/NginxProxyManager/nginx-proxy-manager/releases but they said "No changes to Nginx/Openresty". Any thoughts? nginxProxyManager plus (https://github.com/ZoeyVid/NPMplus) , suggested above, is a good solution. But I recommend that you migrate your hosts manually from npm to npm-plus, because it deploys modsecurity automatically for each host. And modsecurity eats RAM like crazy the way it is implemented on npm-plus.

Rows
Columns

[GH-ISSUE #1003] Custom Nginx Configuration - proxy_set_header Host #841

400 Bad Request