• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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 Apache web server were not created due to the errors in configuration templates.

jwvdmei

New Pleskian
Server info:
OS ‪CentOS Linux 7.2.1511 (Core)‬
Product Plesk Onyx
Version 17.0.17 Update #62, last updated on Dec 27, 2018 03:14 AM

Hi there,
I'm getting the following error on all my websites: 502 bad gateway nginx and see the following error msg:
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/aandenieuwevaart.nl.conf: No such file or directory . Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files.

This message appeared after I removed the subscription "aandenieuwevaart.nl".

Currently I can get some websites live by having "Proxy mode" un-checked in the "Apache & nginx Settings" section.

How can I solve this? I see similar issues on the web but the responses are all slightly different.

I'm a lite user of centos7 and have full access to SSH and Plesk.

Your help is greatly appreciated, Thanks in advance.
 
This is a known and frequent issue. Sometimes, Plesk does not remove configuration entries, but deletes the files only.

Solution a)
Re-create aandenieuwevaart.nl domain (it is sufficient to create it in an existing subscription, but you can equally well create a subscription with it), then re-activate proxy mode, then delete aandenieuwevaart.nl again.

Solution b)
Remove the symbolic link, e.g.
# rm /etc/httpd/conf/plesk.conf.d/vhosts/aandenieuwevaart.nl.conf

I suggest, too, to run
# nginx -t
# apachectl -t
afterwards to make sure that all other syntax is good.
 
Good evening Peter,

Thank you for reply!

In Plesk I see the following (see red stuff):
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/aandenieuwevaart.nl.conf: No such file or directory . Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files.

Do I still need to do that? Or does the command "apachectl -t" take care of that?

Thanks in advance
 
Do not try to reconfigure the web server configuration files with Plesk functions unless you have either deleted the symbolic link (solution (b)) or recreated and redeleted the domain (solution (a)). After you have solved the issue by using solutions (a) or (b) you can use the configuraion trouble shooter to "generate broken configuration files" (do not generate all files, it is unnecessary).

The "apachectl -t" only tests the syntax but does not do anything else. The same applies to "nginx -t". It is important to test the syntax before trying a reload or restart of these services, because else the restart will fail and your websites will become unavailable until the issue is solved and the services can be restarted.
 
I do not understand the post. The picture does not show the domain that Plesk claims it is missing config files for. It looks as if was successfully removed. What is the output of
# apachectl -t
?
 
Then nothing stops you from clicking "generate broken configuration files once again" in the web configuration trouble shooter. Afterwards, all should be o.k. again.
 
Hi Peter,
I am having a similar problem. I am getting paid support from Plesk Support, but despite trying all day, we haven't gotten any results yet. When I restart the server, it gets better, but after a while I get the same error. No website is available at the moment. When I try to rebuild the files, I get a result like I sent a screenshot. do you have an idea? how can we solve it.


Screen Shot 2020-12-14 at 01.53.16.png

Screen Shot 2020-12-14 at 01.50.26.png
 
Official Plesk support has never failed to solve any issue that I had raised with them, so I wonder why you would not want to rely on their analysis and assistance? Specifically in this case where the error messages are so detailed. They'll sure be able to fix anything regarding Plesk.

Your errors are showing two details.
a) A certificate file already exists that should not actually be there.
b) A ModSecurity rule set does not exist that should be there. (Did you recently upgrade Plesk or your operating system?)

I'd start like this to solve it:

a) Look into /usr/local/psa/var/certificates/scfEQ35qF what this certificate covers, e.g.
# openssl x509 -in /usr/local/psa/var/certificates/scfEQ35qF -text -noout
If it covers the domain you want to create or edit, do this:
1. Websites & Domains > Hosting Settings > change SSL setting to "none" or the server's default certificate
2. E-Mail > Settings > change SSL settings of the mail certificate to "none" or the server's default certificate
3. Websites & Domains > SSL/TLS > Delete the certificate
4. Verify on hard disk that the file has been removed, e.g. # ll /usr/local/psa/var/certificates/scfEQ35qF, if not, remove it.
If the certificate does not cover the domain you want to create or edit: What does it cover instead of your domain?

b) Disable ModSecurity serverwide
1) Tools & Settings > Security > Web Application Firewall (ModSecurity) > Off
2) Either install the Comodo Ruleset or - if it is not available - choose a different one that is.
3) Turn ModSecurity on again

After (a) and (b) have been fixed:
Tools & Settings > Webserver Configurations Troubleshooter > Select erroneous entries > Rebuild > Broken
 
Hi Peter, I am having a similar problem. No website is available. When I try to rebuild the files, I get an error (screenshot). Any help would be great! so I can get this solved. Thanks

error-plesk.png
 
Back
Top