Stravia Docs

Client cannot connect

Symptoms

A client cannot reach Stravia, fails to load its model list, or reports a connection timeout before a request appears in history.

Check

  1. Verify which Stravia instance the client should use and whether it is Desktop or Server.
  2. From the client machine, check the configured base URL, scheme, hostname, port, and network path.
  3. If Server is behind a proxy, verify the proxy forwarding and --admin-origin / --trusted-proxy settings for the actual deployment.
  4. Confirm the client uses the intended Stravia API key and supported protocol. Keep the key out of screenshots and shell history.
  5. Check whether the request reached Stravia. If no record exists, investigate connectivity and client config before the upstream model service.

Resolution

Correct the endpoint or proxy path and configure the client using its Stravia Connect instructions. A preview or copied config is not proof that the client accepted it; Desktop Apply changes local client files, but does not guarantee a successful model request.

Escalate if still stuck

Provide the client name/version, sanitized endpoint origin, connection error, and whether the request appears in history. See Connect clients and Reverse proxy .