• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

HOWTO: Fix broken protected directories

hgtech@

New Pleskian
I ran into this problem on my Windows 2003 Server running Plesk 7.0.3. When I created a protected directory and user through Plesk, everything seemed to work fine. However, when I went to check the directory, it let me to the files - no request for credentials. I read a few posts on the forum where some of you guys had this problem last year without resolution.

After my recent run-in with this problem, I was able to resolve the issue per instructions from Plesk. It's actually quite easy to fix:

Login to your server (through rdp or vnc)
Open IIS Manager
Go to websites
Right click on the domain you need to enable protected directories for and go to properties
Select the ISAPI Filters tab
Add mapping.dll as a filter from c:\program files\swsoft\plesk\isapi
Close the properties
Restart the domain

Thats pretty much it. Like I said - easy - unless you have a ton of domains.
Note: Installing this filter at the server level as a global ISAPI filter will NOT work!!

- Matt
 
Back
Top