- Plesk 12.5 for Linux
- Plesk Onyx for Linux
Configuration of Apache, nginx (if enabled) and php-fpm is successful:
# apachectl -t
# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
# php-fpm -t
NOTICE: configuration file /etc/php-fpm.conf test is successful
Webserver Configuration Troubleshooter detects extra configuration:
PLESK_INFO: In some cases, extra webserver configuration files remaining after removing domains might cause conflicts with webserver configuration rebuild process.
A similar to the below error message appears on the Home page in Plesk:
PLESK_ERROR: New configuration files for the Apache web server were not created due to the errors in configuration templates: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 7 of /etc/httpd/conf.d/zz010_psa_httpd.conf: Could not open configuration file /etc/httpd/conf/plesk.conf.d/vhosts/example.com.conf: No such file or directory . See the details in Configuration Troubleshooter
PLESK_ERROR: WARNING! Some problems are found during start service apache2(see log file: /var/log/plesk/rc_actions.log) Continue... /opt/psa/admin/sbin/pleskrc execution failed:
When rebuilding domain configuration, the process fails with the following error message:
PLESK_ERROR: Error: Can not reconfigure web server configurations: Unable to execute httpdmng: Domain with name '' does not exist
The command returns a non-empty result:
# plesk db "select c.id, c.objectId as 'domain_id' from Configurations c left join domains d on c.objectId=d.id where c.objectType in ('domain', 'nginxDomain') and d.id is null;"
The Plesk database contains records about non-existent configuration files.
Open Webserver Configuration Troubleshooter at Tools & Settings in Plesk Onyx 17.8 and from the Extensions menu in Plesk 17.5/17.0/12.5.
Note: If the Webserver Configuration Troubleshooter component is not installed, install it using this KB article.
Click on the button, then set Status to "Error" from the drop-down menu.
The list of broken configuration files will appear. Select all, then click Rebuild > Selected.
If configuration files could not be repaired, select them and click Remove.
Click Check configuration to make sure there is no broken configuration left.