• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

Issue Restrict access to files and directories randomly reverts to disabled

SDGPete

Basic Pleskian
Server operating system version
AlmaLinux 9.7 (Moss Jungle Cat)
Plesk version and microupdate number
Plesk Obsidian 18.0.74 Update #3
Hi,

I keep noticing that "Restrict access to files and directories" within Security Measures randomly reverts back to being disabled. I think it's in connection with auto-updates, I can see that 2 plugins were updated (presumably the protection is disabled for the update) but it wasn't reinstated after. This doesn't always happen but when it does there's no notification to say that it couldn't be applied and then leaves it vulnerable and easier to compromise (if plugins are found to have vulnerabilities).

Does anyone know of a way to prevent this or at the very least to notify when this happens?
 
Hi, @SDGPete . It is likely that some WordPress plugin automatically updates file/folder permissions that differ from the default permissions that are expected by WP-Toolkit. Please temporarily enable Plesk debug mode and check /var/log/plesk/panel.log when the issue reappears. The log entry should be similar to:

Code:
stderr: Incorrect permissions on /var/www/vhosts/example.com/httpdocs/wp-content/cache/wpo-minify/1622487907/assets/wpo-minify-header-b6715801.min.css.gz: expected is one of 00, 04, 040, 044, 0200, 0204, 0240, 0244, 0400, 0404, 0440, 0444, 0600, 0604, 0640, 0644, actual is 0755

It should help you identify which plugin is performing the change.
 
Back
Top