Plesk Website Showing Default Page: How to Fix It

When a website on Plesk displays the default “Plesk Default Page” or a generic Apache/Nginx welcome screen instead of the actual site content, it usually means the web server cannot find or access the site files — or the domain is not correctly mapped to its document root. This is a common issue after domain migrations, new domain additions, or accidental file deletions. The fix depends on which of several underlying causes applies, and this guide walks through each one in order of likelihood.

Cause 1: Site Files Are Missing From the Document Root

Plesk serves website files from /var/www/vhosts/domain.com/httpdocs/. If that directory is empty or contains no recognised index file (index.html, index.php), the web server has nothing to display and falls back to the default page. This is the most common cause and the first thing to check.

1. Log in to the Plesk control panel and navigate to Websites & Domains.
2. Click File Manager for the affected domain.
3. Open the httpdocs folder and confirm whether files are present.
4. If the folder is empty, re-upload your site files via File Manager, FTP, or SFTP.
5. Ensure the root directory contains an index.php or index.html file.
6. Reload the domain in a browser to confirm the site now loads correctly.

If you are deploying via SSH, you can quickly check the folder contents from the command line:

ls -la /var/www/vhosts/domain.com/httpdocs/

Cause 2: Domain Added to Plesk But Not Yet Configured

A freshly added domain in Plesk always shows the default page until content is uploaded or an application is installed. This is expected behaviour. Plesk creates the directory structure and virtual host configuration automatically, but the httpdocs folder will contain only a placeholder file.

1. Upload a site via File Manager or FTP, or use Plesk’s built-in autoinstaller to deploy an application such as WordPress.
2. To use the autoinstaller, go to Websites & Domains, select the domain, and click Install Applications.
3. Follow the installation wizard and the default page will be replaced once the installation completes.

Cause 3: Wrong Document Root Configured

Plesk allows the document root to be changed from the default httpdocs to a custom path. If this was altered accidentally — or set incorrectly during a migration — the web server will look in the wrong directory and find nothing to serve.

1. In Plesk, go to Websites & Domains and select the affected domain.
2. Click Hosting Settings.
3. Locate the Document root field and check the path shown.
4. If it does not point to httpdocs (or your intended subdirectory), correct it and click OK.
5. Plesk will update the virtual host configuration and reload the web server automatically.

The correct default value for most Plesk subscriptions is simply httpdocs (a relative path, not an absolute one). Plesk resolves this to /var/www/vhosts/domain.com/httpdocs/ internally.

Cause 4: DNS Points to the Wrong Server

If the domain’s DNS A record resolves to a different IP address — perhaps an old server from before a migration — requests will never reach the Plesk server in the first place. Instead, they hit another server that displays its own default page, which can look identical to a Plesk configuration problem.

1. Find the current IP of your Plesk server. This is visible in Plesk under Tools & Settings → IP Addresses.
2. Check what IP the domain currently resolves to using nslookup domain.com or a public DNS checker.
3. If the IPs do not match, log in to your DNS provider and update the A record to point to the correct Plesk server IP.
4. Allow time for DNS propagation — typically between a few minutes and 48 hours depending on the TTL value.
5. Once DNS has propagated, reload the domain and confirm it now reaches the correct server.

To confirm which server is actually responding to a request, you can use curl from any machine:

curl -I http://domain.com

Check the response headers for server software or any Plesk-specific identifiers to confirm which machine is handling the request.

Cause 5: Domain Redirect or Alias Issue

In Plesk, domains can be configured as standalone subscriptions, aliases (parked domains), or redirects. If a domain is set as an alias or redirect but the target subscription or URL is misconfigured, Plesk may serve the default page instead of the intended content.

1. Go to Websites & Domains and look at the label displayed beneath the domain name.
2. If it shows Alias or Redirect, confirm the target is correct and the destination subscription is active.
3. If the domain should be a standalone hosting subscription, check that it has its own subscription rather than being attached as an alias to another domain.
4. To convert an alias into a standalone subscription, you may need to remove it as an alias and add it as a new domain with hosting enabled.

Cause 6: WordPress Files Present But Default Page or White Screen Shows

If WordPress files are present in httpdocs but the site still shows the default page or a blank screen, the most likely culprit is a missing or malformed .htaccess file. WordPress relies on .htaccess rewrite rules to route all requests through index.php. Without it, Apache cannot handle WordPress URLs correctly.

1. In Plesk File Manager, navigate to httpdocs and check for a file named .htaccess. Note that files beginning with a dot may be hidden — enable hidden files in File Manager if needed.
2. If the file is missing, log in to the WordPress admin panel and go to Settings → Permalinks.
3. Click Save Changes without changing anything. WordPress will attempt to regenerate the .htaccess file automatically.
4. If the WordPress admin is inaccessible, create .htaccess manually in httpdocs with the following standard WordPress rewrite block:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Also confirm that mod_rewrite is enabled on the server. In Plesk, this is usually enabled by default for Apache, but can be verified under Tools & Settings → Apache Web Server Settings.

Checking Which Virtual Host Is Being Served

If you have worked through the causes above and the problem persists, it may help to inspect the virtual host configuration that Plesk has generated for the domain. Plesk stores virtual host configuration files at /var/www/vhosts/domain.com/conf/. The key files are vhost.conf and vhost_ssl.conf.

1. Connect to the server via SSH.
2. Run ls /var/www/vhosts/domain.com/conf/ to list the configuration files present.
3. Review vhost.conf and confirm the DocumentRoot directive points to the correct directory.
4. To check which virtual host Plesk is matching for an incoming request, use:

curl -I http://domain.com

Examine the Server and X-Powered-By response headers. If the response looks unexpected — for example, it returns headers from a different application stack — the request is likely landing on a different virtual host or server entirely.

After making any changes to virtual host configuration files manually, run plesk repair web domain.com to have Plesk rebuild and reload the configuration cleanly, rather than editing Apache or Nginx config files directly.

Related articles: Plesk Troubleshooting Guide