How to Replace the Parallels Plesk Default Page with a Real Website

The page at nbpat.co.uk is the stock "Web Server's Default Page" generated by Parallels Plesk, the hosting automation software running on that server. It appears because no website has been published at that address yet — the domain resolves to a working server, but the server has nothing to serve. To replace it, you (or whoever controls the hosting account) need to create a domain in Plesk, point the domain's DNS at that server, and upload or generate actual site content. Once a site is bound to the domain and files exist in its document root, the default page is replaced automatically.

What the default page tells you

The page is not an error and not a parked-domain ad. It is Plesk's placeholder, shown when a request reaches the server but no hosted site matches the requested domain. Two things follow from that:

• The server is reachable and Plesk is installed and running.
• No domain entry (or no content for an existing entry) is configured for nbpat.co.uk.

The page itself links to Parallels product information and notes that you can "create domains and set up Web hosting using Parallels Plesk." That is the action path.

Prerequisites

Before you can publish, confirm you have:

1. Access to the Plesk control panel for the server — either as the server administrator or as a hosting customer with a login.
2. Control of the domain's DNS (at your registrar or DNS provider), so you can point nbpat.co.uk at the server's IP address.
3. The server's IP address, visible in Plesk or from your hosting provider.
4. Website files ready to upload, or a decision to build the site with a tool such as Sitebuilder.

If you are not the account holder, you cannot complete this — the fix requires panel and DNS access.

Steps to replace the default page

1. Create the domain in Plesk

Log in to Plesk and add nbpat.co.uk as a domain (in Plesk this is typically under Websites & Domains → Add Domain). Plesk creates a subscription with a document root — the folder where the site's files live. Note that path; you will need it in step 3.

If the domain already exists in Plesk, skip to step 2.

2. Point DNS at the server

At your registrar or DNS provider, set the domain's A record to the server's IP address (and a www record if you want www.nbpat.co.uk to work). DNS changes propagate over time, so the default page may persist until resolution catches up. You can verify with a DNS lookup tool that the domain now returns the server's IP.

3. Put content in the document root

Two common routes:

• Upload files: Use Plesk's File Manager or FTP/SFTP to place an index.html (or your CMS's entry files) in the domain's document root. The default page is served only when no index file exists, so adding one replaces it.
• Use a site builder or installer: Plesk offers Sitebuilder and one-click application installers (for example, for common CMS platforms). These generate the site files in the document root for you.

4. Verify

Visit http://nbpat.co.uk (and https:// if you have installed a certificate). You should see your content instead of the Plesk default page. If the default page still appears, check:

• DNS has propagated and resolves to the correct IP.
• The domain in Plesk is bound to the same IP the DNS points to.
• An index file exists in the correct document root.
• You are not viewing a cached copy — try a hard refresh or a different network.

Common snags

When this is not your job

If you found nbpat.co.uk by accident and do not own it, there is nothing to fix — the placeholder simply means the owner has not published a site. The only people who can change it are those with Plesk and DNS access for that domain.