Skip to content

WordPress troubleshooting

If something is not working, find the closest symptom below. If none of these resolve it, contact support.

Connect fails or the assistant shows fallback chrome

Section titled “Connect fails or the assistant shows fallback chrome”
  • Symptom: Connecting fails, or the assistant panel shows a fallback message instead of the chat.
  • Cause: The instance URL is wrong, the instance is unreachable, or the instance cannot mint short-lived tokens / has no mutually-supported contract version. The plugin requires server-side token exchange — there is no long-lived-key fallback.
  • Fix: Re-check the Cinatra instance URL on Settings → Cinatra, confirm the instance is reachable from your site, and confirm the instance has the matching token-exchange and capabilities endpoints deployed. Then run Connect with Cinatra again.
  • Symptom: No floating Cinatra button in wp-admin.
  • Cause: Your user is not a WordPress administrator, or the plugin is not active.
  • Fix: Confirm the plugin is active under Plugins, and confirm your user has the manage_options capability — the assistant is administrator-only.
  • Symptom: The assistant answers in chat but cannot edit content with tools.
  • Cause: The WordPress MCP Adapter is not installed or not active.
  • Fix: Install and activate the adapter, then re-check the adapter status indicator on Settings → Cinatra.
  • Symptom: A subscription target does not receive a post_published notification.
  • Cause: No subscription is registered for that case, or the site has no server-issued webhook signing credentials (for example the plugin was updated on an existing connection, or the Cinatra URL / instance ID changed).
  • Fix: On settings & permissions, confirm a subscription is registered and the Publish Webhooks status shows provisioned; if it does not, reconnect the site to your Cinatra instance (“Connect with Cinatra”) to provision the credentials. The plugin sends outbound signed webhooks only.
  • Re-read the quick start to confirm each setup step.
  • Check the WordPress plugin/PHP error log for plugin messages.
  • Contact support with the symptom, your WordPress version, and the plugin version.

Docs content licensed under CC-BY-4.0; embedded code snippets under Apache-2.0.