• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue IP Address Banning sort "IP adress" does not work properly

Azurel

Silver Pleskian
Page 1
First entry = 93.xx.xx.xx
Last entry = 45.xx.xx.xx

Page 3
First entry = 23.xx.xx.xx
Second entry = 219.xx.xx.xx
Last entry = 185.xx.xx.xx
 
Do you mean sorting the list of IP's by slimier IP address in Fail2Ban page is not functioning?
If that is the case and you're 100% sure, you can report that with more details in Reports

Please, click Post New Thread button and fill the form if you really believe you discovered a new bug and need to report it to the Plesk developers. It does allow us to handle and resolve your requests much more efficiently. Please be careful and do not submit any found problem with this template! Double check that it is really bug and you can reproduce it!
 
Probably 219.xx.xx.xx is a longer string than 93.xx.xx.xx, and 185.xx.xx.xx is even longer than the 219.xx.xx.xx.
It seems that the sort is not numeric, but alphabetical. In that case, short strings come first, longer strings come last.
 
Back
Top