• 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.

Recent content by SinišaB

  1. S

    HTTP logs for mailman access

    Found it: /var/log/apache2/other_vhosts_access.log Thank you, IgorG!
  2. S

    HTTP logs for mailman access

    Hello! I was unable to find the HTTP log in which the access to the mailman web interface is logged. Looking into the apache VirtualHost and ServerNAme "list" in /etc/apache2/plesk.conf.d/server.conf, I see there are no log definitions at all. Can someone please help? Thank you!
  3. S

    Ban IP after X login attempts

    We need to be able to lock out an IP after certain number of failed login attempts for any user, not just for those with admin privileges. Current mechanism restricts admin access only, but leaves customers' accounts open to password guessing attacks.
  4. S

    Ban IP after X login attempts

    Hello, IgorG, and thanks for replying. Unfortunately, restricting the panel access statically by IP is not an option in many cases. Customers could be .. well.. anywhere. :) I've already heard about future fail2ban integration, I just hope it won't mess up already working f2b installations...
  5. S

    Ban IP after X login attempts

    It's unbelievable Plesk still doesn't have a mechanism to protect itself from brute-force login attacks! While we are waiting for authors to make it available as an option in the Admin panel, here's how I do it: Have a look at database "psa", table "log_actions". Plesk logs failed logins...
See more
Back
Top