• 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 Service apache down after update yum / Origin Modsecurity

Erwan

Regular Pleskian
Server operating system version
AlmaLinux 9.4
Plesk version and microupdate number
18.0.71
Hi all,
To begin with, we encountered this problem on three servers (out of six updated servers).

Problem: the Apache service went down after the following process:
- Update from Plesk 69 to 71 via the interface. All services then worked.
- System update using the command:
#yum makecache --refresh
Then:
#yum update

The process completed, but we then noticed that the Apache service was down.
After further investigation, it turned out that this was caused by Modsecurity.

When we want to restart Apache:
#systemctl restart httpd

We have this error:
httpd: Syntax error on line 358 of /etc/httpd/conf/httpd.conf: Syntax error on line 13 of /etc/httpd/conf.d/00_mod_security.conf: Include/IncludeOptional: No matches for the wildcard '00*

We tried to change Include by IncludeOptional...
But then we come across syntax problems:
AH00526: Syntax error on line 6035 of /etc/httpd/conf/modsecurity.d/rules/comodo_free/30_Apps_OtherApps.conf...
httpd[3591390]: Error creating rule: Error compiling pattern (offset 4): invalid range in character class...


We had to disable Modsecurity to be able to restart Apache.

Has anyone else encountered this issue or has a solution?
We have suspended updates in the meantime as the issue occurs on every other server.

Thank you.

Erwan
 
Hello,
We use Comodi (free) rules.

We solved the problem (or worked around it) by selecting execution by Nginx (Modsecurity 3) instead of Apache (Modsecurity 2.9).
 
Back
Top