You pasted your error into Google. Here's the fix. Jump to your specific error below.
You ran OpenClaw. You configured Ollama. You got "fetch failed." Now you're here.
Good. This page covers every variant of the OpenClaw Ollama fetch failed error, what each one actually means, and the specific fix. No backstory. No theory. Just the answer you need right now.
Jump to your error:
- TypeError: fetch failed
- Failed to discover Ollama models
- TimeoutError: fetch failed (model discovery)
- Ollama model not found
- Ollama not responding (ECONNREFUSED)
- TUI fetch failed Ollama
If your error doesn't match any of these exactly, start with the first one. Most Ollama connection failures are variations of the same root cause.
TypeError: fetch failed
What you see: OpenClaw throws "TypeError: fetch failed" when trying to connect to Ollama. No additional context. No helpful message. Just "fetch failed."
What it means: OpenClaw can't reach the Ollama HTTP API endpoint. The request to Ollama's server never completes. This is almost always a networking issue, not an Ollama issue and not an OpenClaw issue.
The fix: Check three things in this order.
First, verify Ollama is actually running. Open a separate terminal and try hitting Ollama's API directly (usually at http://127.0.0.1:11434). If that doesn't respond, Ollama isn't running. Start it.
Second, check the URL in your OpenClaw config. The baseUrl for your Ollama provider must match where Ollama is actually listening. If Ollama runs on port 11434 and your config says 11435, you get fetch failed.
Third, if you're on WSL2 (Windows Subsystem for Linux) and running OpenClaw in WSL while Ollama runs on the Windows host (or vice versa), 127.0.0.1 doesn't work across the boundary. You need the actual WSL2 IP address. Get it from the hostname command inside WSL and use that IP in your OpenClaw config instead of localhost.
GitHub reference: Issue #14053 documents this specific TypeError for Ollama discovery.
Failed to discover Ollama models
What you see: "Failed to discover Ollama models" appears during OpenClaw startup or when switching to an Ollama provider.
What it means: OpenClaw's auto-discovery tried to query Ollama for available models and the request failed. This is different from "fetch failed" because the connection might partially work but the model list request specifically fails.
The fix: The most common cause is that Ollama hasn't finished loading a model when OpenClaw tries to discover it. Ollama needs time to load model weights into memory, especially for larger models. If OpenClaw starts before the model is ready, discovery fails.
Pre-load your model before starting OpenClaw. Run your model in Ollama first, wait for the "success" confirmation, then start the OpenClaw gateway. This ensures the model is loaded and discoverable when OpenClaw queries for it.
Alternatively, skip auto-discovery entirely by defining your models explicitly in the OpenClaw config. Specify the Ollama provider with the exact model name and context window size. When models are defined explicitly, OpenClaw doesn't need to discover them.
GitHub reference: Issue #22913 documents Ollama models not being detected during discovery.
For the complete Ollama troubleshooting guide covering all five local model failure modes (not just fetch errors), our Ollama guide covers the full picture.
TimeoutError: fetch failed (model discovery)
What you see: "TimeoutError" combined with "fetch failed" during model discovery. Sometimes logged as "failed to discover ollama models timeouterror."
What it means: OpenClaw reached Ollama's API but the response took too long. The discovery request timed out. This typically happens when Ollama is in the process of loading a large model (7B+ parameters) and can't respond to API queries until the load completes.
The fix: Same as above: pre-load the model before starting OpenClaw. Large models (especially 14B+ or quantized 30B models) can take 30–60 seconds to load on machines with limited RAM. OpenClaw's discovery timeout is shorter than that.
If the timeout persists even after the model is loaded, the issue might be system resource pressure. If your machine is running low on RAM (Ollama plus the model plus OpenClaw plus the OS), everything slows down. Check your available memory. For comfortable Ollama operation with OpenClaw, you need at least 16GB total RAM for a 7B model, 32GB for larger models.
GitHub reference: Issue #29120 documents this timeout variant specifically for Qwen models on WSL.
Ollama model not found
What you see: OpenClaw connects to Ollama but reports the specified model as "not found."
What it means: Ollama is running and responding, but the model name in your OpenClaw config doesn't match any model Ollama has pulled. This is usually a typo or a naming format mismatch.
The fix: Ollama model names include a tag. The model "qwen3" isn't the same as "qwen3:8b" or "qwen3:latest." Check exactly which models Ollama has available by listing them, then match the exact name (including tag) in your OpenClaw config.
Common mistakes: using "llama3" when the pulled model is "llama3:8b-instruct," using "mistral" when Ollama has "mistral:7b," or using a model name with a slash (like "ollama/qwen3:8b") when the provider config already specifies Ollama as the provider and just needs the model name without the prefix.
If you recently pulled a new model while OpenClaw was running, the gateway might have cached the old model list. Restart the gateway after pulling new models.
Ollama not responding (ECONNREFUSED)
What you see: "ECONNREFUSED" when OpenClaw tries to reach Ollama, or the connection simply hangs.
What it means: Nothing is listening on the port OpenClaw is trying to connect to. Either Ollama isn't running, it's running on a different port, or a firewall is blocking the connection.
The fix: Verify Ollama is running and listening on the expected port. By default, Ollama serves on port 11434.
If Ollama is running on a remote machine or a different host (not localhost), make sure Ollama is bound to an accessible address. By default, Ollama only listens on 127.0.0.1, which means only the local machine can reach it. To allow connections from other machines or from WSL2, set the OLLAMA_HOST environment variable to 0.0.0.0:11434 before starting Ollama.
If you're running both OpenClaw and Ollama in Docker containers, they need to share a Docker network or use the host's network. Containers can't reach each other via localhost unless they're on the same network or using host networking mode.
For the broader OpenClaw setup sequence and where Ollama configuration fits in the process, our setup guide walks through each step in the correct order.
TUI fetch failed Ollama
What you see: The OpenClaw TUI (terminal user interface) shows "fetch failed" when you try to select or switch to an Ollama model.
What it means: This is the same underlying connection issue as the other fetch failed errors, but triggered from the TUI model selection interface instead of during startup. The TUI tries to query Ollama when you interact with the model picker, and the request fails.
The fix: All the same fixes apply: verify Ollama is running, check the port and URL, handle WSL2 networking, and pre-load models. The TUI doesn't have a different connection path. It uses the same provider configuration as the gateway.
One additional cause specific to the TUI: if you started OpenClaw without Ollama running, then started Ollama later, the TUI might have cached the failed connection state. Restart the OpenClaw gateway after starting Ollama to clear the cache.
Every Ollama fetch failed error comes back to the same question: can OpenClaw actually reach Ollama's HTTP API? Verify the URL, verify the port, verify the network path. The specific error variant tells you where in the process it failed, but the fix is always about making the connection work.
If debugging Ollama networking issues isn't how you want to spend your evening, Better Claw supports 28+ cloud model providers with zero local model configuration. $29/month per agent, BYOK. Pick your model from a dropdown. No Ollama, no fetch errors, no port conflicts. Your agent just works with cloud providers that have reliable API endpoints.
The root cause behind all of these errors
Here's the pattern. Every single error on this page is a variation of "OpenClaw tried to make an HTTP request to Ollama and it didn't work." The reasons vary (Ollama not running, wrong port, WSL2 boundary, model not loaded, firewall blocking), but the diagnostic approach is the same.
Can you reach Ollama's API from the same machine where OpenClaw is running? If yes, make sure your OpenClaw config points to the same URL. If no, fix the network path first.
OpenClaw's error messages for Ollama failures are frustratingly generic. "Fetch failed" could mean any of six different things. The project has 7,900+ open issues on GitHub, and better Ollama error messages have been requested multiple times. Until they improve, this page exists so you don't have to guess which "fetch failed" you're dealing with.
For the broader context of what works and what doesn't with Ollama and OpenClaw, our Ollama guide covers the streaming tool calling bug, recommended models, and whether local inference is worth the effort versus cloud APIs.
When to stop debugging and use a cloud provider instead
Here's what nobody tells you about OpenClaw Ollama fetch failed errors.
Even after you fix the connection, local models through Ollama have a fundamental limitation in OpenClaw: tool calling doesn't work. The streaming protocol drops tool call responses (GitHub Issue #5769). Your local model can chat but can't execute actions. No web searches, no file operations, no skill execution.
If you're debugging fetch failed errors so you can run a full agent with tool calling, cloud providers are the reliable path. DeepSeek costs $0.28/$0.42 per million tokens ($3–8/month for moderate usage). Gemini Flash has a free tier. Claude Haiku runs $1/$5 per million tokens. All of them have working tool calling. Our provider cost guide covers five options under $15/month with full agent capabilities.
If you're debugging fetch failed because you need complete data privacy, local models are worth the effort. Fix the connection, accept the chat-only limitation, and use the hybrid approach: Ollama for heartbeats and private conversations, cloud for everything that needs tool calling.
For the cheapest cloud alternatives to Ollama, our provider guide covers five options under $15/month with full agent capabilities.
If you want to skip Ollama entirely and get your agent running with reliable cloud providers in 60 seconds, BetterClaw supports 28+ cloud model providers with zero local model configuration. $29/month per agent, BYOK. Pick your model from a dropdown. No Ollama, no fetch errors, no port conflicts.
Frequently asked questions
What causes the OpenClaw Ollama "fetch failed" error?
The "fetch failed" error means OpenClaw can't reach Ollama's HTTP API. The most common causes are: Ollama not running, wrong port or URL in the OpenClaw config, WSL2 networking boundary (localhost doesn't cross WSL2/Windows), Ollama not finished loading the model (timeout), or a firewall blocking the connection. The fix is always about verifying the network path between OpenClaw and Ollama's API endpoint (default: http://127.0.0.1:11434).
How does "failed to discover Ollama models" differ from "fetch failed"?
"Fetch failed" means the HTTP connection itself failed. "Failed to discover Ollama models" means the connection might partially work but the model list query specifically fails, usually because Ollama hasn't finished loading a model. The fix for discovery failures: pre-load your model before starting OpenClaw, or define models explicitly in the config to bypass auto-discovery entirely.
How do I fix OpenClaw Ollama connection issues on WSL2?
WSL2 creates a network boundary between the Linux environment and the Windows host. 127.0.0.1 doesn't resolve across this boundary. If OpenClaw runs in WSL2 and Ollama runs on Windows (or vice versa), use the actual WSL2 IP address (from the hostname command) in your OpenClaw config instead of localhost. Also set OLLAMA_HOST to 0.0.0.0:11434 so Ollama accepts connections from outside localhost.
Is fixing Ollama fetch errors worth the effort versus using cloud APIs?
It depends on your use case. If you need data privacy (compliance, sensitive data), fixing Ollama is worth it for chat-only interactions. If you need full agent capabilities (tool calling, web search, skill execution), cloud APIs are more reliable because Ollama's streaming implementation breaks tool calling in OpenClaw (GitHub Issue #5769). Cloud providers like DeepSeek ($3–8/month) or Gemini Flash (free tier) cost less than most people expect and have working tool calling.
Will OpenClaw fix the Ollama error messages?
The error messages are a known complaint in the community. "Fetch failed" is too generic to be useful for debugging. Better Ollama-specific error messages have been requested in multiple GitHub issues. The project has 7,900+ open issues, so improvements may take time, especially with the transition to an open-source foundation following Peter Steinberger's move to OpenAI. Until then, this guide maps each generic error to its specific cause and fix.
Related Reading
- OpenClaw Local Model Not Working: Complete Fix Guide — Broader local model troubleshooting beyond Ollama fetch errors
- "Model Does Not Support Tools" Fix — Tool calling failures with Ollama models
- OpenClaw Ollama Guide: Complete Setup — Full Ollama integration setup from scratch
- OpenClaw Local Model Hardware Requirements — RAM, GPU, and storage specs for local inference
