Identify whether the loop comes from WordPress URLs, HTTPS detection, a plugin, proxy or conflicting web-server rules.
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
- Record the redirect chain with a browser network panel or command-line request rather than relying only on the final browser error.
- Confirm the WordPress Address and Site Address use the intended hostname and scheme.
- Check whether a CDN, proxy or load balancer terminates HTTPS and whether WordPress receives the correct forwarded protocol information.
- Temporarily disable only redirect, security or caching plugins likely to alter the request.
- Review .htaccess and SiteWorx redirect rules for duplicate HTTP-to-HTTPS, www or path redirects.
- Clear every relevant cache and test one canonical hostname directly.
- Restore required security redirects one layer at a time after the site responds normally.
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
- Redirect a website from HTTP to HTTPS
- Create a website redirect
- Configure and clear WordPress caching safely
- Browser reports an SSL or certificate error
- Diagnose a WordPress database connection error
Last reviewed: 2026-07-18.
