• 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 IP(6)TABLES IPs count != Plesk Fail2ban IPs count

Azurel

Azurel

Silver Pleskian
I had very old ipsets in firewall-cmd and just deleted them. After a reload I looked at IPTABLES and saw that there are almost no entries, although my Fail2ban in Plesk has almost ~3000 entries.

Here seems to go somehow what with the time broken. Is there a way to synchronize the Plesk Fail2ban IPs back into IPTABLES/IP6TABLES? Under Fail2ban in Plesk is now displayed to me in any case almost only ips that not include in IPTABLES. Or remove Plesk Fail2ban IPs that not exists in IPTABLES/IP6TABLES anymore?
 
You must log in or register to reply here.

Similar threads

A
Question Fail2Ban capture and ban IP, connection still being made
Replies
8
Views
5K
Bitpalast
Bitpalast
G
Question Plesk Panel Extremely Slow and Shows White Screen Despite Server Resources Being Idle
Replies
2
Views
4K
HHawk
HHawk
JohnnyRobert
Issue VPS Server is stuck with the initial Domain Name
Replies
6
Views
7K
Armina
A
C
Issue Nginx Reverse Proxy IP
Replies
8
Views
4K
IgorG
IgorG
Mark12345
Question Blocking IP Ranges using Plesk Firewall or NGINX Deny
Replies
4
Views
6K
jose.alvarez
jose.alvarez
Back
Top