mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #622] Option to enable 444 on default site and access list #525
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#525
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 @axiom00 on GitHub (Oct 1, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/622
Would it be possible to add a fifth option on the default site configuration to return 444 connection dropped? Also nice to have the 444 option as a toggle in the access list Deny All rule instead of the current 403.
Thanks.
@brtwrst commented on GitHub (Jul 24, 2021):
I have the same "Issue"/Wish.
You can work around it a little bit.
404 Pageas Default Site[npm_data_volume]/nginx/default_host/site.confand change the 404 to 444 in that file.This change will persist until you select a new option for the Default Site.
@webartifex commented on GitHub (Mar 19, 2022):
Just saw this issue and want to encourage that the above suggestions become features eventually.
I work with the exact same fixes, but having them as GUI options for not so "tech" savvy people would probably be great.
@LaazV commented on GitHub (Mar 24, 2022):
Yes, please! Been wanting this for a while since I'm using a wildcard dns entry, and don't want the server responding to any subdomain.
Maybe even a 6th option "Custom Nginx Configuration" to allow for other edge cases when needed.
@KGBist2000 commented on GitHub (Feb 4, 2023):
yes please, return code 444 is much safer, than 404.
One of the usecase is when somebody try to connect via IP and not via hostname/domainname to close the connection by 444 and do not return any information about the server.
@tomassanjuann commented on GitHub (Apr 26, 2023):
Up for this. Custom HTTP codes are an improvement in my opinion.
@github-actions[bot] commented on GitHub (Mar 25, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@frenzis01 commented on GitHub (Dec 2, 2024):
If i got it right this works for the default page, is there any workaround to avoid responding at all (yielding 444 instead of 403) when the client does not match the access list?
@github-actions[bot] commented on GitHub (Jun 21, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@webartifex commented on GitHub (Jun 21, 2025):
Still waiting for it :)
@sym0nd0 commented on GitHub (Jun 24, 2025):
You'd probably be better to migrate over to NPMplus and request this change there, as this project has been pretty much abandoned for years. NPMplus is under active development and has a lot of QoL features missing from the original it was forked from.
@github-actions[bot] commented on GitHub (Jan 30, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍