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

Directory Protection Bug? Plesk 7.5.4

J

jbrovont

Guest
I'm using v 7.5.4 on a linux RedHat install (I think) and there seems to be a problem with directory protection:

When I use the "Directories" page, I can create a new protected directory with no problem. However, using the "Directories" page to remove protection on a directory removes the entry from within Plesk's "Directories" interface, but the directory remains protected. I looked for .htaccess with an ftp client, but I didn't find one. I'm going to try a shell next.

Also, once directory protection has been enabled on the new directory, and trying to remove protection from within the control panel fails, even deleteing the directory, and then creating it again as a normal directory will not remove the protection.

Attempting to create directory protection on an existing directory fails.

Any ideas on a work-around for this, or what might be wrong?

Thanks in advance for any pointers! :D

~Jules
 
Back
Top