• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Question about umask and file permission for domain

gennolo

Basic Pleskian
Hello,
I ask for help to understand this situation - Sorry for being long :D

I installed a domain with Prestashop 1.7 on a Plesk Onyx Centos 7 box with pretty standard settings
(PHP-FPM server by Apache - Php7 Plesk handler).
Domain is using its own user / webspace with the classic "psacln" group and files/folder with 644/755 permission.

It happens that when I try to add some new modules from the application backoffice
or when the application writes cache files
they are written with 666 permission for files and 777 for folders. This looks like totally insecure, and it never happened with other domains on the same host with different applications with the same domain setting, where I have the expected result (644 for files / 755 for folders).


I see lot of people are reporting this behaviour, and the answer was
"this is due to Symfony framework used in Prestashop 1.7 that uses server umask setting to set files/folder permission , so check / fix your envoriment because you have wrong umask".

I checked my server and #umask command (launched as root) is reporting 0022 that is supposed to be the correct setting to have 644 / 755 permission during uploads.

So my question is : am I missing something about umask or how Plesk is setting this value ?
Is there some umask setting I need to check at web-server user level or in Plesk domain configuration ?
Or is the application that needs to be fixed ?

Thank you !
 
Back
Top