github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 17:49:24 -05:00
Code Issues 14.6k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #13740] Need Help: Model Upload Fails with “413 Request Entity Too Large” for 100GB File #9006

New Issue
Closed
opened 2026-04-12 21:49:58 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 21:49:58 -05:00
Owner
Copy Link

Originally created by @CharlesKaiGao on GitHub (Jan 16, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/13740

What is the issue?

Dear Ollama Team,

My account is AntAngelMed (sikuaishitong@sina.com). I encountered an error while uploading a model, which is approximately 100GB in size. During the upload process, I consistently received the following prompt: "Error: max retries exceeded: http status 413 Request Entity Too Large".

The full error HTML response is:

Image

I have searched for related issues in the Ollama GitHub repository but found no existing solutions or discussions regarding this upload size limit and the 413 error.

Could you please advise on how to resolve this? Is there a different method or endpoint for uploading very large models, or perhaps a setting that needs to be adjusted on the server side? Any guidance would be greatly appreciated.

Thank you for your time and support.

Relevant log output

root@owner-Lenovo-WenTian-WA5480-G3:/data/llm/AntAngelMed# ollama push AntAngelMed/AntAngelMed:100b-q8_0
retrieving manifest 
pushing 59059f0b4967...   1% ▕█                                                                                                               ▏   1 GB/109 GB                  
Error: max retries exceeded: http status 413 Request Entity Too Large: 
<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>413 Request Entity Too Large</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Request Entity Too Large</h1>
<h2>Your client issued a request that was too large.
</h2>
<h2></h2>
</body></html>

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.13.5

Originally created by @CharlesKaiGao on GitHub (Jan 16, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/13740 ### What is the issue? Dear Ollama Team, My account is AntAngelMed ([sikuaishitong@sina.com](mailto:sikuaishitong@sina.com)). I encountered an error while uploading a model, which is approximately 100GB in size. During the upload process, I consistently received the following prompt: "Error: max retries exceeded: http status 413 Request Entity Too Large". The full error HTML response is: <img width="1113" height="227" alt="Image" src="https://github.com/user-attachments/assets/534032fb-2615-4768-b9d3-338fb2aaf7a4" /> I have searched for related issues in the Ollama GitHub repository but found no existing solutions or discussions regarding this upload size limit and the 413 error. Could you please advise on how to resolve this? Is there a different method or endpoint for uploading very large models, or perhaps a setting that needs to be adjusted on the server side? Any guidance would be greatly appreciated. Thank you for your time and support. ### Relevant log output ```shell root@owner-Lenovo-WenTian-WA5480-G3:/data/llm/AntAngelMed# ollama push AntAngelMed/AntAngelMed:100b-q8_0 retrieving manifest pushing 59059f0b4967... 1% ▕█ ▏ 1 GB/109 GB Error: max retries exceeded: http status 413 Request Entity Too Large: <html><head> <meta http-equiv="content-type" content="text/html;charset=utf-8"> <title>413 Request Entity Too Large</title> </head> <body text=#000000 bgcolor=#ffffff> <h1>Error: Request Entity Too Large</h1> <h2>Your client issued a request that was too large. </h2> <h2></h2> </body></html> ``` ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.13.5
GiteaMirror added the bug label 2026-04-12 21:49:58 -05:00
GiteaMirror commented 2026-04-12 21:49:59 -05:00
Author
Owner
Copy Link

@CharlesKaiGao commented on GitHub (Jan 16, 2026):

Additionally, a smaller model of 2.4 GB is also reporting the same error.

<!-- gh-comment-id:3757976345 --> @CharlesKaiGao commented on GitHub (Jan 16, 2026): Additionally, a smaller model of 2.4 GB is also reporting the same error.
GiteaMirror commented 2026-04-12 21:49:59 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jan 30, 2026):

This seems resolved now, if the issue persists please re-open.

<!-- gh-comment-id:3823348513 --> @rick-github commented on GitHub (Jan 30, 2026): This seems resolved now, if the issue persists please re-open.
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#9006
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?