[GH-ISSUE #10766] pulling manifest Error: max retries exceeded: Get #53586

Closed
opened 2026-04-29 03:54:44 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @rohaanuv on GitHub (May 18, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10766

What is the issue?

When I execute ollama run llama2 command getting following error .
To resolve this i try follwing things still getting sam error below ollama run and ollama pull both commands still not working in India.
Temporary DNS Change (Linux/macOS)
Run:

sudo nano /etc/resolv.conf
Replace existing entries with:

nameserver 1.1.1.1
nameserver 8.8.8.8

I also saw that it is fixed but it is still there i am trying to pull models ffrom last 3 days. if you have any alternative way please let me know.

Relevant log output

pulling manifest 
Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/26/2609048d349e7c70196401be59bea7eb89a968d4642e409b0e798b34403b96c8/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250518%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20250518T160802Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=de2b516c7a37d24bf292eda5ec61b4d6b1c3d3672d81e44f7e6e7145fa12431d": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host

OS

macOS

GPU

No response

CPU

Apple

Ollama version

0.7.0

Originally created by @rohaanuv on GitHub (May 18, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10766 ### What is the issue? When I execute `ollama run llama2 ` command getting following error . To resolve this i try follwing things still getting sam error below ollama run and ollama pull both commands still not working in India. Temporary DNS Change (Linux/macOS) Run: sudo nano /etc/resolv.conf Replace existing entries with: nameserver 1.1.1.1 nameserver 8.8.8.8 I also saw that it is fixed but it is still there i am trying to pull models ffrom last 3 days. if you have any alternative way please let me know. ### Relevant log output ```shell pulling manifest Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/26/2609048d349e7c70196401be59bea7eb89a968d4642e409b0e798b34403b96c8/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250518%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20250518T160802Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=de2b516c7a37d24bf292eda5ec61b4d6b1c3d3672d81e44f7e6e7145fa12431d": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host ``` ### OS macOS ### GPU _No response_ ### CPU Apple ### Ollama version 0.7.0
GiteaMirror added the bugnetworking labels 2026-04-29 03:54:51 -05:00
Author
Owner

@rick-github commented on GitHub (May 19, 2025):

This is likely #8605, although switching DNS servers usually fixes it. Follow the instructions in https://github.com/ollama/ollama/issues/8605#issuecomment-2639100703 and post the results.

<!-- gh-comment-id:2890265027 --> @rick-github commented on GitHub (May 19, 2025): This is likely #8605, although switching DNS servers usually fixes it. Follow the instructions in https://github.com/ollama/ollama/issues/8605#issuecomment-2639100703 and post the results.
Author
Owner

@rohaanuv commented on GitHub (May 19, 2025):

I run following commands and test the endpoint dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com using mxtoolbox.com I am getting following issues and errors. It looks like someone deleted records from hosted zones.

dig dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com
nslookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com

Image Image Image

Note.
It is work in mobile/Celluer data/internet provider but if you use star link like JIO Fiber like providers.

<!-- gh-comment-id:2891423380 --> @rohaanuv commented on GitHub (May 19, 2025): I run following commands and test the endpoint `dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com` using mxtoolbox.com I am getting following issues and errors. It looks like someone deleted records from hosted zones. `dig dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com` `nslookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com` <img width="1045" alt="Image" src="https://github.com/user-attachments/assets/ea3adecb-70ec-455e-b2cd-9fe151f6a163" /> <img width="1039" alt="Image" src="https://github.com/user-attachments/assets/1365b10c-6c7e-4114-9436-9ce6f861189a" /> <img width="1505" alt="Image" src="https://github.com/user-attachments/assets/8293e949-0e49-44b9-a6f5-20a149c98d90" /> Note. It is work in mobile/Celluer data/internet provider but if you use star link like JIO Fiber like providers.
Author
Owner

@rootkink commented on GitHub (Jul 28, 2025):


same problem

dial tcp: lookup ...r2.cloudflarestorage.com: no such host — DNS record missing from Cloudflare R2 (not local issue)


What is the issue?

Running ollama pull or ollama run results in a DNS error:

Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/...":
dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host

This happens regardless of internet connection or DNS provider used. MXToolbox confirms the domain is not resolving publicly — indicating the issue is with Cloudflare DNS configuration, not the client environment.


What happened? What did you expect to happen?

Expected Ollama to pull and run models normally.

Instead, model pulls fail with a no such host error due to DNS lookup failure on Cloudflare R2 object storage.

I expected the DNS record dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com to resolve successfully. However, it does not exist publicly — and appears to have been deleted or is misconfigured.


Relevant log output

ollama pull qwen3
pulling manifest
Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/...": 
dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host
nslookup r2.cloudflarestorage.com
Server:  UnKnown
Address:  10.58.11.4

DNS request timed out.

What I’ve tried (to rule out client-side problems)

  • Changed DNS to 1.1.1.1 and 1.0.0.1
  • Flushed DNS (ipconfig /flushdns)
  • Switched to mobile hotspot
  • Disabled firewall + antivirus
  • Confirmed DNS lookup fails using nslookup and ping
  • Tried test models from Ollama’s staging server (e.g. issue1736.ollama.dev/library/llama3:8b) — still fail
  • Verified with [MXToolbox](https://mxtoolbox.com)

MXToolbox DNS Diagnostic Results

Used [mxtoolbox.com](https://mxtoolbox.com) to test dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com and cloudflarestorage.com. The following issues were found:

DNS Errors

  • No A record found
  • No DMARC / SPF / DKIM records
  • SOA Serial Number format is invalid
  • SOA Expire Value is out of range
  • HTTP request timed out (connection to root domain failed)

Name Servers

  • No recursive name server detected
  • Name servers are valid but report no data for the R2 bucket subdomain

This confirms that the DNS record is missing or broken at the origin, not blocked on the client side.


OS

Windows 11 Home 64-bit (10.0, Build 22631)


GPU

NVIDIA GeForce RTX 3050-6GB


CPU

Intel Core i5 13th Gen-13450HX


Ollama version

ollama --version
ollama version is 0.9.6
<!-- gh-comment-id:3126021409 --> @rootkink commented on GitHub (Jul 28, 2025): --- same problem `dial tcp: lookup ...r2.cloudflarestorage.com: no such host` — DNS record missing from Cloudflare R2 (not local issue) --- ### **What is the issue?** Running `ollama pull` or `ollama run` results in a DNS error: ``` Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/...": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host ``` This happens regardless of internet connection or DNS provider used. MXToolbox confirms the domain is not resolving publicly — indicating the issue is with **Cloudflare DNS configuration**, not the client environment. --- ### **What happened? What did you expect to happen?** Expected Ollama to pull and run models normally. Instead, model pulls fail with a `no such host` error due to DNS lookup failure on Cloudflare R2 object storage. I expected the DNS record `dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com` to resolve successfully. However, it does not exist publicly — and appears to have been deleted or is misconfigured. --- ### **Relevant log output** ```sh ollama pull qwen3 pulling manifest Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/...": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host ``` ```sh nslookup r2.cloudflarestorage.com Server: UnKnown Address: 10.58.11.4 DNS request timed out. ``` --- ### **What I’ve tried (to rule out client-side problems)** * Changed DNS to `1.1.1.1` and `1.0.0.1` * Flushed DNS (`ipconfig /flushdns`) * Switched to mobile hotspot * Disabled firewall + antivirus * Confirmed DNS lookup fails using `nslookup` and `ping` * Tried test models from Ollama’s staging server (e.g. `issue1736.ollama.dev/library/llama3:8b`) — still fail * Verified with [[MXToolbox](https://mxtoolbox.com/)](https://mxtoolbox.com) --- ### **MXToolbox DNS Diagnostic Results** Used [[mxtoolbox.com](https://mxtoolbox.com/)](https://mxtoolbox.com) to test `dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com` and `cloudflarestorage.com`. The following issues were found: #### DNS Errors * No A record found * No DMARC / SPF / DKIM records * SOA Serial Number format is invalid * SOA Expire Value is out of range * HTTP request timed out (connection to root domain failed) #### Name Servers * No recursive name server detected * Name servers are valid but report no data for the R2 bucket subdomain This confirms that the DNS record is **missing or broken at the origin**, not blocked on the client side. --- ### **OS** Windows 11 Home 64-bit (10.0, Build 22631) --- ### **GPU** NVIDIA GeForce RTX 3050-6GB --- ### **CPU** Intel Core i5 13th Gen-13450HX --- ### **Ollama version** ```bash ollama --version ollama version is 0.9.6 ```
Author
Owner

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

$ host dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com
dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has address 172.66.1.46
dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has address 162.159.141.50
dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has IPv6 address 2606:4700:7::12e
dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has IPv6 address 2a06:98c1:58::12e

It doesn't have an MX record because it doesn't receive email so using mxtoolbox.com doesn't provide any useful information.

$ host -t mx dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com
dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has no MX record

What happens if you ask 1.1.1.1 directly?

$ nslookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com 1.1.1.1
Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
Name:	dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com
Address: 162.159.141.50
Name:	dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com
Address: 172.66.1.46
Name:	dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com
Address: 2606:4700:7::12e
Name:	dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com
Address: 2a06:98c1:58::12e
<!-- gh-comment-id:3126044593 --> @rick-github commented on GitHub (Jul 28, 2025): ``` $ host dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has address 172.66.1.46 dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has address 162.159.141.50 dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has IPv6 address 2606:4700:7::12e dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has IPv6 address 2a06:98c1:58::12e ``` It doesn't have an MX record because it doesn't receive email so using mxtoolbox.com doesn't provide any useful information. ``` $ host -t mx dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com has no MX record ``` What happens if you ask 1.1.1.1 directly? ``` $ nslookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com 1.1.1.1 Server: 1.1.1.1 Address: 1.1.1.1#53 Non-authoritative answer: Name: dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com Address: 162.159.141.50 Name: dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com Address: 172.66.1.46 Name: dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com Address: 2606:4700:7::12e Name: dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com Address: 2a06:98c1:58::12e ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#53586