How to Replace the Plesk Default Page with an Actual Website on pukekoherugby.co.nz

Updated

The Plesk default page appears because the domain resolves to a server where Plesk is installed, but no website content has been published for that domain yet. To replace it, log in to Plesk, confirm the domain exists as a site or subdomain, then upload files to its document root (or install a CMS like WordPress) and point DNS to that server. The default page disappears once the document root contains an index file and the domain's DNS and hosting configuration match.

Why the Plesk default page shows up

The page currently served at pukekoherugby.co.nz is Plesk's placeholder, which states that Plesk is "a hosting panel with simple and secure web server, website and web apps management tools" designed to manage web, DNS, mail and other services through a GUI. That text is not the rugby club's content — it is what the server returns when a domain is routed to Plesk but has no site files assigned to it.

Common causes:

  • The domain is added in Plesk but no document root content exists (no index.html, index.php, etc.).
  • DNS points to the Plesk server, but the domain is not configured as a website or subdomain there.
  • Files were uploaded to the wrong directory, so the server falls back to the default page.
  • The domain is parked or has no hosting subscription attached.

Steps to publish a real site

1. Log in to Plesk and confirm the domain

Sign in to the Plesk panel for the server that hosts this domain. Under Websites & Domains, check whether pukekoherugby.co.nz is listed as a domain or subdomain. If it is missing, add it as a new domain or subdomain first — without this entry, no document root exists to serve content from.

2. Locate the document root

Open the domain's settings to find its document root (often httpdocs or public_html). This is the folder the web server reads from. Any file placed here can be served publicly.

3. Add content

Two common paths:

  • Upload static files — Use the Plesk File Manager or FTP/SFTP to place an index.html (or index.php) plus assets into the document root. The server will serve that file instead of the default page.
  • Install a CMS — Plesk offers a WordPress toolkit and other app installers. Installing WordPress creates the necessary files and database automatically, giving you an editable site without manual file uploads.

4. Verify DNS and hosting

Check that the domain's DNS records (A record or CNAME) point to the IP address of the Plesk server. If DNS points elsewhere, visitors will never reach this Plesk instance and the default page will persist. Also confirm the domain is assigned to the correct subscription and IP in Plesk.

5. Refresh and test

After files are in place and DNS has propagated, reload the domain. The Plesk placeholder should be replaced by your content. If it is not, clear your browser cache and re-check the document root path and DNS resolution.

Quick troubleshooting table

Symptom Likely cause Check
Default page still shows after upload Files in wrong folder Confirm document root path in Plesk
Domain loads nothing / times out DNS not pointing to server Verify A record matches server IP
Domain not listed in Plesk No site/subdomain created Add domain under Websites & Domains
CMS install fails Missing PHP/database Check Plesk components and DB availability

If you only need the rugby club's contact info

If your goal is not to manage the server but to reach the official Pukekohe Rugby club, note that the Plesk default page contains no club contact details, address, or schedule. The placeholder only references Plesk itself and links to Plesk guides, a knowledge base, forum, blog, and video guides. To find the club, search for the organisation's current official site or social pages rather than relying on this domain, since the domain currently serves only the hosting panel's default content.