• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

password protecting your httpdocs directory

I

ilustrate

Guest
i would like to restrict access to everyone on my httpdocs directory until i finish will all my changes. therefore for customer viewing purposes i would like to password protect httpdocs. how would i protect this directory? i have noticed that if i type in httpdocs in the password protect feature in plesk that it actually creates a new httpdocs directory within httpdocs..... this should be very simple but the field has a / and if i remove the diagonal bar then i wouldn't have anything in this required field. Any suggestions?
 
Just did a quick test, seems like no matter what user's I define, the only user who can actually be authenticated is the domain admin. All other users I create in the protected dir area are not being recognized.....

It does protect the docroot. Had to restart apache manually though (minor bug?)

Try using the domain admin username and password.
 
Back
Top