Restore files and the database from compatible points and verify configuration, URLs and scheduled work afterwards.
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.
- Download anything that must be retained and confirm whether the action is reversible.
Step-by-step
- Identify the incident time and choose file and database recovery points from the same period where possible.
- Preserve the current broken state and database before overwriting it in case recent content must be recovered separately.
- Restore website files to the correct document root and confirm file ownership and permissions.
- Restore the matching database and verify wp-config.php still contains the correct database name, user, password and table prefix.
- Clear WordPress, browser and proxy caches and run any required database upgrade once.
- Test administration, media, forms, scheduled tasks and transactional actions; do not rely on the home page alone.
- Rotate credentials and patch the root cause when the restore followed compromise rather than accidental deletion.
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 restored site opens but behaves incorrectly. | Files and database were restored from different times, cached data is stale or configuration still points to the old location. | Align the restore points, clear application caches and verify URLs, credentials and scheduled tasks before declaring recovery complete. |
| Recent data is missing. | The selected recovery point predates the change or the data was stored outside the backed-up location. | Stop making further changes, identify the required timestamp and ask support what recovery points remain available. |
Important notes
- Destructive or ownership-changing actions may be irreversible and can have billing or data-retention consequences. Confirm the target and authority before proceeding.
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
- Restore website files
- Restore a database
- Recover a compromised WordPress website
- Find database connection details
- Create and use a WordPress staging site
Last reviewed: 2026-07-18.
