Model connection issues
Test connection failed
- Open Settings → Models, edit the config, click Test connection.
- Confirm the API key is a valid literal, or that the env var is exported on this machine.
- If you override Base URL, check for duplicated path segments and whether a proxy is required.
- Corporate networks may block vendor domains (e.g.
api.openai.com).
Common errors
| Symptom | Fix |
|---|---|
| 401 / Invalid API Key | BYOK: regenerate key and update config; Newton: sign in again |
| 402 / insufficient balance | Newton: open Dashboard or top-up |
| 404 / model not found | Check model ID and account access; for Newton, refresh the model list |
| 429 / rate limit | Lower concurrency or switch vendor/model |
| Timeout / service unavailable | Check network, proxy, Base URL; for Newton retry later or switch to BYOK |
Newton-specific checks
- Confirm desktop is signed in to Mystilink (not only an activation code).
- If the session expired, sign in again and refresh models.
- If balance is zero or low, top up first — Newton billing.
- Guide: Newton LLM.
Primary model unavailable
If auto fallback is on, keep at least two working configs. Otherwise temporarily set another as primary (you can switch between Newton and BYOK).
Key safety
- Do not commit BYOK keys or account credentials to Git or share screenshots.
- Mystilink does not upload your BYOK keys; BYOK requests go directly to the vendor.
- Do not treat account login tokens as shareable “API keys.”
More: Newton LLM, LLM providers, Official platform API keys, OpenAI-compatible providers, Local model deployment, FAQ: LLMs & privacy.