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

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