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 connector proof says the address is already connectedSame connector and internal address already have an active CMS binding.
  4. 04Download 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 extension 0.1.98 and later opens a short-lived verification window on the branded domain, waits for verification and then retries the launch automatically.
  • Keep the extension popup and branded verification window open until the success screen appears. Use the authenticator code if a passkey is unavailable.
  • If no verification window opens, update the extension, reopen the app and allow BusinessProxy pop-up windows in the browser.
  • The verification must use the branded portal for the custom app domain. It does not require opening the central BusinessProxy app catalog.
BRANDED_MFA_NOT_AVAILABLE: branded verification is not configuredBusinessProxy could not find an active branded portal associated with the selected custom app alias. An administrator must finish the custom-domain setup before extension-only launch can perform MFA.
  • Verify and activate the customer alias domain, keep its app.<domain> portal active and use branded_portal launch authentication for that portal.
  • The target app alias must be active, use extension_required and belong to the same verified alias domain as the branded portal.
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 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.