github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 08:59:13 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #2818] DNS i/o timeout when running ollama pull #1710

New Issue
Open
opened 2026-04-12 11:41:06 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-12 11:41:06 -05:00
Owner
Copy Link

Originally created by @sohanasarah on GitHub (Feb 28, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2818

Originally assigned to: @mxyng on GitHub.

Ollama was working perfectly on my machine, and I had llama2 installed. But now, when I try to install a new model, it gives me the following error:

pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/mixtral/manifests/latest": dial tcp: lookup registry.ollama.ai on 172.25.96.1:53: read udp 172.25.107.139:59735->172.25.96.1:53: i/o timeout

I tried to stop and restart the server. Remove the existing model and download it again. Nothing is working. Any suggestion on how to resolve this?

Originally created by @sohanasarah on GitHub (Feb 28, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2818 Originally assigned to: @mxyng on GitHub. Ollama was working perfectly on my machine, and I had llama2 installed. But now, when I try to install a new model, it gives me the following error: ``` pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/mixtral/manifests/latest": dial tcp: lookup registry.ollama.ai on 172.25.96.1:53: read udp 172.25.107.139:59735->172.25.96.1:53: i/o timeout ``` I tried to stop and restart the server. Remove the existing model and download it again. Nothing is working. Any suggestion on how to resolve this?
GiteaMirror commented 2026-04-12 11:41:09 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Feb 28, 2024):

read udp 172.25.107.139:59735->172.25.96.1:53

this suggests there's a dns error (port 53). is dns set up correctly?

<!-- gh-comment-id:1970015953 --> @mxyng commented on GitHub (Feb 28, 2024): > read udp 172.25.107.139:59735->172.25.96.1:53 this suggests there's a dns error (port 53). is dns set up correctly?
GiteaMirror commented 2026-04-12 11:41:09 -05:00
Author
Owner
Copy Link

@ewebgh33 commented on GitHub (Mar 1, 2024):

Are you using cmd or powershell on windows? I get that error in cmd but not powershell.

<!-- gh-comment-id:1972341390 --> @ewebgh33 commented on GitHub (Mar 1, 2024): Are you using cmd or powershell on windows? I get that error in cmd but not powershell.
GiteaMirror commented 2026-04-12 11:41:10 -05:00
Author
Owner
Copy Link

@gksoriginals commented on GitHub (Mar 11, 2024):

I am also facing a similar issue with the error dial tcp 34.120.132.20:443: i/o timeout is is something related to the internet setup ?

<!-- gh-comment-id:1987910184 --> @gksoriginals commented on GitHub (Mar 11, 2024): I am also facing a similar issue with the error `dial tcp 34.120.132.20:443: i/o timeout` is is something related to the internet setup ?
GiteaMirror commented 2026-04-12 11:41:11 -05:00
Author
Owner
Copy Link

@ricso commented on GitHub (Mar 14, 2024):

I have Ollama installed on a Mac Mini and running perfectly whilst the one running on a RPi5, which is on the same network, gives me the same error, which somewhat rules out network configuration (DNS, etc.), does it not?

<!-- gh-comment-id:1997465305 --> @ricso commented on GitHub (Mar 14, 2024): I have Ollama installed on a Mac Mini and running perfectly whilst the one running on a RPi5, which is on the same network, gives me the same error, which somewhat rules out network configuration (DNS, etc.), does it not?
GiteaMirror commented 2026-04-12 11:41:11 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Mar 21, 2024):

I wonder if this might be the result of our parallelization saturating a slow internet connection, which results in cascading failures when short timeouts hit.

<!-- gh-comment-id:2012269947 --> @dhiltgen commented on GitHub (Mar 21, 2024): I wonder if this might be the result of our parallelization saturating a slow internet connection, which results in cascading failures when short timeouts hit.
GiteaMirror commented 2026-04-12 11:41:12 -05:00
Author
Owner
Copy Link

@racksen commented on GitHub (Apr 8, 2024):

This could be an issue when you are using VPN or behind any firewall.

<!-- gh-comment-id:2043524523 --> @racksen commented on GitHub (Apr 8, 2024): This could be an issue when you are using VPN or behind any firewall.
GiteaMirror commented 2026-04-12 11:41:13 -05:00
Author
Owner
Copy Link

@SleeplessBegonia commented on GitHub (May 27, 2024):

I am also facing a similar issue with the error dial tcp 34.120.132.20:443: i/o timeout is is something related to the internet setup ?

me too.how did u solve it?

<!-- gh-comment-id:2133531861 --> @SleeplessBegonia commented on GitHub (May 27, 2024): > I am also facing a similar issue with the error `dial tcp 34.120.132.20:443: i/o timeout` is is something related to the internet setup ? me too.how did u solve it?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#1710
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?