• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue fail2ban with asterisk

2N3055

New Pleskian
Dear all:
fail2ban is protecting our asterisk software fairly well. However, fail2ban issues warning mails informing it has banned a certain IP when in fact, the supposed banned IP is neither banned nor appears in any server log. Have you ever seen what I am describing? Is there any solution to that behavior? Your comments will be highly appreciated.
 
Dear all:
fail2ban is protecting our asterisk software fairly well. However, fail2ban issues warning mails informing it has banned a certain IP when in fact, the supposed banned IP is neither banned nor appears in any server log. Have you ever seen what I am describing? Is there any solution to that behavior? Your comments will be highly appreciated.
having the same issue.
 
Dear all:
fail2ban is protecting our asterisk software fairly well. However, fail2ban issues warning mails informing it has banned a certain IP when in fact, the supposed banned IP is neither banned nor appears in any server log. Have you ever seen what I am describing? Is there any solution to that behavior? Your comments will be highly appreciated.
and didn't find any response.
 
Back
Top