• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

plesk installation file and dir owners

K

KamilG

Guest
Today I made the most stupid mistake

I used chown on a root account for whole home directory. All file owners on my debian 5.0 has changed to root:root. Even system files...

And everything because small space...


Is there a schema of correct permissions and user owners for plesk installation? I have managed to make correct user owners for all of my vhost but i dont know how to set up correct owners for opt/psa
 
I'm not sure about deb packages but you can reset the permissions of the all installed RPM packages

You need to use combination of rpm and a shell for loop command as follows:
for p in $(rpm -qa); do rpm --setperms $p; done
for p in $(rpm -qa); do rpm --setugids $p; done

Above command combination will reset all the permissions to the default permissions under CentOS / RHEL / Fedora Linux. Maybe you will find something similar for debs.
Also this article can be useful - http://kb.odin.com/en/6572
 
Thank You for Your answer. Unfortunately it doesnt work that way for debian, but I got everything running. Not sure though if there will be no errors in the future as I dont know plesk permissions schema...
 
Strange that deb hasn't something like setperms and setugids opitons as rpm.
I hope that all will work fine on your Plesk server.
 
reset the permissions

I accidentally recursively change permissions on their root filesystem (Centos 5) and have come across this thread. In my research there is a contradiction to the solution stated above. Permissions corrections enacted by –setperms will get blown away by subsequent u/g corrections enacted by –setugids. Therefore

Run

for p in $(rpm -qa); do rpm –setugids $p; done

before

for p in $(rpm -qa); do rpm –setperms $p; done

Getting the order correct, and combining this into a one-liner, we have:

for p in $(rpm -qa); do rpm –setugids $p; rpm –setperms $p; done

Hope this helps

Citation: http://www.cyberciti.biz/tips/reset-rhel-centos-fedora-package-file-permission.html
Also see: http://www.debian-administration.org/articles/476
 
Back
Top