Remove a stale maintenance marker only after confirming that no update process is still writing files or changing 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
- Wait several minutes and reload the administration area once; a legitimate update can finish without intervention.
- Check running tasks and recent file timestamps to confirm that no plugin, theme or core update is still active.
- Use SiteWorx File Manager or FTP over TLS (FTPS) to locate the .maintenance file in the WordPress document root.
- Download a copy for reference, then remove only the stale .maintenance file.
- Open /wp-admin/upgrade.php if WordPress requests a database upgrade and complete it once.
- Verify the site and administration area, then update any component that failed using a fresh package rather than rerunning all updates together.
- Review logs and available storage if the condition returns, because a timeout or full account can interrupt update extraction.
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 |
|---|---|---|
| WordPress shows a critical error or blank page. | A plugin, theme, PHP version or exhausted resource caused a fatal error. | Check the PHP error log, disable only the last changed component and restore a known-good copy if the administration area is unavailable. |
| The site works until cache is cleared or a plugin updates. | Generated cache, stale object data or incompatible code is masking the underlying fault. | Test with caching disabled on a staging copy, update one component at a time and confirm PHP compatibility before re-enabling cache. |
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
- Use the SiteWorx File Manager
- Diagnose a WordPress plugin or theme conflict
- Check website, database and email storage usage
- View website and error logs
- Configure and clear WordPress caching safely
Last reviewed: 2026-07-18.
