Quick diagnosis
This usually points to Ollama endpoint, container networking, host access, or service state. Start with the simplest visible checks before changing advanced settings.
First three checks
- Confirm the exact app, model, route, and error text.
- Check whether the selected model is realistic for the machine’s RAM, VRAM, and context length.
- Confirm whether the issue is a local runtime problem, a UI/provider problem, or a document/retrieval problem.
Common causes and fixes
| Cause | What to check | Safer first fix |
|---|---|---|
| Memory pressure | RAM, VRAM, context length, background apps | Use a smaller model, lower context, or close other apps. |
| Wrong provider or endpoint | App provider settings, localhost URL, Docker host access | Verify the runtime works before connecting another UI. |
| Model/download issue | Exact model name, disk space, network status | Retry with a smaller known model and enough free storage. |
| Privacy-sensitive workflow | Cloud API keys, web search, remote access, exposed ports | Stop and audit settings before uploading sensitive data. |
When to stop
Stop troubleshooting and switch paths when the workflow involves confidential documents and you cannot explain where prompts, files, embeddings, logs, and provider calls go.