[GH-ISSUE #9571] fail to carry out command:"ollama run deepseek-r1:1.5b" #32002

Closed
opened 2026-04-22 12:52:36 -05:00 by GiteaMirror · 9 comments
Owner

Originally created by @lonely83 on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9571

C:\Users\LENOVO>ollama run deepseek-r1:1.5b
pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b": read tcp 192.168.3.184:62157->104.21.75.227:443: wsarecv: An existing connection was forcibly closed by the remote host.

app.log

server.log

config.json

Originally created by @lonely83 on GitHub (Mar 7, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9571 C:\Users\LENOVO>ollama run deepseek-r1:1.5b pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b": read tcp 192.168.3.184:62157->104.21.75.227:443: wsarecv: An existing connection was forcibly closed by the remote host. [app.log](https://github.com/user-attachments/files/19124382/app.log) [server.log](https://github.com/user-attachments/files/19124384/server.log) [config.json](https://github.com/user-attachments/files/19124386/config.json)
GiteaMirror added the networking label 2026-04-22 12:52:36 -05:00
Author
Owner

@rick-github commented on GitHub (Mar 7, 2025):

Could be a temporary network issue, have you tried re-running the command? If it fails again, what's the output of:

curl -v https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b
<!-- gh-comment-id:2706122051 --> @rick-github commented on GitHub (Mar 7, 2025): Could be a temporary network issue, have you tried re-running the command? If it fails again, what's the output of: ``` curl -v https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b ```
Author
Owner

@lonely83 commented on GitHub (Mar 7, 2025):

Could be a temporary network issue, have you tried re-running the command? If it fails again, what's the output of:

curl -v https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b

C:\Users\LENOVO>curl -v https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b

  • Host registry.ollama.ai:443 was resolved.
  • IPv6: (none)
  • IPv4: 104.21.75.227, 172.67.182.229
  • Trying 104.21.75.227:443...
  • schannel: disabled automatic use of client certificate
  • ALPN: curl offers http/1.1
  • Recv failure: Connection was reset
  • schannel: failed to receive handshake, SSL/TLS connection failed
  • closing connection #0
    curl: (35) Recv failure: Connection was reset
<!-- gh-comment-id:2706140568 --> @lonely83 commented on GitHub (Mar 7, 2025): > Could be a temporary network issue, have you tried re-running the command? If it fails again, what's the output of: > > ``` > curl -v https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b > ``` C:\Users\LENOVO>curl -v https://registry.ollama.ai/v2/library/deepseek-r1/manifests/1.5b * Host registry.ollama.ai:443 was resolved. * IPv6: (none) * IPv4: 104.21.75.227, 172.67.182.229 * Trying 104.21.75.227:443... * schannel: disabled automatic use of client certificate * ALPN: curl offers http/1.1 * Recv failure: Connection was reset * schannel: failed to receive handshake, SSL/TLS connection failed * closing connection #0 curl: (35) Recv failure: Connection was reset
Author
Owner

@rick-github commented on GitHub (Mar 7, 2025):

Are you behind a proxy? Any firewall/filtering?

<!-- gh-comment-id:2706156752 --> @rick-github commented on GitHub (Mar 7, 2025): Are you behind a proxy? Any firewall/filtering?
Author
Owner

@lonely83 commented on GitHub (Mar 7, 2025):

Are you behind a proxy? Any firewall/filtering?

No, The first time I executed the command, I was able to download it successfully. However, when I downloaded the 7B model later, I closed the command before the download was complete, which resulted in an error message when executing the command later.

<!-- gh-comment-id:2706192890 --> @lonely83 commented on GitHub (Mar 7, 2025): > Are you behind a proxy? Any firewall/filtering? No, The first time I executed the command, I was able to download it successfully. However, when I downloaded the 7B model later, I closed the command before the download was complete, which resulted in an error message when executing the command later.
Author
Owner

@rick-github commented on GitHub (Mar 7, 2025):

The previously stopped download is not what's causing the current errors. Your machine is unable to connect to registry.ollama.ai. What's the output of:

tracert registry.ollama.ai
<!-- gh-comment-id:2706221122 --> @rick-github commented on GitHub (Mar 7, 2025): The previously stopped download is not what's causing the current errors. Your machine is unable to connect to registry.ollama.ai. What's the output of: ``` tracert registry.ollama.ai ```
Author
Owner

@lonely83 commented on GitHub (Mar 7, 2025):

The previously stopped download is not what's causing the current errors. Your machine is unable to connect to registry.ollama.ai. What's the output of:

tracert registry.ollama.ai

Image

Image

<!-- gh-comment-id:2706271429 --> @lonely83 commented on GitHub (Mar 7, 2025): > The previously stopped download is not what's causing the current errors. Your machine is unable to connect to registry.ollama.ai. What's the output of: > > ``` > tracert registry.ollama.ai > ``` ![Image](https://github.com/user-attachments/assets/b4e9f0ce-679a-41da-8694-51926473946d) ![Image](https://github.com/user-attachments/assets/2a5fdb68-b324-434f-8603-dace08e812dd)
Author
Owner

@rick-github commented on GitHub (Mar 7, 2025):

If you can reach it via the browser but not the command line, that seems like a proxy/firewall issue.

<!-- gh-comment-id:2706285276 --> @rick-github commented on GitHub (Mar 7, 2025): If you can reach it via the browser but not the command line, that seems like a proxy/firewall issue.
Author
Owner

@lonely83 commented on GitHub (Mar 7, 2025):

If you can reach it via the browser but not the command line, that seems like a proxy/firewall issue.

How can I determine the cause of the problem?

<!-- gh-comment-id:2706292839 --> @lonely83 commented on GitHub (Mar 7, 2025): > If you can reach it via the browser but not the command line, that seems like a proxy/firewall issue. How can I determine the cause of the problem?
Author
Owner

@rick-github commented on GitHub (Mar 7, 2025):

Speak to your network administrator.

<!-- gh-comment-id:2706498707 --> @rick-github commented on GitHub (Mar 7, 2025): Speak to your network administrator.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#32002