• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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