← Back to Documentation
Troubleshooting
Common Issues
Work through the most common setup, access, provider, and deployment problems.
Key Steps
- Start by checking auth, organization membership, server URL, and provider health.
- Use request IDs and timestamps to move from symptom to root cause.
- Check the relevant admin view before changing server configuration.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Client cannot connect
- Confirm the server URL is correct and reachable from the client network.
- Check TLS and DNS before debugging application auth.
- Verify the user account is active in the organization.
Model is missing
- Check provider health and model alias configuration.
- Confirm the user role or team is allowed to use the model.
- Review whether the model was removed from the approved catalog.
Usage looks wrong
- Confirm the report time window and organization selection.
- Compare provider-level usage with model-level usage.
- Look for automation or retry loops that can inflate request volume.