• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Error: New files of configuration for Apache web server were not built due to errors

tristans

Basic Pleskian
i can see this message on the home page:

Error: New files of configuration for Apache web server were not built due to errors in configuration templates. The detailed error message was e-mailed to you, so please check the e-mail, fix the errors, and click here to retry generating configuration.

How can i find more information about what errors caused this?

this error appeared after I migrated a large domain (with a larger number of sub-domains - about 40) from my old server. the migration manager indicated no error and migration successful.

is there a log file where i can see what Apache configuration errors were found? if i don't know what caused this error, it will vb virtually impossible to correct it (given the number of domains and subdomains that i just migrated).

Using Plesk 10.0.1 on CentOS 5 64-bits (1and1 virtual host)
Linus 2.6.18-194.26.1.el5xen #1 SMP x86_64 x86_64 x86_64 GNU/Linux
 
thanks.

i'me very familiar with configuring apache, and i have written many very complex config files for apache.

that is not the problem there. in fact, when i start apache on the system, it runs just fine.

but apparently plesk is trying to tell me that it was not able to configure some file, but it does not tell me what file is causing the problem.

is there some log or info to determine exactly what triggers this plesk message?
 
by the way, i did not modify any templates, and the only configuration customizations for my websites are done via the .../conf/vhost.conf files for each virtual domain.

a vague message "an error occurred" without any information or any way to figure out what error occurred and why, this is not very helpful :(
 
Back
Top