Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

Error in Plesk: New configuration files for the Apache web server were not created due to the errors in configuration templates

Avatar
Vladimir Chernikov
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms:

  • Nginx is running fine and its configuration is successful:

    # nginx -t
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful

  • 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: nginx: [warn] conflicting server name "example.com" on 203.0.113.2:80, ignored nginx: [emerg] open() "/var/www/vhosts/system/example.com/logs/proxy_access_log" failed (24: Too many open files) nginx: configuration file /etc/nginx/nginx.conf test failed

  • The following command returns a non-empty result:

    # plesk db "select description from Configurations where status <> 'ok'\G"

Cause

The issue with web-server configuration has been previously fixed, but the Plesk database still contains old error messages.

Resolution

  1. Connect to the server via SSH.

  2. Create folder for temporary used files:

    # mkdir -p /tmp/plesksupport

  3. Create file with other affected domains:

    # MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin psa -Ne"select name from domains where id in (select objectId from Configurations where status<>'ok')" > /tmp/plesksupport/domainlist.txt

  4. Reconfigure other affected domains:

    # cat /tmp/plesksupport/domainlist.txt | while read domain; do /usr/local/psa/admin/bin/httpdmng --reconfigure-domain $domain; echo "$domain - success"; done
    # /usr/local/psa/admin/bin/httpdmng --reconfigure-server

Comments

3 comments

Sort by Date Votes
  • Avatar
    Martin Sauer

    The problem persists for me. Error message after usign this "fix":

    Error: New configuration files for the Apache web server were not created due to the errors in configuration templates: nginx: [warn] conflicting server name "_" on 82.x.y.z:443, ignored nginx: [warn] conflicting server name "_" on [2001:x1:x2:x3:x4:x5]:443, ignored nginx: [warn] conflicting server name "" on 82.x.y.z:80, ignored nginx: [warn] conflicting server name "" on [2001:x1:x2:x3:x4:x5]:80, ignored nginx: [emerg] bind() to [2001:x1:x2:x3:x4:x5]:443 failed (99: Cannot assign requested address) nginx: configuration file /etc/nginx/nginx.conf test failed. Search in KB
     
    The main configuration file:
    File Path: n/a
    Orig. Template: nginx-php
    Related Domain: /

    is shown as eeronous. All other files are green.

    Fun fact: Ihad that ipv6 address active. As of now all sites are disconnected from the IP. So it shouldnt be relevant at all for plesk or apache/nginx. Yet it is correctly assigned to the server.
    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Martin Sauer

    Plesk, check the Nginx configuration:

    # nginx -t
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful

    If you have the same output as provided, Nginx configuration is fine and this error message is orphaned and to remove it you may use this instruction: https://support.plesk.com/hc/en-us/articles/213389789

    Otherwise, the output will provide a hint of where to check the issue.

    In case of getting stuck, submit a support request to support Plesk directly or to the partner where the license was purchased.

    1
    Comment actions Permalink
  • Avatar
    Martin Sauer

    Ivan Postnikov Thank you so much. You nailed it. There were some other support entries with similar solutions, but apparently my OS configuration wasnt ok by then. Now it was and all problems solved.

    Thank you again - good one.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles