Skip to content

Troubleshooting and FAQ

The page origin is not allowed for that client ID. Check the staging or production ID and embed origin, then send the exact scheme, host, and port to your Tiketo contact. Opening a config URL directly has no page Origin and is rejected.

Run the curl origin check before debugging the widget. It distinguishes an allowed 200 from a denied 403.

  • Check that the loader request returns 200 and is not blocked by CSP or an extension.
  • Check the [tiketoChat] Initialization skipped warning and config status.
  • Make sure init receives a string like TC-XXXXXXXX, not the removed { client, env } form.
  • Make sure the snippet runs once, outside a route component that mounts repeatedly.

Confirm the name supplied by Tiketo, the action ID in config, and support for that contract in your pinned loader. Unknown or disabled actions are ignored. Check the console for payload warnings, then review the registration timing and failure behavior.

The payload may be invalid, the component may be disabled, the pinned loader may be too old, or its renderer may be missing. Compare the supplied name and payload with the generated catalog. The component guide explains renderer timing and fallback behavior.

Compare your policy with the CSP baseline. In connect-src, allow the selected embed origin over HTTPS and WSS. Keep inline runtime styles enabled for the widget.

Use the complete logout and account-change example. The reset reference lists its guarantees, failure handling, and relaunch behavior.

Unknown commands are ignored and produce a [tiketoChat] Unknown command … ignored. console warning. They do not make a config request.

No. Registration supplies the browser implementation for a contract that Tiketo has already configured and enabled. Your Tiketo contact provides the action and component names and schemas.