FAQ
Can I connect a site without moving hosting to TMXIO?
Section titled “Can I connect a site without moving hosting to TMXIO?”Yes. That is the main purpose of the TMXIO WordPress Plugin. The plugin connects a self-hosted WordPress site running on any compliant host to TMXIO so you can manage, monitor, and back it up without changing where it lives. You only move hosting if you specifically want TMXIO to host the site as well.
Should I use a workspace token?
Section titled “Should I use a workspace token?”Only if you are working with an older or fallback flow. The current plugin experience centers on creating a TMXIO account from WordPress or validating an API key. If your internal notes still describe a “paste a workspace token” path as the default, update them — the plugin has not used that as the primary path for some time.
What is the first thing I should do if the site looks disconnected?
Section titled “What is the first thing I should do if the site looks disconnected?”Run Test Connection from the plugin in WordPress admin. It runs the same code path as a regular heartbeat, so a success tells you the next scheduled heartbeat will almost certainly land, and a failure shows you exactly which part of the path is broken.
What does Error Monitoring do?
Section titled “What does Error Monitoring do?”It allows TMXIO to collect operational error data from the WordPress install so support can help diagnose problems without asking you to ship log files manually. It is opt-in and can be turned off at any time. For the privacy and data-collection policy behind that feature, see What Information Do We Collect?.
What does 1-Click Access do?
Section titled “What does 1-Click Access do?”It allows quick, secure admin access from TMXIO when enabled, so an operator can open WordPress admin without typing a username or password. It is opt-in. See Understanding TMXIO 1-Click Access for the full customer-facing explanation.
Does TMXIO exclude any tables from backups?
Section titled “Does TMXIO exclude any tables from backups?”Yes. TMXIO excludes a small set of operational log tables by default today and has a larger reviewed list of plugin-specific log tables that support may recommend excluding when they are not part of the site’s authoritative data. See Backup Exclusions for the current default list and the additional reviewed candidates.
Do I need to reconnect after every plugin update?
Section titled “Do I need to reconnect after every plugin update?”No. Updating the plugin in WordPress does not break the connection. The connection state is stored independently of the plugin’s files, and the new version reads the existing state on first load. You only need to reconnect when credentials change or the site moves to a new host.
How quickly will TMXIO notice if a site goes down?
Section titled “How quickly will TMXIO notice if a site goes down?”The plugin heartbeats once a minute. After three consecutive missed heartbeats the site is marked degraded; after ten it is marked disconnected. See Heartbeat and Status for the full status model.
Will the plugin work on a site behind HTTP auth?
Section titled “Will the plugin work on a site behind HTTP auth?”Yes, but the auth wall needs to allow TMXIO to reach /wp-json/. Either whitelist TMXIO’s outbound path or relax the wall for the plugin’s API namespace. See the HTTP Auth tab in Troubleshooting for a cURL command you can use to confirm the wall is the problem.
What happens if I delete the plugin without disconnecting first?
Section titled “What happens if I delete the plugin without disconnecting first?”The site will continue to show as connected in TMXIO until ten heartbeats have been missed, at which point it will transition to disconnected on its own. If you want it removed from the dashboard sooner than the natural timeout, contact support with the workspace and site URL.