A 500 error usually indicates an application, PHP, permissions or configuration failure.
Applies to: Web Hosting troubleshooting
Troubleshooting is fastest when you identify the layer that failed: DNS, TLS, web server, PHP, application, database or local device. Record exact error text and timestamps before changing configuration.
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.
Work through these checks
- Check the domain error log at the time of the request.
- Temporarily reverse the most recent application or configuration change.
- Check supported PHP version and permissions.
- Rename a suspect .htaccess file only for a controlled test.
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
- Troubleshoot a blank or white page
- Read website access and error logs
- Fix a 403 Forbidden error
- Fix a 404 Not Found error
- Website not loading after a DNS change
Last reviewed: 2026-07-18.
