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

Issue Site's IIS Worker Process Group has less file permissions on subdomains than on parent domains

Joel Beazelman

New Pleskian
I created a subdomain beta.xyz.com under the parent domain xyx.com. After installing my ASP.NET Core application in the beta.xyz.com, I received write permission errors when accessing the App_Data. I discovered Plesk uses the same worker process group account, IWPG_xyz, for the parent site and subdomain, but it lacks modify permissions on httpdocs and its subfolders.

First, what's the reason for the different permissions? Is this a bug or is there another reason? Second, what's the best way to correct the permissions on the subdomain such that the permissions stay intact if I need to repair the permissions in the future, update the site, or migrate the files to another server. In the past, I've discovered nasty consequences from changing things behind Plesk's back.
 
Back
Top