How to Replace a Plesk "Web Server's Default Page" with a Real Website

The "Web Server's Default Page" appears because Plesk is installed on the server but no website is configured at that address yet — the page itself states: "You see this page because there is no Web site at this address." To replace it, you need to (1) create or assign a domain in Plesk, (2) make sure the domain points to the correct document root, (3) put real content there (upload files or install an app), and (4) confirm DNS resolves the domain to that server. Once a valid index file exists in the document root, the default page stops showing.

Why the default page shows up

Plesk is a hosting control panel for managing web, DNS, and mail services through a GUI. When a domain resolves to the server but has no site content assigned, Plesk serves its placeholder page instead of a real site. So the default page is a symptom, not a problem in itself — it means the domain-to-content link is missing.

Step 1: Create or assign the domain in Plesk

1. Log in to Plesk.
2. Create the domain (or confirm it already exists under Websites & Domains).
3. Note the document root Plesk assigns — this is the folder where the site's files must live. If the domain is assigned to the wrong root, the site won't load even with correct files.

Expected result: the domain appears in Plesk with a defined document root path.

Step 2: Put content in the document root

The default page disappears once a real index file exists. Two common routes:

• Upload your own site: place an index.html (or index.php, etc.) plus assets into the document root via the Plesk File Manager or FTP/SFTP.
• Install an application: use Plesk's application installer (e.g., WordPress) to deploy a site automatically, which creates the files and database for you.

Verify: the document root contains an index file, and its name matches what the web server serves by default.

Step 3: Point DNS to the Plesk server

For the domain to reach this server, its DNS records must resolve to the server's IP.

• Check the domain's A record (and AAAA for IPv6) points to the correct server IP.
• If Plesk manages DNS for the domain, confirm the records inside Plesk match the intended IP.
• Allow for DNS propagation before re-testing.

Verify: from a terminal, resolve the domain and confirm it returns the server's IP:

dig +short example.com

Step 4: Confirm the default page is gone

• Visit the domain in a browser and confirm your site loads instead of the Plesk placeholder.
• If the default page still appears, check in this order: (1) is there an index file in the document root? (2) does DNS resolve to the right server? (3) is the domain assigned to the correct root in Plesk?

Common sticking points

Key takeaway

The Plesk default page is a placeholder for "no site here." Replacing it is a matter of connecting three things: a domain in Plesk, a document root with real content, and DNS that resolves to the server. Get all three aligned and the default page disappears.