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

Plesk Password Protected Directories - How Limit Login Attempts?

Angler

New Pleskian
Plesk 11.5.30 Update #47

When I look in a directory password protected by the Plesk Panel, I don't see an .htaccess file...

So, how does Plesk password protect directories?

And, is it possible to add functionality that would limit number of login attempts, and block an offending IP for a period of time?

Thank you in Advance!
 
As you can see in the "last.httpd.conf" - file ( or "last_ip_default.conf" - file ) at "/var/www/vhosts/system/YOURDOMAIN.COM/conf", Plesk uses the very same authentification as "normal" .htaccess - authentifications, just with the difference, that it is not named htaccess and the folder where the login - credential are saved, are not in the webroot - folder.
Code:
         <Directory "/var/www/vhosts/YOURDOMAIN.COM(/YOURSUBDOMAIN.COM)">
             AuthType Basic
             AuthName "YOUR_DESIRED_NAME_FOR_THE_LOGIN_SCREEN"
             AuthUserFile "/var/www/vhosts/system/YOURDOMAIN_OR_SUBDOMAIN.COM/pd/d..httpdocs"
             require valid-user
         </Directory>
Please be aware, that such authentifications do not work, if you use nginx to serve php - files as well ( at the moment ). In this case, you have to manually modify the "last.nginx.conf" with the necessary nginx definitions, because Parallels missed that untill now.

You could ban people with false login - attempts, using fail2ban. :)
 
Last edited by a moderator:
Back
Top