• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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