Troubleshooting & FAQ

← Security & API Keys · Home

Troubleshooting #

Claude says it can’t reach / connect to my site #

• Local site + claude.ai (cloud) or Claude Desktop: neither can reach a .local/localhost address — both broker connector requests through Anthropic’s servers. A trusted local HTTPS cert does not help (the issue is reachability). Use a tunnel (e.g. cloudflared), or connect with Claude Code on the same machine (it works locally; the Desktop app does not). See Connecting a local site.
• Wrong/expired key: if you regenerated the key, the old MCP URL stopped working. Copy the current MCP URL from Divi Connect → Connection and update the connector.
• Not HTTPS: claude.ai requires a reachable https:// URL.
• Security plugin / firewall: a WAF or security plugin may block requests. Allow the /wp-json/divi-connect/v1/ routes.

The connector was added but Claude has no tools #

• Start a new chat after adding the connector.
• Make sure the connector is enabled in Claude’s connector settings.
• In Claude Code, run /mcp to confirm divi-connect is listed and connected.

Claude Code asks permission for the wrong site’s connector #

If you have several sites, each with its own Divi Connect connector, Claude Code
can occasionally ask permission for a different connector than the one you meant.
This is Claude Code’s connector picker (client-side), not the plugin. Two things help:

• Each Divi Connect connector names itself by site — the permission prompt shows
  Divi Connect - <Your Site Name> (yourdomain.com), so you can tell them apart and
  approve the one matching the site you’re working on.
• If Claude Code still reaches for the wrong one, deny it and send your request
  again — it then asks for the correct connector.

A design-system push fails with “No Divi theme is active” / “needs Divi 5” #

Divi Connect checks for an active Divi 5 theme before writing colors, variables or
presets. If you see this, the site either has no Divi theme active (install &
activate Divi) or is on Divi 4 (update to Divi 5.0+). The plugin also shows a
warning banner on the Divi Connect and Plugins screens until Divi 5 is active.

I updated Divi Connect but Claude can’t see the new tools/features #

Claude caches the connector’s tool list from when you connected, so after an update it keeps using the old tools until you reconnect — which makes new features look “missing,” or Claude will say it can’t do something it now can. Fix: disconnect and reconnect the connector (claude.ai / Desktop → Connectors; Claude Code → remove and re-add), then start a new chat. After reconnecting you should see more tools than before. See Connecting Claude → After updating.

Tools intermittently hang / time out (then a retry works) #

Fixed in 1.7.5 for the most common trigger. The biggest single cause was divi_get_rendered_page: to show you a page it used to make the site fetch its own URL (a loopback), which needs a second PHP process at the same time — enough to exhaust a small hosting plan and produce hangs or 503 errors. As of 1.7.5 that tool renders the page in-process with no loopback, which removes the connector’s own contribution to the stall (reproduced on a real shared host: 503s eliminated, ~3.5× faster under load). Update to 1.7.5 and reconnect if you’re hitting this.

Any remaining intermittent hangs — calls that stall then succeed on retry, not tied to page size or one tool — are on the hosting side, below the connector. Common causes: too few PHP‑FPM workers (one slow request starves the rest), WordPress running its cron on page loads (WP‑Cron), or a slow ping from another plugin. Checks, quickest first:

• Run real cron instead of on-request cron. In wp-config.php add define('DISABLE_WP_CRON', true); and add a real server cron hitting wp-cron.php every few minutes. This stops random visitor/tool requests from blocking while WP runs scheduled jobs.
• Give PHP more workers. On managed/cheap hosts the PHP‑FPM pool can be very small (2–4). Raising pm.max_children (or moving off a starved plan) removes the “one slow request blocks everything” pattern.
• Add persistent object caching (Redis/Memcached) if the host offers it — cuts repeated option/query cost.
• Retry is usually safe for reads and edits; see the retry‑safety note below before re‑running a create/delete.

Is a timed‑out call safe to retry? A timeout means the client gave up waiting — the server may still have finished. So it’s per‑tool:

Deeper host‑side diagnosis (for site admins) is in docs/TIMEOUTS-DIAGNOSIS.md.

“Invalid Divi Connect key in connector URL” #

The key in your MCP URL doesn’t match the site. Recopy the MCP URL from the settings page (it may have been regenerated or copied incompletely).

Claude built a page but it looks blank or broken #

The plugin validates markup and rejects malformed pages, so a published page should render. If something looks off, ask Claude to rebuild it as a draft and review it in the Divi builder, or tell Claude exactly what’s wrong (“the hero section is empty”) so it can fix the markup.

Saving a global preset fails in the Divi builder (site-wide) #

If the Divi builder suddenly refuses to save any global preset, one malformed preset in your store is likely blocking them all. Just tell Claude “repair my presets” — it normalises every preset back to the current format without changing your styling, which unblocks saving. (Newer builds also clean presets as they’re saved, so this shouldn’t recur.)

A Pro feature returns an error / “402” #

That feature (editing colors/variables/presets, Theme Builder, global layouts, WooCommerce pages, or linked size variables) requires Divi Connect Professional. See Free vs Pro.

I changed a size token but my Free-plan page didn’t update #

On Free, size variables are baked into the page at build time. Upgrade to Professional to keep them linked, or ask Claude to rebuild the page. See the explanation here.

I deleted a page by mistake #

Pages are moved to Trash by default (not permanently deleted). Recover it from WordPress → Pages → Trash. Only a page deleted with explicit “permanent” confirmation is unrecoverable.

FAQ #

Does it work with a free Claude account?
Yes. Free claude.ai accounts can add the custom connector and build pages.

Does my site need to be publicly reachable?
For claude.ai (cloud) and the Claude Desktop app, yes — both broker requests through Anthropic’s servers, so the connector URL must be publicly reachable over HTTPS (use a tunnel for a local site). Only Claude Code running on your own machine can use a local site directly.

Does it require Divi 5?
Yes. Divi Connect targets the Divi 5 builder (5.7+). It does not work with the Divi 4 / legacy builder.

Is it secure?
Each site has its own secret connector key, shown in Divi Connect → Connection, and you can regenerate it at any time to instantly invalidate the old one. See Security & API Keys.

Will it change or delete my existing design system?
No. Reading the design system never changes it. Editing it (a Pro feature) only happens when you explicitly ask Claude to. Uninstalling the plugin removes only the plugin’s own settings, never your Divi data.

Can I use it on multiple sites?
Yes — install it on each site. Each gets its own connector. The Pro 1 / 5 / Unlimited plans (and Lifetime, which is unlimited) cover how many sites can use the Pro features at once.

Can Claude edit a page it already built?
Yes — ask it to make changes and it will update the page. You can also keep editing in the Divi builder as normal.

What happens to my pages if I deactivate the plugin?
Your pages are normal Divi pages — they stay exactly as they are. The plugin only provides the connection; it isn’t required to display pages it built.

Still stuck? #

• Re-check Divi Connect → Connection and recopy the current MCP URL.
• Try the Quick test curl command on the settings page to confirm the API responds.
• Contact support via divilove.com. Never include your full connector URL or API key in a public message — regenerate it first if you think it leaked.

← Security & API Keys · Home