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

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