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

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