Use the least disruptive recovery method and confirm that the mailbox and administrator account are legitimate before resetting access.
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
- Open the normal WordPress lost-password page and request a reset for the known administrator email address or username.
- Check the mailbox, spam folder and email-delivery logs before submitting several repeated reset requests.
- If WordPress email is not working, identify the correct administrator user through the database or a trusted command-line tool rather than changing an arbitrary account.
- Reset only the password field using a supported WordPress method, then sign in and immediately replace any temporary credential with a generated password.
- Review all administrator users, active sessions, application passwords and recently installed plugins to determine whether the lockout was caused by compromise.
- Repair outbound mail so future password resets and security notices are delivered reliably.
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 login page keeps rejecting the details. | The wrong email address, an old password, browser autofill or an account-specific lockout is being used. | Type the account email manually, use the password-reset process once and avoid repeated attempts that may extend a lockout. |
| A one-time code is not accepted. | The device clock is inaccurate, the code belongs to a different account or an older code was entered. | Set the device time automatically, wait for a fresh code and confirm the authenticator entry name before trying again. |
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
- Configure WordPress to send mail through authenticated SMTP
- Manage a database with phpMyAdmin
- Recover a compromised WordPress website
- Secure hosting and application passwords
- Troubleshoot a WordPress contact form that does not send
Last reviewed: 2026-07-18.
