Troubleshooting

Use the symptom—not an assumed internal cause—to choose a guide. Confirm one layer at a time, make the smallest relevant change, then repeat the operation and inspect its result.

Choose what you observe

• Server will not start or setup is unavailable: Startup and setup .
• You cannot complete initial setup or sign in: Login and setup .
• A model service cannot be added, authenticated, or used: Model service connection .
• The model you expect is missing: Missing model .
• A configured client cannot reach Stravia: Client connection .
• The request is rejected as unauthorized: Unauthorized requests .
• A request reaches Stravia but fails: Model request failures .
• Search or media does not work as expected: Web Search issues or Media issues .

Use the request path to narrow the cause

First confirm the client URL and protocol, then the API key and permitted Model ID. In Stravia, check that the model and destination are enabled and the connected service is usable. Finally, inspect Request history for the interaction's status and recorded failure details. A copied example, a saved key, and a successful model response are different checkpoints.

Protect diagnostic data

Do not paste setup tokens, API keys, provider credentials, or complete request bodies into a public issue. Debug captures and exported bundles may contain URLs, headers, bodies, or other sensitive data; review and minimize them before sharing. If these checks do not identify the problem, use Diagnostics to gather the smallest appropriate evidence.

For the complete first-use sequence, return to Quick start .