Determine whether the problem is form validation, WordPress processing, SMTP authentication, DNS policy or recipient filtering.
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
- Submit the form once with a distinctive subject and note the exact UTC time, sender, recipient and confirmation shown by the site.
- Check the form plugin’s submission log or stored entries to confirm whether WordPress accepted the form data.
- Verify that the To address is valid and the From address belongs to an authorised domain rather than using the visitor’s address as the sender.
- Send an authenticated SMTP test through the same WordPress mail configuration.
- Check the recipient mailbox, spam filtering, quarantine and mail logs for the test timestamp.
- Review SPF, DKIM and DMARC alignment when delivery succeeds to some providers but not others.
- Add rate limiting or CAPTCHA if the form is being abused, but keep an accessible alternative contact route for legitimate visitors.
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
- Configure WordPress to send mail through authenticated SMTP
- Troubleshoot hosting email sending and delivery
- Roll out DMARC safely from monitoring to enforcement
- Protect forms and public sites from abuse
- Recover a WordPress administrator password
Last reviewed: 2026-07-18.
