The store app can’t connect to your site? Check these first

The Woo mobile app says it can’t reach your store, but the website works fine? It’s almost always something on the site blocking the app. A simple test from your phone tells you where.

The website loads fine in your browser, but the Woo mobile app says it can’t reach your store, shows no orders, or keeps sending you back to sign in. Sometimes it only happens to one staff member, or only on iPhone.

In our experience this is almost never the phone. Something on the site, usually a security setting, is stopping the app before it reaches WordPress.

New to fixing things yourself? Read the 10 rules we follow before touching a live store first.

1. Rule out the obvious

  1. Open your website and wp-admin in a browser. If those are broken too, fix that first (see our guide to critical errors after an update).
  2. Update the app, sign out, and sign in again.

2. The phone test

This one test tells you more than anything else.

  1. On your phone, turn Wi-Fi off so you’re on mobile data.
  2. Open a private tab and go to yourstore.com/wp-json/ (use your own address).
  • Good: a page of code-like text starting with {"name":. The door is open.
  • Bad: “Just a moment…”, “Verifying your browser”, a CAPTCHA, “403 Forbidden” or a security plugin’s block page. A firewall is stopping the app.

3. Check application passwords

Go to Users → Profile and scroll down to Application Passwords.

  • If the section is missing, or says application passwords are unavailable, a plugin has switched them off. Some security plugins have a setting named like “Disable WordPress application passwords”.
  • If you use a two-factor (2FA) plugin, look for an option that blocks application passwords for users with 2FA turned on. That explains “it works for my colleague but not for me”.

4. Check your firewall or CDN

If you use Cloudflare or your host has “bot protection”, “DDoS protection” or “under attack” mode, look at its blocked-requests log around the time you tried the app. Ask your host to allow requests to /wp-json/ rather than turning protection off.

5. Check Site Health

Go to Tools → Site Health → Status and look for critical items about the REST API or loopback requests.

6. Moved hosts or changed domain recently?

Go to Settings → General and check that WordPress Address (URL) and Site Address (URL) are both your real address and both start with https://.

What we usually find

  • A security or 2FA plugin blocking application passwords
  • A “challenge every visitor” rule at Cloudflare or the host
  • Slow or overloaded hosting timing out, often right after a move
  • One broken plugin printing errors into every response

Stop and get help if

  • The fix means editing wp-config.php or .htaccess, or switching your firewall off entirely.
  • Your site address or DNS records need changing.