Quick summary: Most "Ollama not working" problems come down to five causes: the background server isn't running, the model name doesn't match what you downloaded, the GPU isn't being detected so everything runs slowly on the CPU, the model doesn't fit in memory, or a network setting is blocking downloads or connections. This guide walks through each one with the exact messages Ollama prints, the command that confirms the cause, and the fix from Ollama's own documentation.
What's in this guide
- Step 0: read the server log first
- "Could not connect to ollama server"
- "Model not found, try pulling it first"
- Ollama is slow: the GPU isn't being used
- Out of memory, crashes, or a sluggish PC
- Downloads fail or other apps can't connect
- Windows-specific glitches
- Ollama vs LM Studio vs Jan: when switching makes sense
- Editor's note, FAQ, and related guides
Step 0: Read the server log first
Ollama is really two pieces: a server that loads models and answers requests on your machine, and the ollama command or desktop app that talks to it. When something breaks, the terminal often shows only a short error, while the server log explains why. Ollama's troubleshooting page lists where that log lives on each system:
- macOS: run
cat ~/.ollama/logs/server.log - Linux (systemd): run
journalctl -u ollama --no-pager --follow --pager-end - Docker: run
docker logs <container-name>(find the name withdocker ps) - Windows: press Win+R and open
explorer %LOCALAPPDATA%\Ollama. The newest log isserver.log, older ones are numberedserver-#.logfiles, andapp.logcovers the tray app.
If the log is too quiet, turn on debug output. On Windows, quit Ollama from the tray icon first, then in PowerShell run $env:OLLAMA_DEBUG="1" followed by & "ollama app.exe". On macOS and Linux, set OLLAMA_DEBUG=1 as an environment variable for the server. Keep the log open in a second window while you work through the fixes below.
Fix 1: "Could not connect to ollama server"
On Linux, if you type ollama run gemma4 while no server is running, the CLI stops with could not connect to ollama server, run 'ollama serve' to start it. Running ollama -v in the same situation prints Warning: could not connect to a running Ollama instance instead of a server version. Both mean the same thing: nothing is answering on the default address, 127.0.0.1:11434.
How to fix it
- Linux with the install script: start the service with
sudo systemctl start ollama, then check it withsudo systemctl status ollama. If the status shows it crashing, read the journalctl log from Step 0. - Linux manual install or quick test: run
ollama servein one terminal and use a second terminal forollama run. Closing the first terminal stops the server. - macOS and Windows: the desktop app runs the server in the background. Open Ollama from Applications or the Start menu. In those versions, the CLI tries to launch the app for you when it can't reach the server, so a repeated failure usually means the app itself is failing to start. Check
app.log. - You changed
OLLAMA_HOST: the CLI and the server must agree on the address. If you moved the server to another port or IP, set the sameOLLAMA_HOSTvalue in the shell where you run the CLI.
One more Linux trap: if your system mounts its temp folder with the noexec flag, Ollama can't run its helper files from there. The docs suggest pointing OLLAMA_TMPDIR at a folder the Ollama user can write to, such as /usr/share/ollama/.
Fix 2: "Model not found, try pulling it first"
When an API call or app asks for a model you don't have, the server replies with HTTP 404 and the message model "name" not found, try pulling it first. This often happens with apps that connect to Ollama, because they ask for a model by a name you never downloaded, or by a slightly different tag.
How to fix it
- Run
ollama lsto see the exact names and tags already on your machine. - Download the missing one with
ollama pull gemma4(use the name your app expects). - In the connecting app, pick the model from its list rather than typing the name, or copy the name from
ollama lscharacter for character, including the tag after the colon.
Ollama's API error page also lists the other codes you may see: 400 for a malformed request, 429 when a rate limit is hit, 500 for a server error, and 502 when a cloud model can't be reached. If an error happens partway through a streamed reply, the status code stays 200 and the error arrives as a final JSON line with an error field, so check the end of the stream, not just the status code.
Fix 3: Ollama is slow because the GPU isn't used
The fastest check is ollama ps while a model is loaded. The PROCESSOR column tells you where it is running: 100% GPU is what you want, 100% CPU means the GPU was not used, and a split such as 48%/52% CPU/GPU means the model only partly fit in video memory (VRAM).
NVIDIA cards
- Ollama's hardware page requires compute capability 5.0 or higher and driver 550 or newer. Older cards with compute capability 5.0 to 6.2 (for example the GTX 10-series) need driver 570 or newer. On Windows, the stated minimum is driver 551.61.
- On Linux, if the GPU vanishes after sleep (suspend and resume), reload the driver module with
sudo rmmod nvidia_uvm && sudo modprobe nvidia_uvm, or reboot. - Server logs may show GPU initialization error codes such as 3 (not initialized), 46 (device unavailable), 100 (no device), or 999 (unknown). The documented steps are: run
sudo nvidia-modprobe -u, reloadnvidia_uvm, reboot, and update the driver. - In Docker, first confirm the container runtime can see the card with
docker run --gpus all ubuntu nvidia-smi. If Ollama starts on the GPU and later drops to the CPU with discovery errors, the docs fix is adding"exec-opts": ["native.cgroupdriver=cgroupfs"]to/etc/docker/daemon.json.
AMD cards
- Ollama now bundles ROCm 7 libraries. On Linux, an older ROCm 6.x driver can make GPU discovery hang. The log then shows
failure during GPU discovery...failed to finish discovery before timeout, and Ollama falls back to the CPU. Upgrade to the ROCm v7 driver with AMD'samdgpu-installtool, reboot, and restart Ollama. - On Linux, your user also needs access to
/dev/kfd, which usually means membership in thevideoand/orrendergroup. - On Windows, the ROCm list is limited to RX 7000-series and Radeon PRO W7000 cards. Some RX 6000-series systems don't get ROCm v7 on current drivers. The docs say Vulkan is on by default and is the recommended fallback for them.
- For cards ROCm doesn't officially support on Linux,
HSA_OVERRIDE_GFX_VERSIONcan make Ollama treat the card as a close supported target. The docs' example is10.3.0for an RX 5400. This is experimental, so expect possible instability.
Fix 4: Out of memory, crashes, or a sluggish computer
A model that barely fits will load partly onto the CPU, which slows it down sharply, or fail to load at all. Before you buy hardware, try these levers from Ollama's FAQ:
- Context length. The default context window is 4,096 tokens. Raising it (with
OLLAMA_CONTEXT_LENGTH,/set parameter num_ctxin a chat, ornum_ctxin the API) uses more memory. If you raised it and things got slow, lower it again. - Parallel requests. Memory needed grows with
OLLAMA_NUM_PARALLELtimes the context length. The default is 1. If you raised it for an app, that may explain the jump. - K/V cache quantization. When Flash Attention is active, setting
OLLAMA_KV_CACHE_TYPE=q8_0uses roughly half the cache memory of the defaultf16, with a very small precision loss according to the docs.q4_0saves more but costs more quality. - Models staying loaded. By default, a model stays in memory for 5 minutes after its last use. Free it right away with
ollama stop gemma4, or change the timeout withOLLAMA_KEEP_ALIVEor the API'skeep_alivesetting (0unloads right after the reply). - Too many requests. If you get a 503 "server overloaded" error, the request queue is full. Its size is
OLLAMA_MAX_QUEUE, 512 by default.
If crashes started right after a GPU driver change, you can force CPU mode as a test. On NVIDIA, set CUDA_VISIBLE_DEVICES=-1. More generally, OLLAMA_LLM_LIBRARY="cpu_avx2" skips GPU auto-detection. If the crash disappears, the GPU stack is the problem.
Fix 5: Downloads fail or other apps can't connect
- Behind a corporate proxy: set
HTTPS_PROXYand install the proxy's certificate as a system certificate. The docs specifically warn against settingHTTP_PROXY: model pulls only use HTTPS, and an HTTP proxy setting can break connections between your apps and the server. - Slow downloads inside WSL2 on Windows 10: in the
vEthernet (WSL)network adapter's advanced properties, disable both "Large Send Offload Version 2" entries (IPv4 and IPv6). - Another device on your network can't reach Ollama: by default it only listens on
127.0.0.1, which is this computer only. SetOLLAMA_HOST=0.0.0.0:11434to listen on the network, and only do this on a network you trust. - A browser extension or web app gets blocked: add its origin to
OLLAMA_ORIGINS, for examplechrome-extension://*. - The disk is full: models can take tens to hundreds of GB. Move them with
OLLAMA_MODELS. On Linux, give theollamauser ownership of the new folder (sudo chown -R ollama:ollama <directory>), or the server can't write to it.
Where you set these variables matters. On Linux, add Environment= lines with systemctl edit ollama.service, then run systemctl daemon-reload and systemctl restart ollama. On macOS, use launchctl setenv and restart the app. On Windows, quit Ollama from the taskbar, edit your account's environment variables in Settings, and relaunch from the Start menu. A variable typed into a random terminal won't reach the background app.
Fix 6: Windows-specific glitches
- Strange text like
←[?25h←[?25lor "The parameter is incorrect": older Windows 10 builds don't display control characters correctly. Update Windows. Ollama's stated requirement is Windows 10 22H2 or newer. - Squares instead of progress bars: some older terminal fonts can't show the Unicode characters Ollama uses for progress. Switch to a different terminal font.
- Ollama starts every time you log in: turn it off in Task Manager under Startup apps. On macOS, use Login Items in System Settings.
Ollama vs LM Studio vs Jan: when switching makes sense
If Ollama keeps fighting your hardware, a different local app won't magically add VRAM, but a graphical app can make model choice and settings easier to see. Here is how the three compare, based on each official site checked on 2026-10-24:
| Ollama | LM Studio | Jan | |
|---|---|---|---|
| Local use | Free plan: run models locally, starter cloud credits included | Free plan: local LLMs via llama.cpp and MLX, offline voice transcription | Free download; local models are the default |
| Paid options | Pro $20/month or $200/year ($60 usage credits per month); Team $500/month | Bionic+ $20/month (US-hosted open models); Pro $100/month | Cloud models need your own provider API key (e.g. OpenAI, Anthropic) |
| Main interface | CLI + local API on port 11434, desktop app on macOS/Windows | Desktop app, plus the lms CLI |
Desktop app with a model Hub and local API server |
| Platforms | macOS 14+, Windows 10 22H2+, Linux | Apple Silicon Macs (macOS 14+), Windows x64 with AVX2 or ARM, Linux AppImage | macOS, Windows, Linux |
| Open source | Yes (MIT license) | Not advertised as open source on lmstudio.ai | Yes (Apache 2.0) |
| Helps with hardware fit | ollama ps shows CPU/GPU split |
Docs recommend 16GB+ RAM, 4GB+ VRAM on Windows | Hub shows whether each model fits your hardware |
In practice, keep Ollama if other tools (coding assistants, scripts, browser extensions) need its API. Try Jan if you mainly want a chat window and like being told up front which models fit your computer. LM Studio suits people who want a polished app on Apple Silicon or Windows. Note that it doesn't support Intel Macs, and on x64 PCs it needs a CPU with AVX2.
Editor's note
Who this is for: anyone running Ollama on their own Mac, Windows PC, or Linux box, including people who installed it only so another app (a coding assistant, a notes app, a browser extension) could use local models.
Who it's not for: if you only use Ollama's cloud models, local GPU and memory fixes won't apply. Check your plan and the 429/502 errors instead.
Gotchas I'd flag:
- Environment variables set in a terminal don't reach the background app on macOS or Windows. Set them the way the docs describe, then fully quit and reopen Ollama.
- A model that runs "fine but slowly" usually doesn't fit in VRAM. Check
ollama psbefore blaming drivers. - Raising the context length is the most common self-inflicted slowdown.
- Setting
OLLAMA_HOST=0.0.0.0exposes the API to your network. Only do this on a network you trust, never on public Wi-Fi.
Quick error-to-fix map: "could not connect" → start the service or app. "not found, try pulling it first" → ollama pull with the exact name. 100% CPU → driver or ROCm version. 503 → too many requests queued (OLLAMA_MAX_QUEUE). Garbled Windows terminal → update Windows 10.
FAQ
How do I update Ollama to rule out an old bug?
On macOS and Windows, Ollama downloads updates by itself. Click the menu bar or taskbar icon and choose "Restart to update". On Linux, re-run the install script: curl -fsSL https://ollama.com/install.sh | sh. If a new release breaks something on Linux, the same script accepts an OLLAMA_VERSION value to install a specific older version.
Does Ollama send my prompts to the internet?
According to Ollama's FAQ, prompts to local models stay on your machine. Cloud models are processed on Ollama's servers, and the company says it doesn't store or train on that content. To go local-only, set OLLAMA_NO_CLOUD=1 or add "disable_ollama_cloud": true to ~/.ollama/server.json, then restart. The log will show Ollama cloud disabled: true.
My GPU is in the list, but ollama ps still shows CPU. What next?
First confirm the model actually fits: a split like 48%/52% means VRAM ran out, not that detection failed. If it shows 100% CPU even with a small model, update the driver (NVIDIA 550+ or 570+ for older cards, AMD ROCm v7), restart Ollama, and look for GPU discovery messages in the server log with OLLAMA_DEBUG=1 turned on.
Related guides on lightmind24:
- How to Run Open AI Models on Your Own Windows 11 PC with Llama Windows
- How to Try Meta's Muse Spark Open: Hosted APIs, Local Setups, and Hardware
- How to Use GitHub Copilot Free in VS Code
Start with the server log and ollama ps. Between them, they explain most Ollama failures in under a minute.
Images: screenshots of Ollama's official documentation pages (docs.ollama.com: Troubleshooting, FAQ, Hardware support, Windows), captured 2026-10-24. See the official screenshots at the end of this post.
Last verified: 2026-10-24
Sources:
Ollama docs: Troubleshooting
Ollama docs: FAQ
Ollama docs: Hardware support
Ollama docs: Windows
Ollama docs: Linux
Ollama docs: macOS
Ollama docs: API errors
Ollama docs: CLI reference
Ollama on GitHub (source code and license)
Ollama pricing
LM Studio pricing
LM Studio system requirements
Jan Desktop quickstart
Jan on GitHub (license)
댓글
댓글 쓰기