Domain Shows the default Apache test page or Plesk default page instead of the Domain Content

Refers to:

  • Plesk for Linux
  • Plesk 12.0 for Windows

Created:

2016-11-16 13:04:21 UTC

Modified:

2017-02-23 09:38:57 UTC

1

Was this article helpful?


Have more questions?

Submit a request

Domain Shows the default Apache test page or Plesk default page instead of the Domain Content

Symptoms

Some or all of the domains are showing the Apache default page (not the Plesk default page).

Cause

Apache doesn't reach the configurations added by Plesk.

Resolution

  1. Make sure that the domain name resolves into the same IP address on which the domain's hosting is set up in Plesk. Apache and IIS virtual hosts are created to strictly match the hostname and IP address and, if a request for a domain comes to an IP address other than the one specified in the virtual host configuration, the request will be handled by the default virtual host and the Web Server's Default Page will be displayed.

    To find out the IP address the virtual host uses, check hosting settings of the domain ( Domains > domain > Web Hosting Settings in Plesk 9.x and earlier and Subscriptions > domain.tld > Websites & Domains tab > Web Hosting Access in Plesk 10 and newer). Then, compare this IP address with the IP address the domain resolves into. In addition, try verifying the DNS record against several DNS servers, including your own (see KB article #213912165 for more information on how to trace name resolution problems):

    C:\\>nslookup domain.test
    Name: domain.test
    Address: 1.2.3.4

    If a mismatch is found, change the DNS records or reassign the domain to correct the IP address.

  2. Try opening a non-default document for the domain (http://domain.tld). Open a particular page, for example, http://www.domain.tld/mytest.html (the mytest.html file should be in the domain's httpdocs folder). If it works, the domain is most likely missing an index page, or this page is not listed in the DirectoryIndex directive in the main Apache configuration file ( httpd.conf ).

    Index files usually have names such as "index.html," "index.php," and so on, but you can add your own names. You can modify DirectoryIndex in httpd.conf to match your needs, for example:

    DirectoryIndex index.html index.htm index.shtml index.php index.php3 my_index.html

    Then, restart Apache for these changes to take effect.

  3. Try rebuilding the Apache configuration files for the domain:

    Plesk 10 and later versions:

    # /usr/local/psa/admin/bin/httpdmng --reconfigure-domain <domain_name>

    Plesk 9 and earlier versions:

    # /usr/local/psa/admin/bin/websrvmng --reconfigure-vhost --vhost-name=<domain_name>

    Note: replace <domain_name> with the actual domain name.

    If the issue occurs for all domains, you can run this command:

    Plesk 10 and later versions:

    # /usr/local/psa/admin/bin/httpdmng --reconfigure-all

    Plesk 9 and earlier versions:

    # /usr/local/psa/admin/bin/websrvmng --reconfigure-all
  4. If you have a test server, try comparing its main Apache configuration file to the one on the problem server. Make sure these lines are present:

    NameVirtualHost <IP>:80
    NameVirtualHost <IP>:443
    Include conf.d/*.conf

    Note: replace <IP> with the actual IP address of your server.

  5. If nginx is installed, but not used, try turning on and turn off nginx support:

       # /usr/local/psa/admin/sbin/nginxmng -e
    # /usr/local/psa/admin/sbin/nginxmng -d
  6. If nginx is used, check its status:

    # /etc/init.d/nginx status 
    nginx dead but pid file exists

    To fix the issue, follow the steps below:

    6.1. Back up the nginx.pid:

        # mv /var/run/nginx.pid /var/run/nginx.pid_bak

    6.2. Enable the nginx service:

        # /usr/local/psa/admin/bin/nginxmng -e

    6.3. Disable the nginx service:

        # /usr/local/psa/admin/bin/nginxmng -d

    6.4. Enable the nginx service once again:

        # /usr/local/psa/admin/bin/nginxmng -e

    6.5. Rebuild web configuration files:

        # /usr/local/psa/admin/bin/httpdmng  --reconfigure-domain <domain_name>
  7. Ensure that zz010_psa_httpd.conf is present in /etc/apache2/conf-enabled/ :

       # ln -s /etc/apache2/conf.d/zz010_psa_httpd.conf /etc/apache2/conf-enabled/
Have more questions? Submit a request
Please sign in to leave a comment.