• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Issue AH01574 - New configuration files for the Apache web server - No matches for the wildcard '*asl*.conf

gmadkins

New Pleskian
Server operating system version
Ubuntu 22.* LTS
Plesk version and microupdate number
18.0.57
I can't seem to find any direct example of anyone else posting this error.

I use litespeed, and I think for others with similar issues this has taken down the apache front end loading but not for me, in my dashboard I have

New configuration files for the Apache web server were not created due to the errors in configuration templates: [Wed Jan 10 23:36:23.815943 2024] [so:warn] [pid 54187:tid 140198033958784] AH01574: module security2_module is already loaded, skipping [Wed Jan 10 23:36:23.815978 2024] [so:warn] [pid 54187:tid 140198033958784] AH01574: module unique_id_module is already loaded, skipping apache2_ls_bak: Syntax error on line 147 of /etc/apache2/apache2.conf: Syntax error on line 12 of /etc/apache2/mods-enabled/security2.conf: Include/IncludeOptional: No matches for the wildcard '*asl*.conf' in '/etc/httpd/modsecurity.d', failing. Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files. See the details in Configuration Troubleshooter

I have tried running both "generate broken configuration files" and "generate all configuration files" with no success.

I don't even use the built in mod_security rulesets, Imunify360 places a custom rulset in. It has been working this way for ages.

Any ideas?
 
Back
Top