• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

What are the fail2ban limits?

Linulex

Linulex

Silver Pleskian
Even on a server with "only" 175 domains, plesk gives the error:

"Warning: Fail2Ban might not work well if there are many domains and Fail2Ban has to monitor too many log files."

I have asked google but no one seems to know:
what are the limits of fail2ban?
how many is to many?
What will go wrong if the limit is reached? no more banning? wrong ip addresses banned?

regards
Jan
 
You must log in or register to reply here.

Similar threads

I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
3K
iainh
I
I
Forwarded to devs Postfix fail2ban filter misses authentication failures
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
F
Question Question regarding outgoing email limits
Replies
2
Views
3K
flex1
F
D
Issue Outgoing mail limit increase in UI didn't take effect — turned out to be a service plan sync bug (18.0.80)
Replies
3
Views
6K
Sebahat.hadzhi
Sebahat.hadzhi
O
Issue LogBrowser, Fail2ban and SASL filter
Replies
0
Views
2K
OverWolf
O
Back
Top