30-SECOND SUMMARY
What to take away
- Verify Ollama first.
- Account for Docker-to-host networking.
- Do not expose the port without authentication and data controls.
Connect Ollama and Open WebUI
Separate model and UI failures.
- 01OLLAMA
Verify in terminal
- 02DOCKER
Mount persistent data
- 03CONNECT
Check host address
- 04PROTECT
Accounts and network
Verify Ollama
A model should answer in the terminal before the UI is introduced.
The working rule for “Verify Ollama” is: Verify Ollama first. Do not treat an open window as proof of a complete installation; also record versions, process state, ports, and persistent data paths.
After running the command or code, inspect the exit status, logs, and the file, process, or response it was meant to create. If it fails, change one input, version, permission, or resource condition at a time and repeat the same check so that the cause remains attributable.
ollama run gemma3:4bStart the container
Use the official image and a persistent volume. Recheck the current tag in the official guide.
The working rule for “Start the container” is: Account for Docker-to-host networking. Do not treat an open window as proof of a complete installation; also record versions, process state, ports, and persistent data paths.
Record the current version and settings before the example, then verify the expected response, file, or process afterward. Preserve the error and return to the smallest working command before adding options; this separates installation failures from input and integration failures.
docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:mainCheck the connection
Open localhost:3000 and inspect the model list. If Docker cannot see host Ollama, follow the official host-address configuration.
The working rule for “Check the connection” is: Do not expose the port without authentication and data controls. Do not treat an open window as proof of a complete installation; also record versions, process state, ports, and persistent data paths.
Define completion with an observable result instead of a general impression. Repeat the same input, and if the output changes, isolate whether the model, runtime settings, or source data changed before moving to the next stage.
Keep the first deployment private
A multi-user or internet-facing service needs authentication, TLS, backups, updates, and access logging.
The working rule for “Keep the first deployment private” is: Verify Ollama first. Do not treat an open window as proof of a complete installation; also record versions, process state, ports, and persistent data paths.
For verification, save the model and runtime versions, source input, relevant settings, and observed output together. Repeat the step while changing only one factor, and record unexpected results and untested limits as carefully as successes before applying the guidance to private or production data.
Frequently asked questions
Why are no models listed?
Check Ollama directly, container logs, the host address, and firewall in that order. Verify Ollama first. For a practical check, follow the “Verify Ollama” section, change one condition at a time, and record the result.
Where are chats stored?
Inspect the mounted data volume and define backup and deletion rules. Account for Docker-to-host networking. For a practical check, follow the “Start the container” section, change one condition at a time, and record the result.
Can I share port 3000?
Not without authentication and network controls. Do not expose the port without authentication and data controls. For a practical check, follow the “Check the connection” section, change one condition at a time, and record the result.
Primary sources
Check the original documentation for version-specific details.
Open WebUI Quick Start Open WebUI configuration Ollama Quickstart