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

Question [discussion] what file permission strategy to follow?

Koen Verbruggen

Basic Pleskian
Ideally I would like to have every account have two users: 1 for FTP/SSH access, 1 to run apache.
Then, the first would be owner of files, the second part of group. Files would have 640 and folders 750.
Only upload folders would get 770 and underlaying files 660 so the webserver is able to write to those specific places only.

In plesk, fileowner is the FTP user and group is psaserv.
Files defaulting to 644, folders to 755. Although some Wordpress files get more restricted then others.

I will be looking for a way to set more tight permissions: no writing for apache/nginx except where I specifically want to. Wordpress can be updated using CLI (Wordpress Toolkit) without the need for apache to write.

What I am interested in: Do you leave these settings as is or change them to your preferences? And why?
 
Back
Top