mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #601] Block common exploits funtion. #507
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#507
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 @investlab on GitHub (Sep 10, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/601
Hi there,
Can you tell me what's module did you build this funtion?
Thank you!
@mochman commented on GitHub (Sep 14, 2020):
It looks like when you enable that, block-exploits.conf is included.
@investlab commented on GitHub (Sep 14, 2020):
Thank you @mochman
I will custom this funtion using modsecurity.
@itsKV commented on GitHub (Aug 4, 2022):
And where can I find this block-exploits.conf file on host filesystem?
I couldn't find that conf.d folder mentioned in path of conf file.
@mochman commented on GitHub (Aug 4, 2022):
It's not on the host filesystem. It's located in the container filesystem at
/etc/nginx/conf.d/include/block-exploits.conf.You can get it on the host filesystem by creating a bind mount to the file directly.
@YurkinPark commented on GitHub (Nov 21, 2024):
btw, are there some addons which i can use to provide such options (like "Block common exploits") to be included in configuration (or managed externally) to let administrator specify user-agent or IP to block traffic from such client?