• 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 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