Setting up StoreAgent on a new host, a multisite network or a locked-down server? Check these requirements first. This article covers the minimum versions, WooCommerce compatibility, the outbound connections StoreAgent needs, and how to fix 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.
- WooCommerce installed and active. StoreAgent is built for WooCommerce stores, so it won’t activate without it.
- HTTPS on your site. The plugin talks to the StoreAgent platform over secure connections only.
- Outbound HTTPS to
app.storeagent.aiandapi.storeagent.ai. If your host blocks outbound traffic by default, allowlist both domains so the plugin can connect. - At least 128 MB PHP memory limit. 256 MB is recommended on catalogs over 1,000 products.
WooCommerce compatibility
StoreAgent works with both of WooCommerce’s order storage options: High-Performance Order Storage (HPOS) and the older posts-based storage. From version 1.2.3, StoreAgent declares HPOS compatibility to WooCommerce, and it is tested up to WooCommerce 11.3.
You can check the order storage your store uses under WooCommerce > Settings > Advanced > Features.
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
On some LiteSpeed setups, StoreAgent versions before 1.1.4 could lock you out of wp-admin. Those setups blocked the plugin from reading its own version from the plugin file. Version 1.1.4 fixed this, and the plugin no longer reads that file.
If you’re on LiteSpeed and seeing wp-admin lockouts:
- Update StoreAgent to version 1.1.4 or later under Plugins > Installed Plugins.
- If you can’t reach wp-admin to update, deactivate StoreAgent over SFTP. Rename the
storeagent-ai-for-woocommercefolder underwp-content/plugins, log in, and update through WordPress. Then restore the folder name and reactivate the plugin. - If the problem continues on version 1.1.4 or later, ask your host whether LiteSpeed’s mod_security or file-access rules block PHP file reads. Hosts can usually allowlist the 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 account, has its own AI Memory index, and works on its own.
- Network activation works. The plugin becomes available on every site in the network, but each site still needs to connect its own StoreAgent account from StoreAgent > Settings > Connection.
- AI Memory is per site. A product indexed on site A is not visible to the AI Chat Bot on site B. The same goes for chat history and settings.
- Usage is per StoreAgent account. If two sites in the network share one StoreAgent account, they share that plan’s AI Tasks and AI chat replies.
For typical multisite setups, such as a parent network with brand sub-sites or staging copies of a main site, connect each site separately to keep their AI data apart.
Outbound connectivity requirements
StoreAgent makes HTTPS calls to the StoreAgent platform for its AI features: AI Tasks, AI Chat Bot replies, AI Memory uploads and plan checks. MCP settings and connections use a second domain. If your host firewalls outbound traffic by default, allowlist:
app.storeagent.aion port 443 (HTTPS)api.storeagent.aion port 443 (HTTPS), used by MCP
To test outbound access, run this from your server:
curl -I https://app.storeagent.ai
A clean response, such as HTTP/2 200, means outbound access works. A timeout or DNS error means 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 outbound traffic.
Troubleshooting server-related issues
wp-admin loads slowly or times out after activating StoreAgent
Increase your PHP memory limit to 256 MB, and confirm with curl that your server can reach app.storeagent.ai. Your host’s documentation explains how to raise the memory limit. If both check out, deactivate other heavy plugins one at a time to find a conflict.
Your StoreAgent account does not connect
Run three checks:
- Confirm your site uses HTTPS. An http-only site can’t talk to the StoreAgent platform.
- Confirm your server can reach
app.storeagent.ai. - Check the WordPress error log for cURL or DNS errors.
AI Memory uploads are failing on a multisite network
Stop any sync of saai_* option keys between sites, then run Clear Post Data Hashes from StoreAgent > Settings > Tools on each site. The plugin stores each site’s upload status in that site’s own options, so a mu-plugin or sync tool that shares those options confuses the status tracking.
Frequently asked questions
Can I run StoreAgent on a staging site?
Yes. Connect the staging site to a separate StoreAgent account, or to the same account if you don’t mind staging usage counting toward your plan. Many teams use a separate StoreAgent account on the free Lite plan for staging.
Does StoreAgent work behind a reverse proxy or a CDN like Cloudflare?
Yes. The plugin’s calls to the StoreAgent platform go out from your server, not through your CDN. The AI Chat Bot widget script loads in your visitors’ browsers from app.storeagent.ai, so if your site sends a Content Security Policy, allow that domain. For MCP, StoreAgent also connects in to your store. See how to connect ChatGPT or Claude to your store with MCP for the firewall rule to add.
What if I’m on PHP 7.4? Should I upgrade?
StoreAgent supports PHP 7.4, but WordPress recommends PHP 8.3 or later for security and performance. If you have a choice, upgrade. PHP 7.4 reached end of life in November 2022 and no longer gets 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
