Plugin and server conflicts
Firewalls, caching, security plugins and hosting limits that interfere with Aimogen Pro, and how to identify and fix each.
Web application firewalls#
The most common source of conflicts, and the most confusing because the plugin sees a generic failure.
/wp-json/ blocked#
Symptoms. The REST API returns 404 or 403. Webhooks fail. The MCP server cannot be reached.
Fix. Allowlist the plugin routes:
/wp-json/aiomatic/v1/*
/wp-json/omniblock/v1/*
/wp-json/aiomatic-mcp/v1/*For Sucuri specifically, the MCP screen documents the exact steps: Security › Security Rules ›
Create Rule › Custom Rules, match URI /wp-json/aiomatic-mcp/v1/*, action Skip, select every WAF
component including those under "More components to skip", then Deploy.
admin-ajax.php blocked or rate-limited#
Symptoms. The chatbot does nothing. Front-end forms do not submit. Editor AI actions fail.
How to diagnose. Open the browser developer console. A failing request to admin-ajax.php with 403
points at a firewall; a 200 with an error payload points at the API.
Fix. Allowlist admin-ajax.php for the plugin actions, or raise the rate limit. WAF rules that
count POSTs per visitor frequently block a normal conversation.
Outbound requests blocked#
Symptoms. Every provider call fails with a network error.
How to diagnose. System & Logs › System Info — the Remote POST and Remote GET lines.
Fix. Ask your host to permit outbound HTTPS to the provider domains. Some security plugins proxy or
block wp_remote_*; test with them deactivated.
Caching#
Page caching serving stale chatbot responses#
Fix. Exclude admin-ajax.php from page cache. Also exclude /wp-json/aiomatic/* and
/wp-json/omniblock/* if you use them.
LiteSpeed#
Exclude the chatbot AJAX actions from both page cache and ESI.
Object caching#
Beneficial, and used deliberately — the Snippets Engine caches its active list for
60 seconds in the aimogen group. If snippet changes take a minute to appear, that is why.
[aicontent] appearing not to update#
Not a caching plugin — the shortcode caches its own result for 30 days by default. See The aicontent shortcode.
Security plugins#
Common interference:
| Behaviour | Effect |
|---|---|
Blocking admin-ajax.php | Chatbot and forms fail |
Blocking /wp-json/ | REST, webhooks and MCP fail |
Proxying wp_remote_* | Provider calls fail |
| Disabling the REST API entirely | Same |
| Blocking file uploads | Chatbot uploads and dataset uploads fail |
| Rate limiting by IP | Legitimate chatbot use blocked |
How to isolate. Deactivate the security plugin, retest, reactivate. If that fixes it, work through its rules rather than leaving it off.
Hosting limits#
| Limit | Symptom | Fix |
|---|---|---|
max_execution_time | Generation dies at a consistent number of seconds | Raise to 300 |
memory_limit | Fatal errors during scraping or image work | Raise to 256M+ |
max_input_vars | Settings silently revert on save | Raise to 5000 |
post_max_size / upload_max_filesize | Uploads fail | Raise both |
| Process limits | Runs killed mid-way, leaving stale run locks | Reduce batch sizes, use WP-CLI |
| Outbound allowlists | Provider calls fail | Ask the host |
Other plugins#
Two SEO plugins active#
Only the higher-priority one receives generated metadata. Detection stops at the first match. See SEO plugins.
Page builders and the AI Content Editor#
Editing Gutenberg or Elementor content without block support flattens the layout. Enable the matching block support first. See AI Content Editor.
Other AI plugins#
Several may register conflicting Connectors handling on WordPress 7. The
aiomatic_wp_ai_connectors_known_managers filter exists for exactly this. See
WordPress 7.0 Connectors.
Cron optimisation plugins#
Some clear scheduled events. Reactivating Aimogen Pro re-registers them. See Scheduled tasks do not run.
Featured image plugins#
FIFU is detected and handled. Other featured-image plugins may conflict over the same meta.
Isolating any conflict#
- Reproduce it reliably.
- Switch to a default theme. Retest.
- Deactivate other plugins. Retest.
- Reactivate one at a time, retesting after each.
- Check Activity Logs once you have the culprit.
On staging if at all possible.
Multisite#
- Licensing is network-wide; the updater runs on the main site only.
- Settings are per-site. Configuring one site does not configure the others.
- The capability is granted per site.
- Every site draws on the same provider quota unless each has its own keys.
Related#
Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.