Apache and Nginx (if enabled) web-servers are running fine and their configuration 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
Webserver Configurations Troubleshooter shows any of the following messages:
When checking configurations:
PLESK_INFO: In some cases, extra webserver configuration files remaining after removing domains might cause conflicts with webserver configuration rebuild process.
PLESK_INFO: There is an extra configuration with id 6 belongs to the missed domain with id 1
When rebuilding configurations:
PLESK_ERROR: Error: Can not reconfigure web server configurations: Unable to execute httpdmng: Domain with name '' does not exist
PLESK_ERROR: Error: New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server
One of the following messages might appear on Plesk Home:
PLESK_ERROR: New configuration files for the Apache web server were not created due to the errors in configuration templates: ...
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:
PLESK_ERROR: Due to the following errors in the configuration templates, no new configuration files could be created for the Apache webserver: Can not restart web server: graceful restart failed, perform full restart httpd stop failed 9 / usr / sbin / httpd processes are killed
INFO: Service: Some problems are found during attempt to graceful service httpd - control script does not exist or is not executable (see log file: /var/log/plesk/rc_actions.log)
PLESK_ERROR: nginx: [emerg] duplicate listen options for [2001:db8:f61:a1ff:0:0:0]:80 in /etc/nginx/plesk.conf.d/server.conf:189 nginx: configuration file /etc/nginx/nginx.conf test failed.
PLESK_ERROR: AH00526: Syntax error on line 47 of /etc/httpd/conf/httpd.conf: KeepAlive must be On or Off
Going to Tools & Settings > Webserver Configurations Troubleshooter shows records with
File Path: N/Aand
Related domain: Deleted, as it's shown in the following image:
The following command returns multiple orphan records (non-empty result):
# plesk db "select description from Configurations where status <> 'ok'\G"
Plesk Administrator may receive an email notification containing one of the messages shown in this article
The issue with web-server configuration has been previously fixed, but the Plesk database still contains records about non-existent configuration files or old error messages.
Click on a section to expand
- Log in to Plesk GUI
Go to Tools & Settings > Webserver Configurations Troubleshooter
Note: If the Webserver Configurations Troubleshooter option is not shown, install it following the instructions available in this KB article.
Click the button > Set Status search filter 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.
Connect to the server via SSH
# plesk db dump psa > /root/psa_dump.sql
Remove broken configuration entries from the Plesk database:
# plesk db "delete from Configurations where status <> 'ok'\G"
Validate configuration files:
# plesk repair web -validate-configuration
If errors are found, fix them with the command:
# plesk repair web -y