Verify credentials, server availability and table health before editing or restoring the database.
Applies to: WordPress on Tudor Internet Web Hosting
WordPress problems often come from the interaction between PHP, plugins, themes, caching, scheduled tasks and database state. Change one item at a time, record what you changed and keep a known-good backup before updates or repairs.
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
- Confirm whether every page fails and record the exact error; a plugin-specific database error may have a different cause.
- Compare DB_NAME, DB_USER, DB_HOST and the stored password in wp-config.php with the SiteWorx database and user records.
- Confirm the database user still has the required permissions to the intended database.
- Test a direct connection through phpMyAdmin or a controlled script without publishing credentials.
- Check account storage and database size because a full account can prevent temporary tables or writes.
- Review database error logs or table checks before running repair operations.
- Restore or repair only affected tables, then test writes such as login, form submission or content update.
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 application reports access denied. | The database user, password, host or granted permissions do not match the application configuration. | Confirm the exact prefixed database and user names in SiteWorx, reset the password if necessary and reapply the minimum required permissions. |
| An import stops or times out. | The file is too large, compressed incorrectly, contains incompatible SQL or exceeds execution limits. | Check the first reported SQL error, use a compressed export where supported and request assistance for a controlled command-line import rather than repeatedly retrying. |
| 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
- Find database connection details
- Manage a database with phpMyAdmin
- Check website, database and email storage usage
- Restore a database
- Configure and clear WordPress caching safely
Last reviewed: 2026-07-18.
