Skip to content

Troubleshoot AI Workspace

This page covers the problems you're most likely to encounter while setting up AI Workspace and an AI Gateway. For the setup steps these fixes assume, see Get started with AI Workspace. For background, see AI Workspace overview and AI Workspace configuration and environment interpolation.

The AI Gateway stays Inactive after you start it

Check that:

  • The gateway container can reach the host and port in APIP_GW_CONTROLLER_CONTROLPLANE_HOST. From inside a container, host.docker.internal resolves to your host machine.
  • The registration token in APIP_GW_CONTROLLER_CONTROLPLANE_TOKEN hasn't been revoked. If you click Reconfigure on the gateway's page, it revokes the old token and issues a fresh one. Update api-platform.env and restart the gateway to pick it up.
  • Inspect the gateway container's logs (docker compose logs) for a connection error to the control plane.

A chat completion request returns 401 or 403

Confirm you're sending the generated inbound API key in the header your provider's Security tab configures (X-API-Key by default), not your AI Workspace sign-in session. These authenticate two different things: one signs you in to AI Workspace; the other authenticates an application to the gateway.