[GH-ISSUE #11428] ollama pull failed since 0.9.6 version #54057

Closed
opened 2026-04-29 05:09:48 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @PierreRabreau on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11428

What is the issue?

since v0.9.6 version the registry url target to https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com instead of registry.ollama.ai

Relevant log output

the request ollama pull <model_name> failed with 
 "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/c6/c60c4f9f6a5c9bba665277b81941d09a2ae9a0f40ee90ca562484d31d03fdba3/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250715%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20250715T134557Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=510af0d3f5e697a448053882989ad46ceb993030d7d5ff356df16891ef04b948": tls: failed to verify certificate: x509: certificate signed by unknown authority

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @PierreRabreau on GitHub (Jul 15, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11428 ### What is the issue? since v0.9.6 version the registry url target to https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com instead of registry.ollama.ai ### Relevant log output ```shell the request ollama pull <model_name> failed with "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/c6/c60c4f9f6a5c9bba665277b81941d09a2ae9a0f40ee90ca562484d31d03fdba3/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250715%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20250715T134557Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=510af0d3f5e697a448053882989ad46ceb993030d7d5ff356df16891ef04b948": tls: failed to verify certificate: x509: certificate signed by unknown authority ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-29 05:09:48 -05:00
Author
Owner
<!-- gh-comment-id:3073708766 --> @PierreRabreau commented on GitHub (Jul 15, 2025): Ollama container tag used https://hub.docker.com/layers/ollama/ollama/latest/images/sha256-41cac4de8913952adc161777b5a241eaed84d49f2663e0f280ed960198beb099
Author
Owner

@rick-github commented on GitHub (Jul 15, 2025):

dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com is part of the CDN that servers ollama models. This sounds like you are behind a proxy. See here for configuring ollama for a proxy.

<!-- gh-comment-id:3074033262 --> @rick-github commented on GitHub (Jul 15, 2025): dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com is part of the CDN that servers ollama models. This sounds like you are behind a proxy. See [here](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-do-i-use-ollama-behind-a-proxy-in-docker) for configuring ollama for a proxy.
Author
Owner

@PierreRabreau commented on GitHub (Jul 16, 2025):

Yes it is , thanks for your anwser , but it was working find before with the endpoint registry.ollama.ai : for proxy security purpose we authorize endpoint within a white list.
and this endpoint (registry.ollama.ai) seems to be down since july

<!-- gh-comment-id:3077609647 --> @PierreRabreau commented on GitHub (Jul 16, 2025): Yes it is , thanks for your anwser , but it was working find before with the endpoint registry.ollama.ai : for proxy security purpose we authorize endpoint within a white list. and this endpoint (registry.ollama.ai) seems to be down since july
Author
Owner

@rick-github commented on GitHub (Jul 16, 2025):

registry.ollama.ai works fine for me at the moment.

<!-- gh-comment-id:3077619682 --> @rick-github commented on GitHub (Jul 16, 2025): registry.ollama.ai works fine for me at the moment.
Author
Owner

@PierreRabreau commented on GitHub (Jul 16, 2025):

yep, that's the way the de docker registry advertised the layer storage part which seems to have change
i will change my security setting to take that in count

<!-- gh-comment-id:3077743096 --> @PierreRabreau commented on GitHub (Jul 16, 2025): yep, that's the way the de docker registry advertised the layer storage part which seems to have change i will change my security setting to take that in count
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#54057