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

[GH-ISSUE #3452] Pulling manifest fails with error "read: connection reset by peer" #48641

New Issue
Closed
opened 2026-04-28 08:58:31 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-28 08:58:31 -05:00
Owner
Copy Link

Originally created by @chopeen on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3452

What is the issue?

After upgrading from 0.1.27 to 0.1.30, I can no longer pull models when connected to a corporate network:

$ ollama pull codellama

pulling manifest 
Error: pull model manifest: Get "https://ollama.com/token?nonce=VV5GsyYSIqo_4gO3ILCHrA&scope=repository%!A(MISSING)library%!F(MISSING)codellama%!A(MISSING)pull&service=ollama.com&ts=1712050312": read tcp 10.144.68.189:56764->34.120.132.20:443: read: connection reset by peer

What did you expect to see?

The model codellama should be pulled and saved locally.

Steps to reproduce

  1. Connect to corporate network
  2. Run ollama pull ... or ollama run ... for any model not present locally

Are there any recent changes that introduced the issue?

It used to work in December.

I downgraded and tested two Ollama versions from the past - both 0.1.24 and 0.1.27 are able to pull models on the corporate network. The issue appeared in version 0.1.28.

OS

Linux

Architecture

x86

Platform

No response

Ollama version

0.1.30

GPU

No response

GPU info

No GPU

CPU

Intel

Other software

No response

Originally created by @chopeen on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3452 ### What is the issue? After upgrading from `0.1.27` to `0.1.30`, I can no longer pull models when connected to a corporate network: ``` $ ollama pull codellama pulling manifest Error: pull model manifest: Get "https://ollama.com/token?nonce=VV5GsyYSIqo_4gO3ILCHrA&scope=repository%!A(MISSING)library%!F(MISSING)codellama%!A(MISSING)pull&service=ollama.com&ts=1712050312": read tcp 10.144.68.189:56764->34.120.132.20:443: read: connection reset by peer ``` ### What did you expect to see? The model `codellama` should be pulled and saved locally. ### Steps to reproduce 1. Connect to corporate network 2. Run `ollama pull ...` or `ollama run ...` for any model not present locally ### Are there any recent changes that introduced the issue? It used to work in December. I downgraded and tested two Ollama versions from the past - both `0.1.24` and `0.1.27` are able to pull models on the corporate network. The issue appeared in version `0.1.28`. ### OS Linux ### Architecture x86 ### Platform _No response_ ### Ollama version 0.1.30 ### GPU _No response_ ### GPU info No GPU ### CPU Intel ### Other software _No response_
GiteaMirror added the bug label 2026-04-28 08:58:31 -05:00
GiteaMirror commented 2026-04-28 08:58:33 -05:00
Author
Owner
Copy Link

@chopeen commented on GitHub (Apr 9, 2024):

A configuration change was implemented in the aforementioned corporate network, so I am no longer able to reproduce this issue and help testing any potential changes.

<!-- gh-comment-id:2044708601 --> @chopeen commented on GitHub (Apr 9, 2024): A configuration change was implemented in the aforementioned corporate network, so I am no longer able to reproduce this issue and help testing any potential changes.
GiteaMirror commented 2026-04-28 08:58:33 -05:00
Author
Owner
Copy Link

@fzyabc commented on GitHub (Apr 25, 2024):

Can the author teach me how to downgrade

<!-- gh-comment-id:2077724160 --> @fzyabc commented on GitHub (Apr 25, 2024): Can the author teach me how to downgrade
GiteaMirror commented 2026-04-28 08:58:34 -05:00
Author
Owner
Copy Link

@chopeen commented on GitHub (Apr 25, 2024):

The details depend on your OS and how you install Ollama, but in general under Releases you can find old Ollama versions, e.g. https://github.com/ollama/ollama/releases/tag/v0.1.27.

<!-- gh-comment-id:2077731531 --> @chopeen commented on GitHub (Apr 25, 2024): The details depend on your OS and how you install Ollama, but in general under Releases you can find old Ollama versions, e.g. https://github.com/ollama/ollama/releases/tag/v0.1.27.
GiteaMirror commented 2026-04-28 08:58:35 -05:00
Author
Owner
Copy Link

@fzyabc commented on GitHub (Apr 26, 2024):

详细信息取决于您的操作系统和安装 Ollama 的方式，但通常在“版本”下，您可以找到旧的 Ollama 版本，例如 https://github.com/ollama/ollama/releases/tag/v0.1.27。

Thank you so much!Solved,It's because of the version problem.,Download version 0.1.27 no problem.

<!-- gh-comment-id:2078495444 --> @fzyabc commented on GitHub (Apr 26, 2024): > 详细信息取决于您的操作系统和安装 Ollama 的方式，但通常在“版本”下，您可以找到旧的 Ollama 版本，例如 https://github.com/ollama/ollama/releases/tag/v0.1.27。 Thank you so much!Solved,It's because of the version problem.,Download version 0.1.27 no problem.
GiteaMirror commented 2026-04-28 08:58:36 -05:00
Author
Owner
Copy Link

@mjdacs commented on GitHub (Jul 1, 2024):

Since the security vuln and subsequent patch in 0.1.34 I now get this error message again.

<!-- gh-comment-id:2200915649 --> @mjdacs commented on GitHub (Jul 1, 2024): Since the security vuln and subsequent patch in 0.1.34 I now get this error message again.
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 bug
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#48641
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?