​
Connection Issues

​
Register Token Does Not Work

Check these first:
  • the token was created for the exact site URL you are connecting
  • there are no extra spaces from copy and paste
  • you are using the current register token flow, not an older long-lived API key assumption
If the token is accepted but the site still does not connect, inspect: 
wp option get wthb_options --format=json
Look for fields such as:
  • token
  • site_id
  • connected
  • last_error

​
Account Creation Succeeds But Site Is Not Yet Connected

This usually means account creation completed, but the pairing flow has not finished yet. Remember the current plugin behavior:
  • Create Account may return a register token
  • you still need Continue to Dashboard to save that token and complete the first connection heartbeat
  • some responses may instead ask you to check your email

​
Heartbeat Issues

​
Last Successful Heartbeat Is Not Updating

Check:
  • whether the site is connected
  • whether heartbeat monitoring is paused
  • whether the WordPress server can reach the Watchman Tower API endpoints
Helpful inspection command: 
wp option get wthb_options --format=json
Focus on:
  • connected
  • pause
  • last_success
  • last_error

​
Authentication Errors

The current plugin uses a staged auth model:
  • initial connection uses a register token
  • later requests use the stored site_id and hmac_secret
If you see unauthorized behavior:
  • confirm the site is still paired in Watchman Tower
  • confirm local pairing data still exists
  • try unlinking and reconnecting with a fresh register token

​
WT-Triggered Endpoint Problems

The plugin exposes: 
/wp-json/wt/v1/heartbeat
If Watchman Tower cannot trigger that route successfully, check:
  • the site is connected
  • the stored site_id and hmac_secret still exist
  • WordPress REST routes are reachable
  • reverse proxy or firewall rules are not interfering

​
Dashboard Issues

​
Connected Screen Looks Incomplete

The current connected screen is intentionally small. It should show:
  • connected badge
  • instance ID
  • site ID
  • last successful heartbeat
  • optional last error
  • interval and pause controls
  • unlink action
  • Quick Actions status snapshot
If you expect a separate manual heartbeat button or a large analytics workspace, that is a docs mismatch rather than current plugin behavior. When in doubt, this is the safest reset flow:
  1. inspect wthb_options
  2. unlink the site from the plugin
  3. generate a fresh register token
  4. reconnect from I Already Have an Account
  5. confirm site_id, connected, and last_success are present

​
Next Steps