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

[GH-ISSUE #12478] Proposal: Improve install.sh robustness for unreliable connections (curl --retry options) #34051

New Issue
Open
opened 2026-04-22 17:17:01 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-22 17:17:01 -05:00
Owner
Copy Link

Originally created by @Alogani on GitHub (Oct 2, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12478

Proposal: Improve install.sh robustness for unreliable connections (curl --retry options)

Summary

Many users—including myself—have experienced frequent interruptions, "max retries exceeded", and TLS/curl errors when installing or downloading models via the official install.sh script, especially on slow or unstable connections. There are multiple open and closed issues on this topic (see references below).

Proposal:
To improve reliability for all users, especially those with poor connections, please consider a simple patch to your scripts/install.sh:

sed -i -E 's/(^|[;&|]) *curl /&--connect-timeout 5 --retry 9999 --retry-delay 2 --retry-max-time 0 /' install.sh

This will ensure that every curl invocation in the script is far more robust to transient network issues, and will retry aggressively as needed.

Rationale & References

Request

Would maintainers consider this patch acceptable? This would immediately improve install reliability for a large portion of the user base with minimal risk.

In that case, a maintainer or I can open a PR for a quick change.

Originally created by @Alogani on GitHub (Oct 2, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12478 ### Proposal: Improve install.sh robustness for unreliable connections (curl --retry options) #### Summary Many users—including myself—have experienced frequent interruptions, "max retries exceeded", and TLS/curl errors when installing or downloading models via the official `install.sh` script, especially on slow or unstable connections. There are multiple open and closed issues on this topic (see references below). **Proposal:** To improve reliability for all users, especially those with poor connections, please consider a simple patch to your `scripts/install.sh`: ```bash sed -i -E 's/(^|[;&|]) *curl /&--connect-timeout 5 --retry 9999 --retry-delay 2 --retry-max-time 0 /' install.sh ``` This will ensure that every `curl` invocation in the script is far more robust to transient network issues, and will retry aggressively as needed. #### Rationale & References - There are some open issues about failed download attempt—examples: - [Install script curl issues](https://github.com/ollama/ollama/issues/12343) - #12454 - #8359 - The retry logic is a standard best practice for `curl` in installer scripts (see also [curl docs](https://curl.se/docs/manpage.html#--retry)). - The patch is non-intrusive: it does not change URLs, file handling, or script logic—only adds retry logic to all curl invocations. #### Request Would maintainers consider this patch acceptable? This would immediately improve install reliability for a large portion of the user base with minimal risk. In that case, a maintainer or I can open a PR for a quick change.
GiteaMirror added the feature request label 2026-04-22 17:17:01 -05:00
GiteaMirror commented 2026-04-22 17:17:02 -05:00
Author
Owner
Copy Link

@maternion commented on GitHub (Oct 3, 2025):

Yes please, this would be highly appreciated. Not having a fast and stable connection makes it impossible to install using curl. I had to change the script to use aria2c and add resume and retry capabilities. So even if any error occurs, i don't lose the download progress made.

<!-- gh-comment-id:3364692699 --> @maternion commented on GitHub (Oct 3, 2025): Yes please, this would be highly appreciated. Not having a fast and stable connection makes it impossible to install using curl. I had to change the script to use aria2c and add resume and retry capabilities. So even if any error occurs, i don't lose the download progress made.
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 feature request
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#34051
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?