Troubleshooting Guide
Solutions to common issues with WooAI Chatbot Pro. Find your problem below and follow the step-by-step fix.
Before diving into specific issues, run through this checklist:
- Plugin is activated and license is valid
- AI provider API key is configured and tested
- Browser console shows no JavaScript errors
- Server PHP version is 7.4 or higher
- WordPress and WooCommerce are up to date
- Caching plugins are cleared after changes
Widget Issues
- Widget is disabled in settings
- Current page is in "Hide on Pages" list
- JavaScript conflict with theme or other plugins
- Ad blocker is blocking the widget script
- Go to WooAI Chat → Settings and verify "Enable Widget" is ON
- Check "Hide on Pages" setting - remove current page if listed
- Open browser console (F12) and look for JavaScript errors
- Disable ad blocker temporarily to test
- Try switching to a default WordPress theme (Twenty Twenty-Four)
- Deactivate other plugins one by one to find conflicts
- JavaScript not fully loaded
- CSS z-index conflict (something covering the widget)
- Event handlers not attaching properly
- Wait for page to fully load before clicking
- Check browser console for errors
- Inspect the widget element - look for overlapping elements
- Add this custom CSS:
.wooai-chat-launcher { z-index: 999999 !important; } - Clear all caches and hard refresh (Ctrl+Shift+R)
- Theme has fixed elements in the same position
- Offset values need adjustment
- Other floating widgets (like cookie notices) conflicting
- Go to WooAI Chat → Appearance
- Try changing position from Bottom Right to Bottom Left (or vice versa)
- Increase offset values (try 30-50px instead of 20px)
- Use custom CSS to fine-tune position if needed
AI Provider Issues
- API key was copied incorrectly (extra spaces)
- API key has been revoked or expired
- Using wrong type of key (service key vs. public key)
- Go to your AI provider's dashboard and generate a new API key
- Copy the key carefully - no spaces before or after
- For Gemini: Use key from Google AI Studio (not Google Cloud)
- For OpenAI: Key should start with
sk- - For Claude: Key should start with
sk-ant- - Paste the new key and save settings
- Use "Test Connection" button to verify
- Too many requests in a short time
- Exceeded monthly/daily quota
- Free tier limits reached
- Wait 1-2 minutes and try again
- Check your provider's usage dashboard for quota status
- Configure a fallback provider in WooAI settings
- Consider upgrading to a paid tier for higher limits
- For Gemini free tier: 60 requests/minute limit
- Using a slow/heavy AI model
- Large system prompt or context
- RAG search taking too long
- Network issues between your server and AI provider
- Switch to a faster model:
gemini-1.5-flashorgpt-4o-mini - Reduce system prompt length (keep under 500 words)
- In RAG settings, reduce "Max Results" to 3
- Increase similarity threshold to reduce search time
- Test AI directly via provider's console to isolate network issues
- RAG is not configured or disabled
- Products not indexed in Supabase
- Similarity threshold too high (missing results)
- Product descriptions are too short
- Go to WooAI Chat → RAG & Search and verify it's enabled
- Check the indexed product count - should match your catalog
- Click "Reindex All Products" to refresh the index
- Lower similarity threshold to 0.6 for more results
- Add more detailed product descriptions in WooCommerce
RAG & Supabase Issues
- Incorrect Supabase URL or API key
- Supabase project is paused (free tier inactivity)
- Server firewall blocking outbound connections
- Verify Supabase URL format:
https://xxxxx.supabase.co - Use the
anon(public) key, notservice_role - Log into Supabase and check if project is paused - restore if needed
- Contact your host if firewall is blocking port 443 outbound
- PHP timeout for large catalogs
- Memory limit exceeded
- Supabase rate limits hit
- Increase PHP max_execution_time to 300 in php.ini
- Increase PHP memory_limit to 256M or higher
- For large catalogs (1000+), index in batches using WP-CLI:
wp wooai index-products --batch=100 - Wait a few minutes between large batches
- Products not indexed or partially indexed
- Similarity threshold too high
- Product descriptions don't match search terms
- Use the "Test Search" feature in RAG settings
- Lower similarity threshold to 0.5 temporarily for testing
- Click "Reindex All Products" to refresh
- Add relevant keywords to product descriptions
- Include common synonyms (e.g., "running shoes", "jogging sneakers")
License Issues
- License key copied incorrectly
- License already used on another site
- Server cannot reach license server
- Copy license key again from your purchase email
- Ensure no extra spaces before/after the key
- If transferring from another site, deactivate there first
- Check that your server allows outbound HTTPS connections
- Contact support if you need to reset your activation
Performance Issues
- Plugin conflict causing PHP slowdown
- Database queries not optimized
- Caching not configured properly
- WooAI widget loads asynchronously - should not affect page load
- If slow in admin, check for plugin conflicts
- Enable object caching (Redis/Memcached) if available
- Use Query Monitor plugin to identify slow queries
- Contact support with performance data if issue persists
Enable Debug Mode
For advanced troubleshooting, enable debug mode to see detailed logs:
WordPress Debug Log
Add these lines to your wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Logs will be saved to /wp-content/debug.log
WooAI Debug Mode
Enable in WooAI settings:
- Go to WooAI Chat → Settings → Advanced
- Enable "Debug Mode"
- Reproduce the issue
- Check debug.log for WooAI-specific entries
Remember to disable debug mode on production sites. Debug logs can contain sensitive information and may impact performance.
Server Requirements Check
Verify your server meets minimum requirements:
PHP Version: 7.4+ (8.0+ recommended)
WordPress: 6.0+
WooCommerce: 7.0+
Memory Limit: 128M+ (256M recommended)
Max Execution Time: 60+ seconds
cURL: Enabled with SSL
OpenSSL: 1.0.1+
Check your configuration in WordPress: Tools → Site Health → Info
Still stuck?
If you've tried the solutions above and still have issues, our support team is here to help.
When contacting support, please include: WordPress version, WooCommerce version, PHP version, error messages, and steps to reproduce.
Contact Support