Sign in
Stable

Troubleshooting library

Problem pages support can send directly: errors, permissions, connectors and recovery.

Common issues

Open the issue that matches the visible error.

  1. 01Private app opens with ERR_TIMED_OUTProxy state, connector readiness, upstream timeout, route.
  2. 02WordPress admin returns Access deniedAdmin cookies, enforcement mode and emergency recovery.
  3. 03CMS site proof is temporarily unavailableRestore the canonical CMS address, verify the active module and retry without resetting Site ID.
  4. 04CMS connector proof says the address is already connectedSame connector and internal address already have an active CMS binding.
  5. 05Download signature verification failedUse the current public key, namespace and exact file.

Reference

Implementation details for setup and review.

APP_MFA_REQUIRED: verify the app launchThe app requires a fresh account MFA or passkey assertion. BusinessProxy opens a short-lived verification window and retries the launch after verification.
  • If a branded verification domain is configured, BusinessProxy uses it. Otherwise extension 0.1.107 and later opens the central BusinessProxy app portal.
  • If no verification window opens, update the extension, reopen the app and allow BusinessProxy pop-up windows in the browser.
  • A branded domain changes where verification is shown; it is not required for managed Alias or CMS Direct access.
BRANDED_MFA_NOT_AVAILABLE: branded verification is not configuredBusinessProxy could not find an active branded portal associated with the selected custom app alias. Extension 0.1.107 and later automatically continues verification in the central BusinessProxy app portal.
  • Update the extension if this error is shown instead of the central verification portal.
  • Configure and activate app.<domain> with branded_portal only when verification must be shown on the customer domain.
APP_MFA_HANDOFF_EXPIRED: verification took too longThe one-time extension handoff is deliberately short-lived and can be consumed only once. Close the old verification window and open the app from the extension again to create a new request.
APP_MFA_HANDOFF_INVALID: launch binding changedThe verification request does not match the current user, workspace, app or signed browser device. This prevents a handoff opened on one device from authorizing another device.
  • Close the old window, confirm that the extension is signed in to the intended workspace and retry from the same browser profile.
  • If the error repeats, sign out and sign in to refresh the signed device registration, then retry.
APP_MFA_CANCELLED: verification window was closedThe branded verification window was closed before BusinessProxy received a completed assertion. Open the app again and finish passkey or authenticator verification before closing the window.
CMS_SITE_PROOF_TEMPORARILY_UNAVAILABLE: the site did not answer the binding checkBusinessProxy could not retrieve or validate the signed site proof from the canonical CMS address. HTTP 503 describes a temporary verification failure; it does not mean that the Connector is offline and it is not a reason to reset the Site ID or reinstall the module immediately.
  • Open the canonical HTTPS address outside BusinessProxy and make sure the site, its REST or control endpoint and TLS certificate are available. If the server has just restarted, wait until PHP, the web server and scheduled jobs have fully started.
  • In the CMS, keep one active copy of the current signed BusinessProxy module. If duplicate plugin directories were removed, activate the remaining module, open its connection page and refresh the local status before retrying the remote check.
  • In BusinessProxy click Retry verification for the current CMS connection. Reconnect only when the Site ID shown by the module does not match the current connection or the pairing check still fails after the site proof endpoint is available.
  • If the same site has an old and a current CMS connection, transfer its custom Alias to the current connection instead of deleting and recreating the domain. This preserves DNS verification and the existing certificate.
Transfer a CMS custom domain
CMS connector proof: address already connectedThis message is not a connector outage. BusinessProxy stops the test before dispatching a proof request when the same workspace already has an active CMS binding for the selected connector and the same normalized internal address.
  • Check the selected connector and internal address in the CMS plugin, then compare them with existing CMS sites and private apps in BusinessProxy.
  • If this is the same site being reconnected, remove the old CMS binding or the private app created for it in BusinessProxy, then run the connector test again.
  • If this is a different CMS on the same host, use a distinct internal URL or path, or a separate connector route, so BusinessProxy can distinguish the sites.
  • Do not rotate Site ID or reinstall the plugin as the main fix. A new Site ID with the same connector and internal address still conflicts with the existing binding.