Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

Unable to start Apache on a Plesk server: No matches for the wildcard '*.conf' in

Avatar
Kuzma Ivanov
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

Apache web-server fails to start with the following error message in configuration:

Note: The name of the ModSecurity rule-set in the error message may vary.

  • on CentOS/RHEL-based distributions

    # httpd -t
    httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 5 of /etc/httpd/conf.d/security2.conf: Syntax error on line 6 of /etc/httpd/conf/modsecurity.d/zz_rules.conf: No matches for the wildcard '*.conf' in '/etc/httpd/conf/modsecurity.d/rules/modsecurity_crs-plesk', failing (use IncludeOptional if required)

  • on Debian/Ubuntu-based distributions:

    # apache2ctl -t
    apache2: Syntax error on line 141 of /etc/apache2/apache2.conf: Syntax error on line 4 of /etc/apache2/mods-enabled/security2.conf: Syntax error on line 6 of /etc/apache2/modsecurity.d/zz_rules.conf: No matches for the wildcard '*.conf' in
    '/etc/apache2/modsecurity.d/rules/tortix', failing (use IncludeOptional if required)

Cause

The ModSecurity configuration file zz_rules.conf contains links to non-existent files.

Resolution

 

For CentOS/RHEL-based distributions

 

  1. Connect to the Plesk server via SSH.

  2. Open the file zz_rules.conf in a text editor. In this example, we are using the vi editor:

    # vi /etc/httpd/conf/modsecurity.d/zz_rules.con

  3. Replace "Include" with "IncludeOptional" in all lines.

  4. Save the changes and close the file.

  5. Start Apache:

    # service httpd start

  6. Log in to Plesk > go to Tools & Settings > Web Application Firewall (ModSecurity) and activate ModSecurity.

 

For Debian/Ubuntu-based distributions

 

  1. Connect to the Plesk server via SSH.

  2. Open the file zz_rules.conf in a text editor. In this example, we are using the vi editor:

    • # vi /etc/apache2/modsecurity.d/zz_rules.conf

  3. Replace "Include" with "IncludeOptional" in all lines.

  4. Save the changes and close the file.

  5. Start Apache:

    # service apache2 start

  6. Log in to Plesk > go to Tools & Settings > Web Application Firewall (ModSecurity) and activate ModSecurity.

 

Comments

2 comments

Sort by Date Votes

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles