• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

cannot protect directories with Plesk 12.0.18 #52

Conny

New Pleskian
After I've upgraded Plesk 1.0.18 to latest version, I'm unable to set protection on directories. Plesk say it is set, but it is not. I can access protected directory without pop-up of login-details. Old protected directories work, but for new one added not working anymore. I also tried by conventional way adding .htaccess and .htpasswd files to the directory, but it does not apply either.
 
It was set to 0 (zero) as per default, and does not solve the problem. Something is very strange behaviour. If I create a new directory/folder and protect it, it works. If I add to this directory also other folders or files, than directory is not protected anymore. What I did: I added new folder with feature protect folder (and also tried to add it before and than protect it), copy than the content of another folder to this protected folder (cause I want to create a clone for software upgrade tests) and the folder is not protected anymore. The same, if I add the content to this protected directory via filezilla for ex. Protection is lost when I add something on this directory. It should be a bug.
 
Back
Top