Facebook
Twitter-
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.
Resolved ModSecurity don't work
- Thread starter blackdoor
- Start date
I tried that workaround but it doesnt work. Looks like the issue is presistent for a year now.
This is Plesk bug with ID #PPPM-6202 which will be fixed in future updates.
I fixed the issue by doing
1. Find the current config:
bashgrep -r "SecDataDir" /etc/modsecurity/ /etc/apache2/ /etc/httpd/ 2>/dev/null
2. Create a new directory:
bashmkdir -p /var/cache/modsecurity
chown www-data:www-data /var/cache/modsecurity
chmod 770 /var/cache/modsecurity
3. Update SecDataDir in your ModSecurity config to:
SecDataDir /var/cache/modsecurity
If someone else has this issue:
Also, this error is present with the atomicorp full modsecurity ruleset
Message: Exec: Execution failed while reading output: /usr/bin/asl-stream-client (End of file found)
Message: Rule processing failed (id=351000, msg=Atomicorp.com Upload Malware Scanner: Malicious File upload attempt detected and blocked).
The rule is activated by default but the ASL scanner is not part of the modsecurity ruleset. That specific rule can be disabled, so no logs show up.
1. Find the current config:
bashgrep -r "SecDataDir" /etc/modsecurity/ /etc/apache2/ /etc/httpd/ 2>/dev/null
2. Create a new directory:
bashmkdir -p /var/cache/modsecurity
chown www-data:www-data /var/cache/modsecurity
chmod 770 /var/cache/modsecurity
3. Update SecDataDir in your ModSecurity config to:
SecDataDir /var/cache/modsecurity
If someone else has this issue:
Also, this error is present with the atomicorp full modsecurity ruleset
Message: Exec: Execution failed while reading output: /usr/bin/asl-stream-client (End of file found)
Message: Rule processing failed (id=351000, msg=Atomicorp.com Upload Malware Scanner: Malicious File upload attempt detected and blocked).
The rule is activated by default but the ASL scanner is not part of the modsecurity ruleset. That specific rule can be disabled, so no logs show up.
