• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

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