Provide useful branded error pages without hiding server errors or returning a successful 200 status for missing content.
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 lightweight static error pages that do not depend on the same application or database that may have failed.
- Configure the error page for the intended domain and status through SiteWorx or supported web-server rules.
- Use root-relative links and avoid assets that may also be missing under the failed path.
- Request a nonexistent URL and inspect the response status to confirm it remains 404 rather than 200.
- Test HTTPS, www and non-www hostnames and any application-level routing.
- Keep technical details out of public error pages and use logs for diagnostics instead.
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 problem started immediately after a change. | A deployment, plugin, permission, PHP or configuration change introduced the fault. | Roll back only the last known change, clear caches and retest before making a second change. |
| The fault is intermittent. | Resource limits, traffic spikes, remote dependencies or scheduled work may be involved. | Record exact timestamps and compare them with CloudLinux usage, application logs and the Service Status page. |
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
- Fix a 404 Not Found error
- Read website access and error logs
- Find a website document root
- Create a website redirect
- Add another website or domain in SiteWorx
Last reviewed: 2026-07-18.
