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

Multiple FTP Accounts

CSN-Carl

Basic Pleskian
Please add support for multiple FTP accounts on domains, this has been requested by many people over the last few years but this feature is still not available in Plesk 9.0.
 
Parallels claims that this would take a huge architectural change but how difficult is it for them to write the code to add the users to /etc/passwd? I mean really?

Besides someone else has written the code for this on his own time once, which contradicts the Parallels explanation. And yes, cPanel has supported this feature for many years...
 
This really is a permissions issue in Plesk more than anything else.

When a user is created in cpanel that user is given a unique UID (user id) and GID (group id). So to have more than one user access the same webspace is a trivial matter of creating a user in passwd and then assigning the user to the same GID as the master account. This makes security enforcement very simple as you know that for a given account (say user foo) there is a unique GID called 'foo' that you can add each additional user to and maintain proper security and restrict that users permissions accordingly. So you can set your security policy at the group level which is a wider area and still maintain control. This allows a many to one relationship for a given account.

In Plesk things are very different. For any given user there is only a unique UID with a commonly shared GID (psacln). This poses some rather difficult security issues as you no longer have the ease of enforcing security restrictions at the group level, since all users are in the same group. This forces a one to one relationship between the user and a given domain.

So this isn't as simple as you make it seem, but only for reasons that are not immediately apparent unless you look deeper into the linux security model and the decisions based on how Plesk does things versus how cpanel does things.
 
Back
Top