Troubleshoot a WordPress Connection

Begin with the exact connection error and the time it occurred.

1. Confirm the public Website loads over HTTPS.
2. Open https://example.com/wp-json/ and confirm WordPress returns JSON.
3. Confirm the supported TMXIO plugin is active.
4. Check maintenance mode, basic authentication, IP restrictions, and security plugins.
5. Review CDN, firewall, rate-limit, and bot-protection events for the same time.
6. Confirm the connection belongs to the intended TMXIO Account and Website.
7. Retry one connection refresh.

For WordPress Multisite, confirm the connection was started from the intended Website’s dashboard rather than Network Admin. Network activation loads the plugin for every Website, but the main Website and each child Website have separate TMXIO connections—even when a subfolder network gives them the same hostname.

WordPress boundary

The boundary is likely WordPress when the REST API returns an error, HTML, or a redirect loop; WordPress has a fatal error; or the plugin cannot make normal outbound HTTPS requests.

Edge boundary

The boundary is likely edge protection when browser traffic succeeds but TMXIO requests receive challenges, access denials, or intermittent rate limits.

Do not disable protection permanently to make validation pass. Add the narrow rule required for supported TMXIO communication, then test again.

If the connection still fails, contact support with the domain, timestamp, exact error, and relevant redacted firewall event.