Skip to content

It Seems We Can't Communicate With Your WordPress API

TMXIO uses the WordPress plugin and API to confirm your site is reachable and authenticated. If that connection fails, the problem is usually one of a small number of things.

  • The site URL configured in WordPress is different from the public URL you expect TMXIO to use.
  • A firewall, security plugin, CDN rule, or basic-auth layer is blocking TMXIO requests.
  • The WordPress REST API is unavailable or returning an unexpected response.
  • The site connection credentials are outdated or saved against the wrong workspace or site.
  • Outbound or inbound HTTPS requests are failing because of SSL or DNS issues.
  1. Confirm the site loads publicly over HTTPS in a browser.
  2. Confirm the WordPress REST API responds:
https://your-site.example/wp-json/
  1. Make sure the TMXIO plugin is active and the site is still connected to the correct TMXIO workspace.
  2. Review any Cloudflare, WAF, rate limit, or bot-protection rules that could block API traffic.
  3. Disable maintenance mode, temporary basic auth, or IP restrictions and test again.

If You Use Security Plugins Or Edge Protection

Section titled “If You Use Security Plugins Or Edge Protection”

Temporarily allow:

  • wp-json/*
  • admin-ajax requests required by the plugin
  • inbound HTTPS requests from TMXIO services

If a firewall log shows blocked validation or connectivity requests, whitelist them and retry the connection test.

  • wp-json returns 403, 404, 500, or HTML instead of JSON.
  • The site has plugin conflicts, fatal errors, or REST API restrictions.
  • The server cannot make normal HTTPS requests because curl or SSL trust is broken.
  • The site works in your browser but TMXIO still fails intermittently.
  • Cloudflare or another CDN is showing bot or security challenges.
  • The public DNS record was changed recently and has not propagated yet.

Send support:

  • the site domain
  • whether the site is hosted by TMXIO or external
  • the exact error text you saw
  • any firewall or CDN rules that might block API traffic

That is usually enough for us to identify the failing step quickly.