Websites
Inspect your domains, document roots, and website-level settings.
1Overview
Websites lists the hosting domains owned by your account and links each to its managed document root and website controls.
2Before you begin
User-panel actions affect only resources owned by the signed-in hosting account.
3Step-by-step workflow
Open Websites, choose a domain, review its status and document root, then use its tools for website settings, PHP, logs, SSL, or security as offered by your package.
- Open Websites and find the domain you want to manage.
- Confirm its status, document root, and associated application before changing it.
- Choose Add website when you need a separate site and your package permits another domain.
- Enter a domain you control and review the proposed directory so an existing site is not overwritten.
- Create the site and wait for provisioning to finish.
- Upload its content through File Manager or your assigned transfer account.
- Point the domain to the assigned server address and configure SSL when validation is possible.
- Open the public site and test a page, image, and application login if applicable.
4Practical example
Example: shop.example.com can be a separate website with its own document root. An alias for an existing site belongs in Domains instead.
5Verify the result
Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.
- Request the public URL and confirm the document root serves the expected content.
- Review logs after runtime, SSL, or application changes.
6Common problems and what to check
The domain already exists: check your current websites and aliases before trying a different spelling.
The server default page appears: check DNS, the document root, and the site entry file.
Creation is unavailable: review your package domain allowance and ask the provider to investigate the displayed provisioning error.
7Security, impact, and rollback
Keep application files inside the displayed document root. Deleting the domain or its root removes access to the site and may not remove related DNS, mail, or certificates.