• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Plesk Onyx keeps resetting permissions on a different drive

shall

Regular Pleskian
Whenever a micro-update is automatically installed by Plesk Onyx, it is resetting permissions on a different drive.

I understand the goal (security) of forcing psaadm and psacln to be denied rights outside their respective tree, but I need to be able to store a large media repository on another drive and I need Plesk to stop reverting my permissions changes within the mapped folder (a virtual directory).

How do I prevent Plesk Onyx from breaking this?

I have already disabled permissions propagation to the folder and (repeatedly) removed the psacln & psaadm users from the folder. Is there an option somewhere to tell Plesk to leave *this* folder alone?
 
Customizing Disk Security

Article describes case, when you have some web hosting software installed and you want psacln be able to access this software.
In your case you want Plesk just ignored such folder. So you should create file %plesk_dir%\etc\DiskSecurity\mapped_drive.xml, for example, with the following content:
Code:
<?xml version="1.0" encoding="utf-8" ?>
<Entries>
    <Entry AccounType="1" Account="Psacln" Path="D:\MappedLocation" AceFlags="ThisFolderSubfoldersAndFiles" AccessMask="NoAccess" EntryFlags="0" />
    <Entry AccounType="1" Account="Psaadm" Path="D:\MappedLocation" AceFlags="ThisFolderSubfoldersAndFiles" AccessMask="NoAccess" EntryFlags="0" />
</Entries>

In this case Plesk understands that there shouldn't be any rules for psaadm and psacln for your specified location, deletes ACE rules for that folder and wouldn't touch your folder anymore. (probably your directory will be touched only first time after you have created such file).
 
Back
Top