mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #734] Fail2Ban #622
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#622
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 @Trrw on GitHub (Nov 20, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/734
Hello,
can you add Fail2Ban?
Thanks you!
@F-0PS commented on GitHub (Nov 24, 2020):
I would also like to vote for adding this when your bandwidth allows. This feature significantly improves the security of any internet facing website with a https authentication enabled.
@Danie10 commented on GitHub (Dec 15, 2020):
Yes fail2ban would be the cherry on the top!
@crazybadger commented on GitHub (Dec 16, 2020):
How would fail2ban work on a reverse proxy server? Isn't that just directing traffic to the appropriate service, which then handles any authentication and rejection?
@Rustymage commented on GitHub (Jan 12, 2021):
Unless you could parse the logs downstream at each service and update the list of banned IPs for npm to block upstream.
Edit: https://github.com/jc21/nginx-proxy-manager/issues/39#issuecomment-564297645
@chaptergy commented on GitHub (May 12, 2021):
Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/39