Plugin activates but “Yuko Integration” is missing from the WordPress sidebar
Possible causes, in order of likelihood:Browser or admin cache
Browser or admin cache
- Hard-refresh the WordPress admin page (Ctrl+Shift+R / Cmd+Shift+R)
- Log out and log back in
- Try a different browser or an incognito window
User role not Administrator
User role not Administrator
Yuko menu items are only visible to users with the
manage_options capability (Administrator role).Check Users → Your Profile → Role. If you’re an Editor or Shop Manager, ask a site admin to grant access.Plugin conflict
Plugin conflict
- Deactivate every non-essential plugin except Yuko and WooCommerce
- Check if the Yuko menu appears
- Reactivate plugins one at a time, checking after each, until the conflict surfaces
”Connection failed” when authenticating your store
Checklist:Store URL format is correct:
- Starts with
https://(nothttp://— Yuko requires SSL) - Uses your primary domain, not a staging preview URL
- Does not include
/wp-admin,/shop, or trailing slashes - Matches exactly what’s set in WordPress Admin → Settings → General → WordPress Address (URL)
https://yourstore.com
❌ http://yourstore.com/wp-adminPlugin and WooCommerce are both active:
- Yuko Integration shows “Active” under Plugins
- WooCommerce shows “Active” under Plugins
- Your shop page loads normally at the front end
Security isn’t blocking the handshake:Temporarily disable:
- WordFence / Sucuri / iThemes Security
- “Block REST API” rules in any security plugin
- Cloudflare’s “Under Attack” mode (drop to “Medium” for a minute)
app.yukoapp.com in your security rules permanently.REST API is reachable:Visit
https://yourstore.com/wp-json/yuko/v2/ in your browser. You should see a JSON response (possibly {"error":"unauthorized"} — that’s fine). A 404 or 500 means the REST API is blocked.If blocked, check Settings → Permalinks and re-save to refresh rewrite rules.”Invalid signature” error during authentication
This happens when the plugin and backend don’t agree on the HMAC signature. Usually caused by:- Clock drift — your server’s time is off by more than 5 minutes. Check with
dateon the server or a time-checking WordPress plugin. Contact your host if skewed. - Plugin reinstalled — the local secret key was regenerated but the backend still holds the old one. Disconnect from the Yuko dashboard (Account → Integrations → WooCommerce → Disconnect), then re-authenticate from WordPress.
- Two plugin installs on the same WP site — only one Yuko Integration install per site is supported.
”HTTPS required” error
Yuko requires HTTPS on the storefront. If you see this:- Install a free SSL certificate via your host (most hosts offer Let’s Encrypt one-click)
- Force HTTPS in Settings → General → WordPress Address (URL) — both fields must start with
https:// - Update any hardcoded
http://URLs with a plugin like Better Search Replace - Flush permalinks (Settings → Permalinks → Save)
- Re-authenticate in Yuko
Plugin upload fails with “file too large”
Your host’s PHPupload_max_filesize or post_max_size is too low.
- Ask your host to bump both to at least 10 MB, or
- Install via FTP instead (see Advanced installation in the install guide)
After a host migration, Yuko shows “Disconnected”
Moving your site between hosts changes file paths and often regenerates secrets. After migration:- Yuko Dashboard → Account → Integrations → WooCommerce → Disconnect
- WordPress Admin → Yuko Integration → Re-authenticate
- Confirm the new store URL (usually the same)
- Run a fresh sync
Need Help?
Book Free Setup Call
Talk to our team for personalized setup helpTime: 30 minutes
Contact Support
Reach our team at yukoreviews.com/supportResponse time: Within 24 hours
View All Guides
Browse detailed guides for every feature
Integration Help
Connect Yuko with other tools