Symptoms, causes and fixes for the problems store admins most often meet with the Companion plugin, from sign-in errors to late emails.
Find the symptom you are seeing, then follow the fix. Most problems come down to one of four things: the
Storefront URL is not set, a setting is still within its 5-minute cache, a required plugin (Contact Form 7,
Brevo) is missing, or WordPress’s scheduler is not running often enough. Problems with the storefront’s own
deployment are covered in Storefront troubleshooting.
Is the Storefront URL set? Go to StoreFront → Settings → General and check Storefront URL. Emails,
preview links, product redirects and wallet payments all depend on it.
Did you press Save Changes? One button saves every tab. If any tab has a problem, nothing is saved; look for a
red message at the top of the screen.
Have 5 minutes passed? The storefront caches settings and page content for up to 5 minutes. Wait, then reload
the storefront page (a hard reload, or a private window).
Is the feature switched on? Several features are off by default: Compare, the shop-page banner, the promo
popup, most home-page sections and the newsletter provider.
Nobody can sign in or register; the storefront reports a server error (jwt_secret_missing)
The signing secret RSC_JWT_SECRET is not in wp-config.php. The Social Login tab shows an amber “JWT signing secret is not configured” banner.
Copy the ready-made line from that banner (it includes a freshly generated secret) and ask whoever manages the server to add it to wp-config.php. See Sign-in and security.
New customers can’t sign in after registering
Email verification is required, and the verification email did not arrive.
Check email delivery and that the Email verification email is enabled. See Emails.
The Google or Facebook button is missing
Google needs a Client ID; Facebook needs both App ID and App Secret.
Fill them in under Authentication → Social Login and save. The badge shows Connected when ready.
Google says Error 400: redirect_uri_mismatch
The storefront’s login address is not listed in Google Cloud.
Add the storefront address followed by /login (no trailing slash, no language prefix) to Authorised redirect URIs. The setup guide on the Social Login tab shows the exact value.
Facebook sign-in works for you but not for shoppers
The Meta app is still in Development mode.
Switch the app to Live (it needs privacy-policy and data-deletion URLs).
An administrator can’t use Google or Facebook sign-in
Staff accounts are not allowed to use social sign-in, by design.
Sign in with the account’s password.
A shopper is asked for a password after choosing Facebook
Their Facebook email matches an existing account, which must be confirmed once.
Expected. They enter that account’s password once to link it.
Social-login and Turnstile keys are set only in WordPress, never in the storefront’s configuration.
These notices appear at the top of wp-admin for administrators. None of them switches anything off.
Notice
What it means
What to do
“StoreFront: Stripe did not register the storefront domain …”
Stripe refused to register your storefront’s domain for wallet payments, so the Apple Pay and Google Pay buttons won’t appear. Card payments are not affected.
Check the reason Stripe gave and your Stripe keys. It is retried automatically within the hour, or straight away when the Storefront URL or Stripe keys change. Local and test addresses are never sent. Keep Link switched off in the Stripe plugin: only Apple Pay and Google Pay are supported on the storefront. See Payments.
“StoreFront: (plugin and version) is active, but storefront payments are verified against …”
Your WooCommerce Stripe Gateway or WooCommerce PayPal Payments version is outside the range the storefront was tested with. Payments keep working.
Test a sandbox payment before relying on this version, or ask your developer to confirm it.
“StoreFront: this store takes payments on the storefront, but RSC_STOREFRONT_SHARED_SECRET is not defined …”
A shared secret between WordPress and the storefront is missing, so checkout attempts are not limited per shopper.
Ask your developer to set the same secret in wp-config.php and in the storefront’s configuration.
“(Yoast SEO or Rank Math) is now where SEO is edited for the storefront. Run “Sync SEO” once …”
You activated or switched SEO plugins.
Click Open the SEO settings and run Sync SEO. See SEO.
“StoreFront: WooCommerce’s built-in customer stock notifications … are switched on alongside …”
Two back-in-stock systems are on, so customers may be emailed twice.
Remove WOOCOMMERCE_BIS_ALPHA_ENABLED from wp-config.php.
Gather the details your developer will need: what you did, what you expected, what happened, the time, and a
screenshot of any message. Check WooCommerce → Status → Scheduled Actions for failed actions and WooCommerce →
Status → Logs for errors.