• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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