#Ollama API error 500

14 messages · Page 1 of 1 (latest)

stoic latch
#

"error":"Internal Server Error

#

: {"error":"Internal Server Error (ref: d71bec0a-2ab1-48e1-864d-9a377e75aa8f)"}

void deltaBOT
#

That error string alone is too thin to diagnose, but a couple common Ollama/OpenClaw gotchas jump out.

First, can you paste these:

openclaw --version
openclaw status --all
openclaw logs --follow

Then trigger the failure once and paste the relevant log lines.

Also, if you configured Ollama manually, check this part carefully:

  • good: baseUrl: "http://host:11434"
  • bad: baseUrl: "http://host:11434/v1"
#

OpenClaw wants the native Ollama API, not the OpenAI-compatible /v1 route. Docs: https://docs.openclaw.ai/providers/ollama

If you are actually going through a stricter OpenAI-compatible local backend, two other common fixes are:

  • compat.requiresStringContent: true
  • compat.supportsTools: false or agents.defaults.localModelMode: "lean"

Relevant docs:

If you paste:

  1. your version,
  2. the provider config snippet, and
  3. the first real log error after reproducing,
#

I can usually narrow it down pretty fast.

#

Yep, that ref helps a bit, but the real cause will be in your local gateway log.

Please paste these, in one message if you can:

openclaw --version
openclaw status --all
openclaw models status
openclaw logs --follow

Then reproduce the error once while openclaw logs --follow is running, and paste the lines around that failure.

Also tell me:

  • your Ollama baseUrl
  • whether you used onboarding or manual config
#
  • what model you selected

One very common fix, if you configured Ollama manually:

  • use http://host:11434
  • not http://host:11434/v1

OpenClaw wants native Ollama API for tool calling. Docs: https://docs.openclaw.ai/providers/ollama

If you want, paste your models.providers.ollama config snippet too, and I’ll sanity-check it.

stoic latch
#

C:\Windows\System32>openclaw models status

🦞 OpenClaw 2026.3.24 (cff6dc9) — I can run local, remote, or purely on vibes—results may vary with DNS.

Config : ~.openclaw\openclaw.json
Agent dir : ~.openclaw\agents\main\agent
Default : ollama/minimax-m2.7:cloud
Fallbacks (0) : -
Image model : anthropic/moondream
Image fallbacks (0): -
Aliases (1) : Gemma -> ollama/gemma:2b
Configured models (4): ollama/qwen2.5:3b, ollama/minimax-m2.7:cloud, ollama/gemma:2b, anthropic/moondream

Auth overview
Auth store : ~.openclaw\agents\main\agent\auth-profiles.json
Shell env : off
Providers w/ OAuth/tokens (1): openai-codex (1)

  • ollama effective=profiles:~.openclaw\agents\main\agent\auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | ollama:default=marker(ollama-local) | env=5bfe51c6...Y29dDoDB | source=env: OLLAMA_API_KEY | models.json=5bfe51c6...Y29dDoDB | source=models.json: ~.openclaw\agents\main\agent\models.json
  • openai-codex effective=profiles:~.openclaw\agents\main\agent\auth-profiles.json | profiles=1 (oauth=1, token=0, api_key=0) | openai-codex:default=OAuth

Missing auth

  • anthropic Run openclaw models auth login --provider anthropic, openclaw configure, or set an API key env var.

OAuth/token status

  • openai-codex usage: 168h 51% left ⏱23h 31m
    • openai-codex:default ok expires in 8d

C:\Windows\System32>

void deltaBOT
#

This is useful, I see your default model is ollama/minimax-m2.7:cloud.

So the first question is whether the problem is:

  1. that specific Ollama cloud model, or
  2. your whole Ollama/OpenClaw setup

Quickest split-test:

ollama signin
openclaw infer model run --model ollama/gemma:2b --prompt "hi" --json
openclaw infer model run --model ollama/minimax-m2.7:cloud --prompt "hi" --json

And in another terminal:

# 
openclaw logs --follow

Then paste what happens.

What I’m looking for:

  • gemma:2b works, minimax-m2.7:cloud fails
    → likely Ollama cloud sign-in / Ollama cloud model issue

  • both fail
    → likely provider config/base URL issue, or a broader Ollama runtime problem

Also please paste your models.providers.ollama config snippet if you have one, especially:

  • baseUrl
#
  • api

One very common bad config is using /v1. For Ollama, it should usually be:

baseUrl: "http://host:11434",
api: "ollama"

not:

baseUrl: "http://host:11434/v1"

Docs:

stoic latch
#

Leave it worked by compacting, reseting the session and at last restarting my pc 😐

void deltaBOT
#

Nice, glad you got it unstuck.

That smells more like a stale session/runtime state than a pure Ollama config issue, especially since compacting + session reset + reboot fixed it.

I’d still do two things when you get a minute:

  1. update OpenClaw when you can, you were a bit behind on 2026.3.24
  2. if it happens again, grab:
    openclaw status --all
openclaw logs --follow
    before rebooting, so there’s something actionable to trace

Glad that helped! 🎉
If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution.
That helps Answer Overflow index the solution for future users.