• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Unable to generate webserver configuration file

Sally1

Regular Pleskian
Hello,

my actual config is ‪CentOS Linux 7.6.1810 (Core)‬ with Plesk Onyx
Version 17.8.11 Update #64

getting the issue when doing a backup of my domains, but just sometimes. After generate the Files again the issue is gone for some days.


Unable to generate the web server configuration file on the host <xyz.cloud> because of the following errors:


Template_Exception: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Could not open configuration file /etc/httpd/conf.d/zz010_psa_httpd.conf: No such file or directory


file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php

line: 75

code: 0


Please resolve the errors in web server configuration templates and generate the file again.

How can i fix this?


Thx
Sally
 
This could be a temporary issue. You may see the warning and get the email, but in fact right afterwards, there is nothing wrong with the file. The same applies to the webmail configuration files. Most of the time, only the mail is generated, but no warning logged in the GUI. If you see a warning in GUI, it is normally sufficient to generate the "error" configurations by Webserver Configuration Trouble Shooter. The issue should not occur during a backup, because a backup does not touch the configuration files at all unless you select the option where you can block domain access during the backup. Normally the issue occurs after or during the nightly maintenance window, e.g. when updates are installed. It can also occur when several configuration changes are done near the same time, so that one change is processed before another change was finished.
 
When doing the Domain Backups I mark the Option Suspend the Domain until the Backup is completed. When the message appear the repair with the Trouble Shooter is working, at the moment, hope also every time in future when this happens :)

Thx
Sally
 
In normal scenarios it is not necessary to suspend domains during a backup. This is only recommended if you want to make sure that you have a fully consistent data state in your database and files of a subscription. But normally, this is not needed, e.g. it does not really matter if someone posts a comment to a Wordpress website while a backup is running. The comment won't be included in the backup then, but it won't damage the backup. You might see an "error" in the backup as some temporary files are created or deleted after the backup starts, but this does not damage the backup either. So in your case the situation could easily be resolved if you simply uncheck the suspension checkbox.
 
Back
Top