mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #3704] NPM passes through some requests even though 444 option is set #2443
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#2443
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 @ericswpark on GitHub (Apr 16, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3704
Checklist
jc21/nginx-proxy-manager:latestdocker image?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_HOSTis set (the server IP instead of the proxy hostname).Nginx Proxy Manager Version
v2.11.1
To Reproduce
Steps to reproduce the behavior:
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_HOSTheader set to the server's IP address instead of the correct hostname I set while setting up the proxy host in NPM.@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.
@ericswpark commented on GitHub (May 2, 2024):
@h4de5 nope, root (
/) with no files.@ericswpark commented on GitHub (Jun 4, 2024):
This occurred due to a Docker Compose misconfiguration; not an NPM issue. Sorry!