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

Give a user full home directory access

B

Brayden

Guest
Hi,

Just wondering if anyone can help me out here.

When a domain is created in Plesk and the user is given shell access, the home directory for that domain is /var/www/vhosts/domainName

The user account associated with the account/domain is given write access to /var/www/vhosts/domainName/httpdocs as it is owned by them, but they are not given full access to /var/www/vhosts/domainName as it appears to be owned by "root"/

Is there a way when creating a shell account for a user that they can be given full, complete access to /var/www/vhosts/domainName and all sub-directories to be able to edit files in there?

Thanks in advance!

Brayden
 
anon_ftp, cgi-bin, httpdocs, httpsdocs and private should be owned by that ftp user. Not sure why everything is owned by root.

You can always chown the directory from the SSH consol

chown username: psaserv -R httpdocs/

Should do the trick
 
No I need to know why the "home" directory is owned by root and not the user, not the httpdocs directory. :)

TIA,

Brayden :)
 
That's just how plesk is. If you don't like it. Just chown everything to the user under the home directory. Problem solved.
 
Perhaps it has to do with normal users not modifying vhost.conf, screwing up directory structure, removing logs, etc... Unless ofcourse you like them overriding stuff...
 
Sure hope you understand the risks n such...

Those rights aren't there for nothing you know, somebody (probably more knowledgable than us) has put thought in that. For example there is a conf directory in there that will pretty much allow to override any apache/php configuration there is. They might as well use vhost.conf to configure 90 other domains and never pay for them.
 
Back
Top