Troubleshooting

Authentication failed before routing. Re-check your seat key and confirm it has not been revoked. If the key is valid, verify the server's license configuration with your administrator.

The service binding is stale — the host needs a full rebuild and service recycle, not just a restart. The first start after a rebuild can return 503 for 2–4 minutes while the service warms up. Wait and retry before escalating.

Expected behaviour during the warm-up window after a fresh deploy or recycle. Wait 2–4 minutes and try again. If the error persists beyond 5 minutes, check that the service process started successfully.

Ask the assistant for system information to confirm the deployed build matches the release you installed. A version mismatch between the client binary and the server can cause unexpected behaviour — update both from the same release.

Verify the MCP server URL in your assistant's settings matches the address shown in your portal's Hosted MCP server panel. If you self-host, confirm the container is running and the port is reachable from the network your assistant uses.

Re-download from the portal. Do not use files obtained outside the portal. The sha256 shown on the Downloads page can be used to verify the file you received matches what was published.

Paste the full key including any leading or trailing characters. Keys are case-sensitive. If the key was revoked, ask your organisation's Ilvy admin to issue a replacement from the portal's Users & seats panel.