error: could not connect to ollama server, run 'ollama serve' to start it

Not specified by the original author.

Short answer: start the server. Run ollama serve in a second terminal window and leave it open, then retry your command in the first one. `` Error: could not connect to ollama server, run 'ollama serve' to start it 1. Run ollama serve in its own terminal and leave it running. Expected: startup log lines, no error. 2. In another terminal run ollama list. Expected: your downloaded models, not the connect error. 3. Make it permanent so reboots stop breaking it. Linux: sudo systemctl enable --now ollama. macOS with Homebrew: brew services start ollama. Windows or macOS installer: launch the Ollama app, the tray or menu-bar icon means the server is up. 4. If the server is up but clients still fail, check the OLLAMA_HOST variable is identical on both sides, and remember the default binds the loopback interface only, so remote machines cannot reach it without rebinding. 5. If you see address already in use on port 11434 instead, Ollama is already running. Use it, do not start a second server. Root cause: the CLI is stateless. It needs the server process listening before any command (run, ps, pull, API calls) can work, and nothing starts that server automatically on most installs. When to use: this exact message from the CLI or from API clients. When NOT to use: connection refused from inside a Docker container pointing at the loopback interface is a different problem, the client needs the host's address or the Ollama service name, not the loopback address. Variant phrasings: "could not connect to ollama", "ollama server not running", "ollama connection refused 11434". Edge cases: on macOS and Windows ollama ps` tries to launch the app for you. If the error persists there, the app itself is failing to start, check its logs rather than retrying the command.

Context: Ollama is two processes: a background server and the CLI client you type into. Every CLI command dials the server on port 11434, and this error means nothing is listening there. Ollama is installed, but the server part is not running. This is the normal state after a reboot or a fresh Homebrew install, which does not auto-start the service.

Source: Ollama is two processes: a background server and the CLI client you type into. Every CLI command dials the server on port 11434, and this error means nothing is listening there. Ollama is installed, but the server part is not running. This is the normal state after a reboot or a fresh Homebrew install, which does not auto-start the service.

Verified resolution: Short answer: start the server. Run ollama serve in a second terminal window and leave it open, then retry your command in the first one. `` Error: could not connect to ollama server, run 'ollama serve' to start it 1. Run ollama serve in its own terminal and leave it running. Expected: startup log lines, no error. 2. In another terminal run ollama list. Expected: your downloaded models, not the connect error. 3. Make it permanent so reboots stop breaking it. Linux: sudo systemctl enable --now ollama. macOS with Homebrew: brew services start ollama. Windows or macOS installer: launch the Ollama app, the tray or menu-bar icon means the server is up. 4. If the server is up but clients still fail, check the OLLAMA_HOST variable is identical on both sides, and remember the default binds the loopback interface only, so remote machines cannot reach it without rebinding. 5. If you see address already in use on port 11434 instead, Ollama is already running. Use it, do not start a second server. Root cause: the CLI is stateless. It needs the server process listening before any command (run, ps, pull, API calls) can work, and nothing starts that server automatically on most installs. When to use: this exact message from the CLI or from API clients. When NOT to use: connection refused from inside a Docker container pointing at the loopback interface is a different problem, the client needs the host's address or the Ollama service name, not the loopback address. Variant phrasings: "could not connect to ollama", "ollama server not running", "ollama connection refused 11434". Edge cases: on macOS and Windows ollama ps` tries to launch the app for you. If the error persists there, the app itself is failing to start, check its logs rather than retrying the command.

Source URL: https://github.com/ollama/ollama/blob/main/README.md