简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Parallels Plesk?
Parallels Plesk is hosting automation software: a control panel that a hosting provider installs on a server so that domains, websites, email and related services can be created and managed without hand-editing server configuration files. The page at this address is the placeholder a Plesk installation serves when no website has been set up on that domain yet — so seeing it usually means the hosting account exists but is empty, misconfigured, or pointed at the wrong server.
Who actually uses it
- Hosting providers and resellers use Plesk as the layer their customers log into, and to standardise how accounts are provisioned across many servers.
- Small businesses and agencies use it to run several sites, email accounts, databases and DNS records from one dashboard, often without a dedicated sysadmin.
- Developers and IT staff use it when they want repeatable setups — PHP versions, SSL certificates, staging sites — rather than configuring each service by hand.
What it competes with, and the trade-off
Plesk is most often compared with cPanel, the other long-established commercial control panel. Both hide the same underlying stack (web server, mail, databases, DNS) behind a GUI; they differ in interface conventions, extension ecosystems and which operating systems and hosting partners favour them. Free or open alternatives such as Webmin and Vesta Control Panel (now largely community-maintained) cost nothing but typically demand more of the administrator.
The core trade-off is convenience against control and cost: a panel speeds up routine tasks and reduces mistakes, but adds a licence fee and a layer you must keep patched, and it can get in the way of unusual configurations.
If you are looking at this page now
Decide first whether you are the server owner or a customer:
- Customer on shared hosting: you almost certainly cannot fix this yourself. Contact your host and ask whether the domain is correctly assigned to your account and whether DNS points to their server.
- Server owner or administrator: log in to Plesk (commonly on port 8443 over HTTPS) and check that a domain and document root exist, that the correct site is set as default, and that DNS resolves to this machine. If Plesk was installed but you never intended to run a panel, removing it and serving the site directly may be simpler.
As a next step, confirm what you actually need: a panel for managing many sites and mailboxes, or just a single site on a plain server. The placeholder page itself is a diagnostic signal, not a product feature.
How do I remove the default Parallels Plesk page from my web server?
To remove the default Parallels Plesk page, you don't delete the page itself. You replace the empty document root with your own site content, or point the domain to a location that already has one. The Plesk placeholder appears because the domain exists but no website files are being served at that address.
The usual fix in Plesk
- Log in to Plesk (typically on port 8443 of your server).
- Go to Websites & Domains and select the domain showing the default page.
- Open Document Root (or File Manager) and check the folder it points to, often
httpdocsorpublic_html. - Upload an
index.htmlorindex.phpthere, or install an application (WordPress, for example) into that directory. - Confirm the domain's DNS points at this server and that the correct document root is set for both HTTP and HTTPS.
Once a valid index file exists, the placeholder is replaced automatically.
If you're not using Plesk
The same logic applies on any host: the default page is what the web server shows when the configured directory has no index file. On Apache or Nginx, find the site's root or DocumentRoot directive, make sure it points to your project folder, and place an index file there. If the domain is parked or unused, remove the domain from the server configuration or point it elsewhere rather than leaving an empty root.
Quick decision guide
| Situation | What to do |
|---|---|
| Domain will host a real site | Upload or install content into the document root |
| Domain is unused | Remove the domain from Plesk or redirect it |
| Wrong folder is being served | Correct the document root setting |
| DNS points elsewhere | Update DNS to the correct server |
As a next step, open the domain's document root in Plesk's File Manager and confirm whether it is empty. If it is, adding a single index.html is the fastest way to verify the fix before building out the full site. For Plesk-specific configuration, the official documentation is at Plesk.
Can I use Parallels Plesk to set up and manage multiple websites on one server?
Yes. Parallels Plesk is built for exactly that: hosting and managing multiple websites from a single server, using one control panel. The page you are looking at is the placeholder Plesk shows when a domain is pointed at a server but no site has been configured there yet — a sign that Plesk is installed and waiting for domains to be added.
What multi-site management looks like in practice
- Add domains as separate sites. Each domain or subdomain becomes its own entry in the panel, with its own document root, so files and databases stay separated.
- Per-site configuration. You typically set PHP versions, SSL certificates, mailboxes, DNS records, FTP/SFTP accounts and databases individually for each site rather than server-wide.
- Central overview. One login covers all sites, which is the main reason agencies, freelancers and small hosts use a panel instead of editing server config files by hand.
- Limits depend on your licence. The number of domains, mailboxes and resellers you can create is set by the Plesk edition and licence your host provides, not by the software's technical ceiling.
Who it suits, and the trade-offs
It fits a freelancer or small agency running a handful to a few dozen client sites on one VPS, or a business consolidating several brand domains. The trade-off is abstraction: the panel hides the underlying web server, so unusual configurations may need manual work outside it. It also adds overhead compared with a lean, hand-configured server, and if all sites share one server, a resource spike on one can affect the others.
A useful next step
Decide first whether you want a panel-managed server (easier, less control) or a plain one (more control, more maintenance). If you choose Plesk, start by adding one test domain and verifying DNS, SSL and mail before migrating live sites. For platform details, see Plesk and Parallels.
What are the differences between Parallels Plesk and Parallels Automation for hosting providers?
The difference is scope: Plesk is a single-server control panel for managing websites, mail and DNS on one machine; Parallels Automation is a multi-server platform for running a hosting business, adding billing, provisioning and self-service across many servers. The page at nbpat.co.uk is a placeholder "Web Server's Default Page" generated when Plesk is installed but no site is configured, and it lists both under Service Provider Products.
Where each fits
| Parallels Plesk | Parallels Automation | |
|---|---|---|
| Typical scale | One server, or a small cluster | Many servers and services |
| Main job | Control panel for hosting accounts | Business automation: billing, provisioning, self-service |
| Who uses it | Small hosts, agencies, admins, resellers | Larger service providers and cloud operators |
| Trade-off | Quick to set up, limited business logic | More capable, heavier to deploy and run |
Concrete scenario
A two-person agency with one dedicated server wants to create customer domains, mailboxes and databases. Plesk is the natural fit: the page itself says you can "create domains and set up Web hosting using Parallels Plesk." A provider selling shared hosting, VPS and SaaS to hundreds of small businesses needs order-to-cash automation, so Automation is the relevant layer; Plesk may still sit underneath as the panel customers see.
Next step: decide by scale and business process. If you only need to manage sites and mail on one server, you do not need Automation. If you need automated ordering, billing and provisioning across multiple servers, Plesk alone will not cover it.
For the vendor's own product framing, see Parallels.
Is Parallels Desktop for Mac the right choice for running Windows applications on macOS?
Yes—if your goal is to run Windows programs inside macOS without rebooting, Parallels Desktop for Mac is explicitly positioned for that job. The page describes it as the way to run Windows, Linux, or other operating systems alongside OS X, so a Mac user who needs a Windows-only app can keep macOS as the main environment and open Windows in a window.
That matters most for people who switch between platforms all day. A designer using a Mac but needing a Windows-only CAD tool, an accountant running a legacy Access database, or a developer testing a Windows build can avoid a second machine or a reboot.
Weigh these trade-offs:
- Convenience vs. resources. Running two systems at once is easier than dual-booting, but it consumes RAM, disk space and battery life.
- Compatibility vs. simplicity. Parallels is designed for many operating systems, but heavy 3D games and low-level hardware tools often work better on native Windows hardware.
- Windows licence. You still need a valid Windows licence, which is separate from the Parallels product.
If your work is mostly macOS with occasional Windows apps, this is a reasonable fit. If Windows performance is the priority, compare with Apple Boot Camp guidance or a dedicated PC before deciding. For the product itself, check Parallels for current system requirements and supported Windows versions.
How do I access the Plesk control panel to create domains and configure hosting?
The page at nbpat.co.uk is the default Parallels Plesk placeholder, not a working site. It states plainly that you see it "because there is no Web site at this address," and it points to Parallels Plesk as the tool for creating domains and setting up web hosting. In other words, the hosting account exists, but no site has been published to that address yet.
What this means for you
- If you are the account owner: your domain resolves to a server running Plesk, but the document root is still empty or pointing at the default page. You need to log in to Plesk to add the domain and upload or install a site.
- If you are a visitor: there is nothing to browse here. The page is a server-generated notice, not the site's content.
How to reach the Plesk panel
The panel usually lives on the same host under a secure URL, commonly one of these patterns:
https://nbpat.co.uk:8443https://www.nbpat.co.uk:8443- A hostname your provider gave you, such as
https://server-name.example:8443
Port 8443 is the conventional Plesk login port; some setups use 8880 for the non-secure version. If neither responds, check the welcome email from your hosting provider — it contains the exact panel URL, username and password.
Once you are in, the path is typically Websites & Domains → Add Domain (or select the existing domain), then set the document root and create a hosting space. DNS for the domain must already point at this server, which appears to be the case here.
If you do not have credentials
Contact whoever sold you the hosting. The Plesk administrator — not Parallels itself — controls your login. If you are evaluating Plesk for a new project, the vendor's own site is the place to compare editions: Plesk. For the broader Parallels product line referenced on the page, see Parallels.
Decision criterion
If you only need to publish a simple site, ask your provider whether they offer a one-click installer or a simpler panel; Plesk's full feature set is aimed at managing multiple domains, mail and reseller accounts. If you are the one administering the server, log in on port 8443 first and confirm the domain is listed under Websites & Domains before changing anything else.
Amazon.com, Inc.
Microsoft 365
Dublin, Leinster, Ireland
User reviews (0)