Article ID: 115587, created on Jun 25, 2013, last review on Aug 12, 2014

  • Applies to:
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix

Contents

Problem:

Web server configuration fails for websites and reconfiguring does not help. The reason of failure is unclear and it is impossible to troubleshoot it.

Solution:

To find out why the web server configuration failed, do the following:
  • On Parallels Plesk Panel 11.x installations, use a special troubleshooting extension, which, when installed, is available from the Panel.
  • On Parallels Plesk Panel 10.4 installations, use a command-line tool as described further in this article.
These tools, prepared by Plesk engineers and Plesk Service team, are based on their troubleshooting experience and are intended to assist administrators with troubleshooting.
Feel free to leave your feedback on this tool in the special thread on the Parallels Forum.

Obtaining and Installing the Extension:

You can obtain and install the extension by either of the following ways:

By issuing the following command in the console:

# wget http://autoinstall.plesk.com/extensions/packages/configs-1.0-1.zip
# /usr/local/psa/bin/extension --install configs-1.0-1.zip
The extension was successfully installed.

By using the Panel user interface:

1. Download the extension from http://autoinstall.plesk.com/extensions/packages/configs-1.0-1.zip
2. Log in to the Panel as administrator.
3. Go to Extensions > Add Extension.

4. Select and upload the file you obtained on step 1.

Using the Extension:

Use this extension when you encounter the following errors in Panel:
“New files of configuration for Apache web server were not built due to errors in configuration templates”

1. Go to Extensions > Web Server Configurations Troubleshooter. The Configurations tab shows a list of all configuration files generated by Plesk Panel and indicates their status (“ok” or “error”).



2. Filter out faulty configurations by clicking the Show Errors button. This will help you determine the sites for which generation of configuration files failed.

Here you can also go to the corresponding subscription using links in the Belongs To column.

3. To check whether there are known issues related to the generation of web server configuration files, go to the Checker tab.

When you go to this tab, it starts a script which detects the most frequent issues related to the regeneration of web server configuration files. For every detected issue the script shows a link to the KB article which describes how to solve it.



4. Visit the suggested articles in the Parallels Knowledge Base and try to apply the solutions from the articles.

If the suggested solutions do not help, try to find error messages indicating the failure reasons.

5. Search for error messages in the Panel’s and web servers’ logs. To do this, go to the Bootstraps tab.

It lists all bootstrapper files, which are configuration files that contain directives for loading other bootstrappers or domain configuration files.


On this tab, you can view the contents of the bootstrappers or search in the log files for references to them. This can be useful because when a web server validates a configuration file, it refers in the error messages not to the faulty configuration file, but to the bootstrapper that includes it.

6. Click the link Search in log files next to each file path. (To return to the Bootstraps tab, use the browser’s Back button.)

If an error was found, try to determine the cause of the error by looking at the error message, or use an online search in the Plesk Troubleshooters service to find a knowledge base article by the error message.
You can also search for the problem description and solution on the Parallels Forum or using your favorite search engine.

7. If you did not find any errors, try using the Logs Search tab to search for error messages in log files.


For example, you can search for the most common errors by typing any of these words: fail, denied, No such, error.

Searching by these words is also performed in the Panel’s log files. For this reason, a huge number of search results may be displayed, and the results might not be related to the issues with regenerating web server configuration files. However, by making such a search, you can reveal issues with malformed additional configuration directives for custom per-site PHP settings:

2013-04-19T13:56:06+07:00 ERR (3): phpinimng failed: Cannot parse php.ini: (<class 'ConfigParser.ParsingError'>, File contains parsing errors: <stdin> [line 11]: 'mbstring.substitute_character ""\n')



If an error was found, try to determine the cause of the error by looking at the error message, or use an online search in the Plesk Troubleshooters service to find a knowledge base article by the error message.
You can also search for the problem description and solution on the Parallels Forum or using your favorite search engine.

Using the Command-Line Utility to Check for Known Issues:

In addition to the extension available in the user interface, there is also a command-line tool called webserver_configuration_checker.php.
It performs the same operations as the Checker tab of the Web Server Configurations Troubleshooter, but it can be downloaded and run from the console by means of the following commands:
# wget http://kb.sp.parallels.com/Attachments/23693/Attachments/webserver_configuration_checker.php
# /usr/local/psa/bin/sw-engine-pleskrun webserver_configuration_checker.php

Additional information

The utility can detect the following known issues:

http://kb.sp.parallels.com/113210  Web server reconfiguration fails with error: "JkWorkersFile only allowed once"
http://kb.sp.parallels.com/113475  Unable to manage domains with "Forwarding" hosting type
http://kb.sp.parallels.com/113826  Parallels Plesk Panel generates empty domain-level Apache config files due to corrupted records in Parallels Plesk Panel database
http://kb.sp.parallels.com/112815  Reference between several subscriptions and APS applications has been broken
http://kb.sp.parallels.com/1520  Wrong order of loading Zend extensions/ionCube declaration in php.ini can cause to Apache fail
http://kb.sp.parallels.com/114556  Webserver (Apache/Nginx) configs regeneration fails because files with the same names as the Apache symlinks you are trying to create already exist
http://kb.sp.parallels.com/113490  Apache configs regeneration fails if vHost directories or system users are missing
http://kb.sp.parallels.com/115012  Apache fails to regenerate its configuration files due to incorrect vhosts_bootstrap.conf files
http://kb.sp.parallels.com/115420  Database records with empty "Name" field in Configurations table cause a fatal PHP error during Apache reconfiguration
http://kb.sp.parallels.com/115299  Webserver reconfiguration fails with "Permission denied" error when SELinux is in enforced mode
http://kb.sp.parallels.com/115139  If there are more than 256 domains, Nginx fails with "Too many open files" error

Attachments

56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f 01bc4c8cf5b7f01f815a7ada004154a2 aea4cd7bfd353ad7a1341a257ad4724a e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7

Email subscription for changes to this article