A staging site allows testing away from the live domain but consumes account resources.
Applies to: Websites, domains and document roots in SiteWorx
Each website must have the correct domain assignment, document root, DNS destination and certificate. Treat changes to a live primary domain or document root as production changes and take a backup first.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- Create a restricted subdomain or separate site.
- Copy files and use a separate database.
- Update application URLs and configuration.
- Prevent public indexing.
- Remove the staging copy when no longer required. Read the confirmation text because the action may remove data or interrupt service.
Confirm the result
- The intended hostname loads over HTTPS from a private browser session and serves the correct website.
- Forms, database-driven pages and the administration area work without a new PHP, permission or redirect error.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The domain shows the wrong website. | DNS points elsewhere, the domain is attached to another account or the document root is incorrect. | Compare authoritative DNS with the service address and verify the domain and document-root mapping in SiteWorx. |
| HTTPS redirects repeatedly. | Both the application and hosting configuration force different schemes or proxy assumptions. | Keep one controlled HTTPS redirect, clear application caches and test the origin without adding another rule. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Add another website or domain in SiteWorx
- Find a website document root
- Redirect a website from HTTP to HTTPS
- Create custom 404 and other error pages
- Password-protect a website directory
Last reviewed: 2026-07-18.
