Skip to content

Websites

Find each hosted domain, its owner, document root, status, and website-level tools.

1Overview

Websites is the server-wide website inventory. It links a domain to its account, document root, PHP runtime, security settings, and current status.

Websites in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Administrator website inventory showing each domain, its hosting account, status, SSL state, and management actions.

Websites in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services.

3Step-by-step workflow

Search by domain or account, open Manage for the selected website, then use the detail page to inspect document root, security, logs, and related domain operations. Use the account login action for customer-scoped work.

  1. Open Websites and search for the exact domain or hosting account.
  2. Check the owner, status, document root, and runtime shown for the selected website.
  3. Open the website management action to review its detailed settings and linked tools.
  4. Use Add Website only when creating a genuinely new website for an existing hosting account.
  5. Enter the domain without a URL path and choose the intended owner, root, and supported runtime.
  6. After saving, confirm the new website appears under the expected account.
  7. Check the public domain separately; update DNS at the authoritative provider when the website is ready.
  8. Use the matching SSL, PHP, application, or log tool for follow-up work instead of recreating the website.

4Practical example

Example: example.com and shop.example.com can have different document roots and applications. Check the exact domain before uploading files or changing a PHP version.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Request the public website and its HTTPS endpoint.
  2. Check the website status and relevant log after the change.

6Common problems and what to check

The public site shows a default page: compare its DNS address and configured document root with the website record.

Add Website is rejected: check account ownership, duplicate domains, package limits, and the provisioning message.

HTTPS fails while HTTP works: inspect the certificate and domain validation in SSL/TLS.

7Security, impact, and rollback

Do not delete a website to solve a DNS or certificate problem. Confirm ownership and take a backup before removing a domain from the server.

Related guides

ApplicationsDeploy and operate verified Node.js, Next.js, and Python applications.Packages and feature listsSet resource limits, inode limits, and customer-visible capabilities.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area