• 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 permissions issue - possible glitch in #plesk repair fs ?

TomBoB

Silver Pleskian
Hi all,

long story, let me try to make it short. (sorry nearly forgot: CentOS 7.4.1708, Plesk 17.5#44

Read Service Vulnerabilities: 3 Hosting Companies Fix NFS Permissions Problem and Service Vulnerability: MelbourneIT Fixes NFS Permissions Problem and wanted to double-check and make sure that our servers as protected.

[ for reference, Virtual Host Structure (Linux) is how Plesk Onyx likes its permissions ]

What i found:

vhosts - 755 - ok

clientdomains
some 755 - not ok
most 710 - ok

before starting to repair I checked the httpdocs folders permissions within the clientdomains folders:
all clientdomain folders with 755, httpdocs also 755 - not ok
some clientdomain folders with 710, httpdocs 750 - ok
other clientdomain folders with 710, httpdocs 755 - not ok

All right, ran the general
Code:
plesk repair fs
to the rescue.

All clientdomains 710 now. - great

When checking the httpdocs folders however, the permissions had not changed to 750 but remained 755 for those who previously had 755.

To test I tried the more specific
Code:
plesk repair fs clientdomain.com
on a clientdomain that still had the 755 permission on the httpsdocs folder... It stayed 755 instead of changing to the proper 750.

---
Glitch in the command execution?
As per both Plesk and Wordfence, 750 is definitely correct as there shouldn't be a traversable permission set on that folder.
---

Anyone experienced the same / similar ?
Sorry, permissions issues that deep down is something close to the limit of my current knowledge...

Cheers,
Tom
 
Back
Top