[GH-ISSUE #3704] NPM passes through some requests even though 444 option is set #2443

Closed
opened 2026-02-26 07:35:35 +03:00 by kerem · 3 comments
Owner

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

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 running NPM with the default page option set to 444 (No Response), some requests still make it to proxied hosts, causing errors because the wrong HTTP_HOST is set (the server IP instead of the proxy hostname).

Nginx Proxy Manager Version

v2.11.1

To Reproduce
Steps to reproduce the behavior:

  1. Set up a proxy host
  2. Set default server behavior to 444
  3. Send requests to the server IP

Expected behavior

None of the requests should make it through to the proxied host

Additional context

This issue appears to be sporadic as I'm unable to reproduce it on-demand. However, I get errors from the proxied app behind NPM, telling me that requests are coming through with the HTTP_HOST header set to the server's IP address instead of the correct hostname I set while setting up the proxy host in NPM.

Originally created by @ericswpark on GitHub (Apr 16, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3704 **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** <!-- A clear and concise description of what the bug is. --> When running NPM with the default page option set to 444 (No Response), some requests still make it to proxied hosts, causing errors because the wrong `HTTP_HOST` is set (the server IP instead of the proxy hostname). **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.11.1 **To Reproduce** Steps to reproduce the behavior: 1. Set up a proxy host 2. Set default server behavior to 444 3. Send requests to the server IP **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> None of the requests should make it through to the proxied host **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> This issue appears to be sporadic as I'm unable to reproduce it on-demand. However, I get errors from the proxied app behind NPM, telling me that requests are coming through with the `HTTP_HOST` header set to the server's IP address instead of the correct hostname I set while setting up the proxy host in NPM.
kerem 2026-02-26 07:35:35 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

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

are those requests maybe related to static assets like .jpg, .css, .js or .woff files?

if so, there is a location rule in a include/assets.conf that takes precedence here.

<!-- gh-comment-id:2089643619 --> @h4de5 commented on GitHub (May 2, 2024): are those requests maybe related to static assets like .jpg, .css, .js or .woff files? if so, there is a location rule in a include/assets.conf that takes precedence here.
Author
Owner

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

@h4de5 nope, root (/) with no files.

<!-- gh-comment-id:2089751303 --> @ericswpark commented on GitHub (May 2, 2024): @h4de5 nope, root (`/`) with no files.
Author
Owner

@ericswpark commented on GitHub (Jun 4, 2024):

This occurred due to a Docker Compose misconfiguration; not an NPM issue. Sorry!

<!-- gh-comment-id:2147028199 --> @ericswpark commented on GitHub (Jun 4, 2024): This occurred due to a Docker Compose misconfiguration; not an NPM issue. Sorry!
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#2443
No description provided.