• 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 protected directories unreliable

F

fastdrive

Guest
I've noted that the function to create password protected directories is working unreliably.
When creating new directories through Plesk, it is ok. But if I protect a directory that is already existing, it doesn't work or works with big delays.
Manually using .htaccess files locks the dirs immediately.
 
Plesk puts configuration for protected directories directly into the httpd.include file and not a .htaccess file. This means that the configuration won't take effect until httpd reloads (up to 15 mins with default Plesk setting). However, changes to the usernames and passwords on a directory that already has protection working should take effect immediately.

Force a manual reload by executing apachectl graceful at a root shell.
 
Back
Top