[Bug]: Ollama Cloud Authentication fails with 401 after update to 2026.3.31

[Felox63]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

After updating OpenClaw from version 2026.3.24 to 2026.3.31, all requests to Ollama Cloud models fail with HTTP 401 "unauthorized". The same API key works perfectly when tested directly via curl against the Ollama API.

Steps to reproduce

Have a working setup with Ollama Cloud provider on version ≤2026.3.24
Update OpenClaw to version 2026.3.31
Attempt to use any Ollama Cloud model (e.g., kimi-k2.5:cloud)
Observe 401 authentication errors
Also on 2026.04.01

Expected behavior

Ollama Cloud requests should authenticate successfully using the configured API key, as they did in version 2026.3.24.

Actual behavior

HTTP 401: unauthorized
failoverReason: auth
model: kimi-k2.5:cloud
provider: ollama
rawErrorPreview: 401 unauthorized

OpenClaw version

2026.4.1

Operating system

6.12.74+deb13+1-amd64

Install method

pnpm

Model

Ollama Cloud

Provider / routing chain

openclaw ollama all llm

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Tested with baseUrl: "https://ollama.com/api" → Results in 404 (double /api/api/chat path)
Tried restarting gateway after config changes
Token is confirmed valid via direct API call
Issue appears to be in how OpenClaw 2026.3.31 constructs/sends the Authorization header

Impact and severity

No response

Additional information

No response

[neeravmakwana]

Tracked in #59310.

I reproduced this against current main: the stored ollama:default profile can return the synthetic ollama-local key before real Ollama env/config credentials are considered, which makes direct cloud requests send the wrong bearer token.

The PR defers that synthetic profile until after real Ollama auth sources are checked, while still keeping local-only Ollama setups working as a fallback.

[athuljayaram]

same error

[jbillington]

same for me using openclaw 4.2

[MYJarvisClaw]

This "HTTP: 401 unauthorized" error was from v2026.3.28 all the way to the current version.

[Felox63]

Anyone tested it with a new build?

[MYJarvisClaw]

@Felox63, I only tested it on 4.2 and same error. I haven't tried to test on version after 4.2

[MYJarvisClaw]

@Felox63 , I took a leap of faith to upgrade from v2026.3.24 (last version before Ollama Cloud auth starts to fail) to v2026.4.15. Looks like the issue is fixed "somehow" between 4.2 and 4.15 although this ticket is still open. I think we should close this bug.

[Felox63]

@MYJarvisClaw Yeah! Thank you. I also tested it. It works fine. I´ll close this case