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

Question Plesk 12.5 protect with htaccess?

Hi Azurel,

are you sure, that your described issue is not based on browser-caching? Consider to test the authentification with another browser, or delete cached content for the domain in question in your browser. ;) If you restartet the "sw-cp-server" with your modifications, the suggestions from @MisterU still work as expected with Plesk 12.5 as well.
 
I will ask this again, because that protection maybe not protect anymore. Yes, the Auth-Box appear, but after x wrong login a get the plesk-login page and can submit it. Screenshot from Windows Edge. Here I never before used Plesk login and get this after x times with wrong Auth: http://fs5.directupload.net/images/161025/4zqe8wmc.png

And I get daily login errors in panel.log:
ERR [panel] [Action Log] Failed login attempt with login 'admin' from IP XX.XX.XX.XX

So I don't think that the old way from @MisterU here still correct works.
 
Back
Top