StoreAgent runs on standard WordPress hosting, but a few server-side details matter — minimum versions, outbound network access, and how it behaves on multisite networks or specific stacks like LiteSpeed. This article covers the requirements, known compatibility issues, and how to diagnose the rare cases where the host gets in the way.
Minimum requirements
- WordPress 5.9 or later. Older WordPress versions are not supported.
- PHP 7.4 or later. PHP 8.0, 8.1, 8.2, and 8.3 are all supported.
- WooCommerce installed and active. StoreAgent is built specifically for WooCommerce stores — it won’t activate without it.
- HTTPS on your site. The plugin talks to the StoreAgent.ai platform over secure connections only.
- Outbound HTTPS to
app.storeagent.ai. If your host blocks outbound traffic by default, allowlist that domain so the plugin can connect. - At least 128 MB PHP memory limit. 256 MB is recommended on catalogs over 1,000 products.
Hosting compatibility
StoreAgent works on every major WordPress host we’ve tested — SiteGround, WP Engine, Kinsta, Pressable, Bluehost, Hostinger, Cloudways, and shared LAMP hosts. The plugin has no host-specific code paths, so if your site can run WooCommerce, it can run StoreAgent.
LiteSpeed servers
Some LiteSpeed configurations historically blocked file_get_contents() calls on plugin headers, which caused wp-admin to become inaccessible while StoreAgent was active. This was tracked as issue #402 and fixed in v1.1.6 — the plugin now uses a hardcoded version constant instead of reading the plugin header dynamically, so the file read is never attempted.
If you’re on LiteSpeed and seeing wp-admin lockouts:
- Update StoreAgent to v1.1.6 or later under Plugins → Installed Plugins.
- If you can’t reach wp-admin to update, deactivate StoreAgent via SFTP (rename the
storeagent-ai-for-woocommercefolder underwp-content/pluginsto anything else), log in, update via the WordPress UI, then restore the folder name and reactivate. - If the issue persists on v1.1.6+, ask your host to confirm whether LiteSpeed’s mod_security or file-access rules are blocking PHP file reads. The hosting team can usually allowlist your plugin folder.
Multisite networks
StoreAgent is multisite-compatible but designed as a per-site integration, not a network-wide one. Each site in the network connects to its own StoreAgent.ai account, has its own AI Memory index, and operates independently.
- Network activation works — the plugin will be available on every site in the network — but each site still needs to connect its own StoreAgent.ai account from StoreAgent → Settings → Connection.
- AI Memory is per-site. A product indexed on site A is not visible to the chat bot on site B. Same for chat history, settings, and credit usage.
- Credits are per StoreAgent.ai account. If two sites in the network share one StoreAgent.ai account, they draw from the same credit pool.
For typical multisite use cases (a parent network with brand sub-sites, or staging mirrors of a main site), connect each site separately to keep their AI data isolated.
Outbound connectivity requirements
StoreAgent makes HTTPS calls to the StoreAgent.ai platform for every AI request — agent runs, chat replies, memory uploads, plan-status checks. If your host firewalls outbound traffic by default, allowlist:
app.storeagent.aion port 443 (HTTPS)
Test outbound access from your server:
curl -I https://app.storeagent.ai
A clean response (e.g. HTTP/2 200) means outbound connectivity is fine. A timeout or DNS error indicates your host needs to allowlist the domain. Hosts like WP Engine and Pressable tend to be open by default; some shared hosts and corporate networks block aggressively.
Troubleshooting server-related issues
wp-admin loads slowly or times out after activating StoreAgent
Usually a memory or outbound-connectivity issue. Increase your PHP memory limit to 256 MB (your host’s documentation should explain how), and confirm app.storeagent.ai is reachable via curl from the server. If both check out, deactivate other heavy plugins one at a time to isolate any conflict.
“Failed to connect to StoreAgent” during account connection
Three checks: confirm your site is on HTTPS (an http-only site can’t talk to the StoreAgent.ai platform); confirm app.storeagent.ai is reachable from the server; and check the WordPress error log for any cURL or DNS errors. Most “failed to connect” errors trace back to one of these.
“Could not check plugin version” warning on activation
This was the LiteSpeed-specific symptom of issue #402, fixed in v1.1.6. If you’re on the latest version and still seeing it, file a support ticket with your host’s name and PHP version — there may be a new variant of the same protection.
AI Memory uploads are failing on a multisite network
The plugin stores per-site state in options on each blog. If sites share configuration via a mu-plugin or sync mechanism, this can confuse the upload status tracking. Disable any sync of saai_* option keys and run a Clear Post Data Hashes from StoreAgent → Settings → Tools per site to reset.
Frequently asked questions
Can I run StoreAgent on a staging site?
Yes. Connect the staging site to a separate StoreAgent.ai account (or to the same account if you don’t mind staging usage counting against your plan credits). Most teams use a dedicated trial-tier StoreAgent.ai account for staging.
Does StoreAgent work behind a reverse proxy / CDN like Cloudflare?
Yes — the plugin’s outbound calls go from your server, not through your CDN. Cloudflare and similar services in front of your site don’t affect StoreAgent’s ability to talk to the StoreAgent.ai platform. The chat widget loads JavaScript from your own site, so CDN page rules apply to it the same way they apply to any other plugin asset.
What if I’m on PHP 7.4 — should I upgrade?
StoreAgent supports PHP 7.4, but WordPress recommends PHP 8.1 or later for security and performance. If you have a choice, upgrade — PHP 7.4 reached end-of-life in November 2022 and is no longer receiving security patches.
Need help?
If you have a question or run into any issues, we’re here to help.
- Premium users: Open a support ticket
- Free users: Visit our community forum
