# Open WebUI with Ollama: connect an existing local runtime

Connect an existing Ollama runtime to Open WebUI and verify model selection, account visibility, and a follow-up conversation.

Author: Retrivium team
Updated: 2026-11-03
Canonical URL: https://retrivium.ai/journal/open-webui-with-ollama-local-chat/
Language: en

Connect Open WebUI to an already working Ollama runtime, then test model selection and a follow-up conversation. This is an application connection task: it does not require changing GPU settings or rebuilding a local infrastructure stack.

## The concrete application boundary

In the provider connection settings, select the Ollama integration rather than assuming a compatible API entry has the same discovery behavior. Open WebUI’s model selector is populated through its connection to the existing runtime. A Workspace model adds a reusable configuration over a base model, which is useful later but unnecessary for the first conversation. Begin directly with the available backend entry so that one extra wrapper does not obscure the path. The address is interpreted by the running application, not by the user’s description of the machine. This walkthrough assumes an existing local arrangement and deliberately makes no changes to remote networking or runtime installation ([Open WebUI Models](https://docs.openwebui.com/features/workspace/models/)).

## A practical route

Verify that the intended model is available in Ollama before opening connection settings. Choose the Ollama connection type and use the address appropriate to the existing application arrangement. Refresh the available models, select the intended entry, and send a plain text question. Keep tools and document attachments out of the first check ([Open WebUI Ollama connection guide](https://docs.openwebui.com/getting-started/quick-start/connect-a-provider/starting-with-ollama)).

## A worked example

Ask the selected model to turn a fictional maintenance note into a short checklist. Follow with a question about the item that must happen first. Save the conversation and reopen it using the same account. This checks the chosen model path and conversation continuity; it does not validate every optional feature offered by the interface.

| Check | Record |
| --- | --- |
| Backend | The actual Ollama model entry available before the connection was added. |
| Application | The connection type and the model selected in the Open WebUI conversation. |
| Account | The user who can reopen the conversation and see the intended selection. |

## Reading the failure correctly

A model missing from the selector may involve connection inventory or application visibility rather than failed generation. Check whether the backend works independently and whether the current account can use the model. If an administrator succeeds while another user cannot, preserve that distinction instead of reinstalling Ollama.

## What completes the check

Retain one successful initial answer and its follow-up, together with the account and backend identity. Add reusable Workspace wrappers only after this baseline is clear, so that a later instruction or sharing problem is not confused with the underlying connection. Keep the connection unchanged between the initial and follow-up questions ([Open WebUI documentation](https://docs.openwebui.com/)).

Related background: [vLLM served-model-name: Fix a Missing API Model](/journal/vllm-served-model-name/), [llama.cpp server: a local API from a GGUF model](/journal/llama-cpp-server-launch/).