[GH-ISSUE #8873] pull model manifest: 500 #67807

Closed
opened 2026-05-04 11:44:46 -05:00 by GiteaMirror · 191 comments
Owner

Originally created by @auserwn on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/8873

C:\Windows\System32>ollama -v
ollama version is 0.5.7

C:\Windows\System32>ollama run deepseek-r1:1.5b
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

What error is this and how do I solve it?

Originally created by @auserwn on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/8873 C:\Windows\System32>ollama -v ollama version is 0.5.7 C:\Windows\System32>ollama run deepseek-r1:1.5b pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} What error is this and how do I solve it?
GiteaMirror added the networking label 2026-05-04 11:44:46 -05:00
Author
Owner

@Mrkk1 commented on GitHub (Feb 6, 2025):

While pulling normally just now, all pulling services on all servers were interrupted.

<!-- gh-comment-id:2639135444 --> @Mrkk1 commented on GitHub (Feb 6, 2025): While pulling normally just now, all pulling services on all servers were interrupted.
Author
Owner

@rjindael commented on GitHub (Feb 6, 2025):

Seems to be that the server is currently overloaded. I am receiving the same issue

<!-- gh-comment-id:2639135634 --> @rjindael commented on GitHub (Feb 6, 2025): Seems to be that the server is currently overloaded. I am receiving the same issue
Author
Owner

@ariyankabir7 commented on GitHub (Feb 6, 2025):

let just wait without filling the server with comments and let the developer do their work. 😑

<!-- gh-comment-id:2639136521 --> @ariyankabir7 commented on GitHub (Feb 6, 2025): let just wait without filling the server with comments and let the developer do their work. 😑
Author
Owner

@Zeying-Gong commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639137394 --> @Zeying-Gong commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@Marvin4444 commented on GitHub (Feb 6, 2025):

same problem

<!-- gh-comment-id:2639137652 --> @Marvin4444 commented on GitHub (Feb 6, 2025): same problem
Author
Owner

@Leibnizhu commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639138226 --> @Leibnizhu commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@Mrkk1 commented on GitHub (Feb 6, 2025):

I feel that developers of the Pulla Ollama model around the world will soon ask questions under this post

<!-- gh-comment-id:2639138984 --> @Mrkk1 commented on GitHub (Feb 6, 2025): I feel that developers of the Pulla Ollama model around the world will soon ask questions under this post
Author
Owner

@mickyss commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639139117 --> @mickyss commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@TT0824 commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639139208 --> @TT0824 commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@neverbiasu commented on GitHub (Feb 6, 2025):

root@02444a7210b2:/workspace# ollama run deepseek-r1:14b
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

same on Linux

<!-- gh-comment-id:2639139349 --> @neverbiasu commented on GitHub (Feb 6, 2025): root@02444a7210b2:/workspace# ollama run deepseek-r1:14b pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} same on Linux
Author
Owner

@somera commented on GitHub (Feb 6, 2025):

Same on linux.

$ ollama -v
ollama version is 0.5.7
$ bash ollama_update_models.sh
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
<!-- gh-comment-id:2639140588 --> @somera commented on GitHub (Feb 6, 2025): Same on linux. ``` $ ollama -v ollama version is 0.5.7 $ bash ollama_update_models.sh pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} ```
Author
Owner

@hxf4869 commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639141461 --> @hxf4869 commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@gulihua10010 commented on GitHub (Feb 6, 2025):

same on mac Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639142355 --> @gulihua10010 commented on GitHub (Feb 6, 2025): same on mac Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
Author
Owner

@thekumi commented on GitHub (Feb 6, 2025):

Probably the server that's overloaded or something. The error comes straight from the server, e.g. here: https://registry.ollama.ai/v2/library/llama3/manifests/latest

<!-- gh-comment-id:2639143268 --> @thekumi commented on GitHub (Feb 6, 2025): Probably the server that's overloaded or something. The error comes straight from the server, e.g. here: https://registry.ollama.ai/v2/library/llama3/manifests/latest
Author
Owner

@linlinlin530 commented on GitHub (Feb 6, 2025):

same on macOS just now, just 10 mins ago I was still pulling

<!-- gh-comment-id:2639143410 --> @linlinlin530 commented on GitHub (Feb 6, 2025): same on macOS just now, just 10 mins ago I was still pulling
Author
Owner

@catna commented on GitHub (Feb 6, 2025):

Same here
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639143924 --> @catna commented on GitHub (Feb 6, 2025): Same here `Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}`
Author
Owner

@wusanshou2017 commented on GitHub (Feb 6, 2025):

same on both windows and linux now

<!-- gh-comment-id:2639144032 --> @wusanshou2017 commented on GitHub (Feb 6, 2025): same on both windows and linux now
Author
Owner

@Cakeday commented on GitHub (Feb 6, 2025):

same on m1 Mac -- tried reinstalling -- same thing

<!-- gh-comment-id:2639145224 --> @Cakeday commented on GitHub (Feb 6, 2025): same on m1 Mac -- tried reinstalling -- same thing
Author
Owner

@mkblbj commented on GitHub (Feb 6, 2025):

same!

<!-- gh-comment-id:2639145474 --> @mkblbj commented on GitHub (Feb 6, 2025): same!
Author
Owner

@HilariousJi commented on GitHub (Feb 6, 2025):

same here on Windows

<!-- gh-comment-id:2639146991 --> @HilariousJi commented on GitHub (Feb 6, 2025): same here on Windows
Author
Owner

@wuyanzu commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639149308 --> @wuyanzu commented on GitHub (Feb 6, 2025): same here
Author
Owner

@ayylmaonade commented on GitHub (Feb 6, 2025):

It's happening across all OS. Linux & Windows both impacted here.

<!-- gh-comment-id:2639149807 --> @ayylmaonade commented on GitHub (Feb 6, 2025): It's happening across all OS. Linux & Windows both impacted here.
Author
Owner

@peakhell commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639150142 --> @peakhell commented on GitHub (Feb 6, 2025): same here
Author
Owner

@MR6464466 commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639150754 --> @MR6464466 commented on GitHub (Feb 6, 2025): same here
Author
Owner

@SummerSec commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639156099 --> @SummerSec commented on GitHub (Feb 6, 2025): same here
Author
Owner

@machaojin1917939763 commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639156775 --> @machaojin1917939763 commented on GitHub (Feb 6, 2025): same here
Author
Owner

@walawalala commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639157276 --> @walawalala commented on GitHub (Feb 6, 2025): same here
Author
Owner

@yangxiaoyx commented on GitHub (Feb 6, 2025):

Same here
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639158892 --> @yangxiaoyx commented on GitHub (Feb 6, 2025): Same here Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
Author
Owner

@ra1mj commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639159757 --> @ra1mj commented on GitHub (Feb 6, 2025): same here
Author
Owner

@BigPineappleDe commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639159805 --> @BigPineappleDe commented on GitHub (Feb 6, 2025): same here
Author
Owner

@bjttt commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639160080 --> @bjttt commented on GitHub (Feb 6, 2025): same here
Author
Owner

@bmw8080 commented on GitHub (Feb 6, 2025):

same here~

<!-- gh-comment-id:2639160241 --> @bmw8080 commented on GitHub (Feb 6, 2025): same here~
Author
Owner

@reTsubasa commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639161397 --> @reTsubasa commented on GitHub (Feb 6, 2025): same here
Author
Owner

@GeekDaiDao commented on GitHub (Feb 6, 2025):

same here~

<!-- gh-comment-id:2639161449 --> @GeekDaiDao commented on GitHub (Feb 6, 2025): same here~
Author
Owner

@LeonardZhang commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639161575 --> @LeonardZhang commented on GitHub (Feb 6, 2025): same here
Author
Owner

@Biao-K commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639162319 --> @Biao-K commented on GitHub (Feb 6, 2025): same here
Author
Owner

@thekumi commented on GitHub (Feb 6, 2025):

More "same here" messages are not going to help anyone, it's abundantly clear at this point that everyone is affected. Please don't spam developers.

<!-- gh-comment-id:2639162854 --> @thekumi commented on GitHub (Feb 6, 2025): More "same here" messages are not going to help anyone, it's abundantly clear at this point that *everyone* is affected. Please don't spam developers.
Author
Owner

@jiongjiong commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639163615 --> @jiongjiong commented on GitHub (Feb 6, 2025): same here
Author
Owner

@zt1115798334 commented on GitHub (Feb 6, 2025):

我也出现相同的问题了

<!-- gh-comment-id:2639164093 --> @zt1115798334 commented on GitHub (Feb 6, 2025): 我也出现相同的问题了
Author
Owner

@Konk32 commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639164825 --> @Konk32 commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@Soporior commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639165341 --> @Soporior commented on GitHub (Feb 6, 2025): same here
Author
Owner

@zhangningfang commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639165495 --> @zhangningfang commented on GitHub (Feb 6, 2025): same here
Author
Owner

@WZS666 commented on GitHub (Feb 6, 2025):

Same here 🎠

<!-- gh-comment-id:2639165514 --> @WZS666 commented on GitHub (Feb 6, 2025): Same here 🎠
Author
Owner

@abadfox233 commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639165959 --> @abadfox233 commented on GitHub (Feb 6, 2025): same here
Author
Owner

@DongShengWork commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639166432 --> @DongShengWork commented on GitHub (Feb 6, 2025): +1
Author
Owner

@xiaomaofeng commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639166816 --> @xiaomaofeng commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@auserwn commented on GitHub (Feb 6, 2025):

你之前部署过没,我是第一次使用ollama 想部署个deepseek看看

---- Replied Message ----
| From | @.> |
| Date | 2/6/2025 16:39 |
| To | @.
> |
| Cc | @.>,
@.
> |
| Subject | Re: [ollama/ollama] pull model manifest: 500 (Issue #8873) |

我也出现相同的问题了


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

<!-- gh-comment-id:2639167707 --> @auserwn commented on GitHub (Feb 6, 2025): 你之前部署过没,我是第一次使用ollama 想部署个deepseek看看 ---- Replied Message ---- | From | ***@***.***> | | Date | 2/6/2025 16:39 | | To | ***@***.***> | | Cc | ***@***.***>, ***@***.***> | | Subject | Re: [ollama/ollama] pull model manifest: 500 (Issue #8873) | 我也出现相同的问题了 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@lfhy commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639167940 --> @lfhy commented on GitHub (Feb 6, 2025): +1
Author
Owner

@ziuyung commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639170162 --> @ziuyung commented on GitHub (Feb 6, 2025): +1
Author
Owner

@QFJiao commented on GitHub (Feb 6, 2025):

pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} +1 什么时候能好哇,本来下载就慢

<!-- gh-comment-id:2639170325 --> @QFJiao commented on GitHub (Feb 6, 2025): pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} +1 什么时候能好哇,本来下载就慢
Author
Owner

@xiaohei07 commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639170497 --> @xiaohei07 commented on GitHub (Feb 6, 2025): +1
Author
Owner

@ImproveRei0 commented on GitHub (Feb 6, 2025):

same here ,新鲜bug

<!-- gh-comment-id:2639171406 --> @ImproveRei0 commented on GitHub (Feb 6, 2025): same here ,新鲜bug
Author
Owner

@chenggx commented on GitHub (Feb 6, 2025):

Same here too

<!-- gh-comment-id:2639171604 --> @chenggx commented on GitHub (Feb 6, 2025): Same here too
Author
Owner

@suhli commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639172467 --> @suhli commented on GitHub (Feb 6, 2025): same here
Author
Owner

@prideli0310 commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639172640 --> @prideli0310 commented on GitHub (Feb 6, 2025): +1
Author
Owner

@PengGYing commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639173208 --> @PengGYing commented on GitHub (Feb 6, 2025): +1
Author
Owner

@reele commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639173272 --> @reele commented on GitHub (Feb 6, 2025): +1
Author
Owner

@irisOvo commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639173279 --> @irisOvo commented on GitHub (Feb 6, 2025): same here
Author
Owner

@OneYiLei commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639174547 --> @OneYiLei commented on GitHub (Feb 6, 2025): +1
Author
Owner

@kimiisme commented on GitHub (Feb 6, 2025):

+10086

<!-- gh-comment-id:2639176252 --> @kimiisme commented on GitHub (Feb 6, 2025): +10086
Author
Owner

@SCUlevi commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639176282 --> @SCUlevi commented on GitHub (Feb 6, 2025): same here
Author
Owner

@JX223 commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639176294 --> @JX223 commented on GitHub (Feb 6, 2025): +1
Author
Owner

@Samge0 commented on GitHub (Feb 6, 2025):

+1

ollama -v
ollama version is 0.5.7

ollama run deepseek-r1:1.5b
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
<!-- gh-comment-id:2639176629 --> @Samge0 commented on GitHub (Feb 6, 2025): +1 ```shell ollama -v ollama version is 0.5.7 ollama run deepseek-r1:1.5b pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} ```
Author
Owner

@i7eo commented on GitHub (Feb 6, 2025):

Please look at this @Leibnizhu

<!-- gh-comment-id:2639177040 --> @i7eo commented on GitHub (Feb 6, 2025): Please look at this @Leibnizhu
Author
Owner

@sadness-sa commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639177053 --> @sadness-sa commented on GitHub (Feb 6, 2025): +1
Author
Owner

@2h-Lin commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639177361 --> @2h-Lin commented on GitHub (Feb 6, 2025): same here
Author
Owner

@qwertyu45rtdj commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639177678 --> @qwertyu45rtdj commented on GitHub (Feb 6, 2025): same here
Author
Owner

@JARVGOD commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639177708 --> @JARVGOD commented on GitHub (Feb 6, 2025): +1
Author
Owner

@abulili commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639178176 --> @abulili commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@CorvusCorax1024 commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639180267 --> @CorvusCorax1024 commented on GitHub (Feb 6, 2025): +1
Author
Owner

@afang518 commented on GitHub (Feb 6, 2025):

😯

<!-- gh-comment-id:2639180489 --> @afang518 commented on GitHub (Feb 6, 2025): 😯
Author
Owner

@guoer577 commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639180532 --> @guoer577 commented on GitHub (Feb 6, 2025): +1
Author
Owner

@Yuding-Zhang commented on GitHub (Feb 6, 2025):

same on windows

<!-- gh-comment-id:2639180929 --> @Yuding-Zhang commented on GitHub (Feb 6, 2025): same on windows
Author
Owner

@xiaofengcanyue-d commented on GitHub (Feb 6, 2025):

+1,sooo Fresh bugs🤣🤣🤣

<!-- gh-comment-id:2639180981 --> @xiaofengcanyue-d commented on GitHub (Feb 6, 2025): +1,sooo Fresh bugs🤣🤣🤣
Author
Owner

@QGtiger commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639181379 --> @QGtiger commented on GitHub (Feb 6, 2025): +1
Author
Owner

@liberty4me commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639181701 --> @liberty4me commented on GitHub (Feb 6, 2025): +1
Author
Owner

@wjl1272165766 commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639182086 --> @wjl1272165766 commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@codingloverzz commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639182322 --> @codingloverzz commented on GitHub (Feb 6, 2025): same here
Author
Owner

@deno-source commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639182449 --> @deno-source commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@Mrkk1 commented on GitHub (Feb 6, 2025):

After the Spring Festival, everyone starts to use deepseek, right?

<!-- gh-comment-id:2639182650 --> @Mrkk1 commented on GitHub (Feb 6, 2025): After the Spring Festival, everyone starts to use deepseek, right?
Author
Owner

@dahuoshi commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639182888 --> @dahuoshi commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@anson920520 commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639183104 --> @anson920520 commented on GitHub (Feb 6, 2025): same here
Author
Owner

@xuzheng0017 commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639183585 --> @xuzheng0017 commented on GitHub (Feb 6, 2025): same here
Author
Owner

@heroinlin commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639183655 --> @heroinlin commented on GitHub (Feb 6, 2025): same here
Author
Owner

@WBarbar commented on GitHub (Feb 6, 2025):

一直这样

pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639184351 --> @WBarbar commented on GitHub (Feb 6, 2025): 一直这样 pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
Author
Owner

@mipmip commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639184987 --> @mipmip commented on GitHub (Feb 6, 2025): same here
Author
Owner

@WBarbar commented on GitHub (Feb 6, 2025):

C:\Users\84304>ollama -v
ollama version is 0.5.7

C:\Users\84304>ollama run deepseek-r1:1.5b
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
求大大解决

<!-- gh-comment-id:2639185755 --> @WBarbar commented on GitHub (Feb 6, 2025): C:\Users\84304>ollama -v ollama version is 0.5.7 C:\Users\84304>ollama run deepseek-r1:1.5b pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} 求大大解决
Author
Owner

@xinshou-xin commented on GitHub (Feb 6, 2025):

same here. what time can slove?

<!-- gh-comment-id:2639186802 --> @xinshou-xin commented on GitHub (Feb 6, 2025): same here. what time can slove?
Author
Owner

@BigBossWHD commented on GitHub (Feb 6, 2025):

same here on MacOS 10min ago

<!-- gh-comment-id:2639187894 --> @BigBossWHD commented on GitHub (Feb 6, 2025): same here on MacOS 10min ago
Author
Owner

@Zoexyz77 commented on GitHub (Feb 6, 2025):

same

<!-- gh-comment-id:2639188161 --> @Zoexyz77 commented on GitHub (Feb 6, 2025): same
Author
Owner

@MoZiBai commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639188374 --> @MoZiBai commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@wwpu commented on GitHub (Feb 6, 2025):

what happened

<!-- gh-comment-id:2639188521 --> @wwpu commented on GitHub (Feb 6, 2025): what happened
Author
Owner

@binz123 commented on GitHub (Feb 6, 2025):

sam here on linux ubuntu 10min ago

<!-- gh-comment-id:2639188684 --> @binz123 commented on GitHub (Feb 6, 2025): sam here on linux ubuntu 10min ago
Author
Owner

@wangybbj commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639189357 --> @wangybbj commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@Phoenix-PKU commented on GitHub (Feb 6, 2025):

same on MacOS

<!-- gh-comment-id:2639189619 --> @Phoenix-PKU commented on GitHub (Feb 6, 2025): same on MacOS
Author
Owner

@FT-Fetters commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639189625 --> @FT-Fetters commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@ColorCJY commented on GitHub (Feb 6, 2025):

Is the server down because too many people are pulling?

<!-- gh-comment-id:2639190106 --> @ColorCJY commented on GitHub (Feb 6, 2025): Is the server down because too many people are pulling?
Author
Owner

@1SolPi1 commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639191782 --> @1SolPi1 commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@Asabis commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639191859 --> @Asabis commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@maskedman227 commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639191994 --> @maskedman227 commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@acshmily commented on GitHub (Feb 6, 2025):

if someone else want to use deepseek ,you can try use modelscope
you can visit modelscope learn how to use

and deepseek GGUF model here:https://www.modelscope.cn/models/unsloth/DeepSeek-R1-Distill-Qwen-32B-GGUF

<!-- gh-comment-id:2639192191 --> @acshmily commented on GitHub (Feb 6, 2025): if someone else want to use deepseek ,you can try use modelscope you can visit [modelscope](https://www.modelscope.cn/docs/models/advanced-usage/ollama-integration) learn how to use and deepseek GGUF model here:https://www.modelscope.cn/models/unsloth/DeepSeek-R1-Distill-Qwen-32B-GGUF
Author
Owner

@Harrytty commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639194136 --> @Harrytty commented on GitHub (Feb 6, 2025): same here
Author
Owner

@guoer577 commented on GitHub (Feb 6, 2025):

Neither my mac nor my PC can be pulled. It must be the problem with the ollama server! Seeking solutions

<!-- gh-comment-id:2639194544 --> @guoer577 commented on GitHub (Feb 6, 2025): Neither my mac nor my PC can be pulled. It must be the problem with the ollama server! Seeking solutions
Author
Owner

@cristinarccc commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639195706 --> @cristinarccc commented on GitHub (Feb 6, 2025): same here
Author
Owner

@Zevi-zzy commented on GitHub (Feb 6, 2025):

same problem

<!-- gh-comment-id:2639196194 --> @Zevi-zzy commented on GitHub (Feb 6, 2025): same problem
Author
Owner

@thekumi commented on GitHub (Feb 6, 2025):

@guoer577 It is. At this point, the only solution is waiting for the server to be fixed.

<!-- gh-comment-id:2639196976 --> @thekumi commented on GitHub (Feb 6, 2025): @guoer577 It is. At this point, the only solution is waiting for the server to be fixed.
Author
Owner

@Pendlers commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639197773 --> @Pendlers commented on GitHub (Feb 6, 2025): same here
Author
Owner

@mYoCaRdiA commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639197956 --> @mYoCaRdiA commented on GitHub (Feb 6, 2025): +1
Author
Owner

@edwarddu commented on GitHub (Feb 6, 2025):

same here ...when to recover ?

<!-- gh-comment-id:2639199065 --> @edwarddu commented on GitHub (Feb 6, 2025): same here ...when to recover ?
Author
Owner

@LLL672-ae commented on GitHub (Feb 6, 2025):

pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

why?

<!-- gh-comment-id:2639199122 --> @LLL672-ae commented on GitHub (Feb 6, 2025): pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]} why?
Author
Owner

@ElonMikeLi commented on GitHub (Feb 6, 2025):

So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.

<!-- gh-comment-id:2639199328 --> @ElonMikeLi commented on GitHub (Feb 6, 2025): So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.
Author
Owner

@mg-kell0806 commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639199333 --> @mg-kell0806 commented on GitHub (Feb 6, 2025): same here
Author
Owner

@outman000 commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639199600 --> @outman000 commented on GitHub (Feb 6, 2025): same here
Author
Owner

@mYoCaRdiA commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639199608 --> @mYoCaRdiA commented on GitHub (Feb 6, 2025): +1
Author
Owner

@jackywood commented on GitHub (Feb 6, 2025):

Error: pull model manifest: 500:我刚刚也遇到了

<!-- gh-comment-id:2639199746 --> @jackywood commented on GitHub (Feb 6, 2025): Error: pull model manifest: 500:我刚刚也遇到了
Author
Owner

@AnGoYang commented on GitHub (Feb 6, 2025):

same here on MacOS

<!-- gh-comment-id:2639200183 --> @AnGoYang commented on GitHub (Feb 6, 2025): same here on MacOS
Author
Owner

@DongShengWork commented on GitHub (Feb 6, 2025):

Image
<!-- gh-comment-id:2639200389 --> @DongShengWork commented on GitHub (Feb 6, 2025): <img width="807" alt="Image" src="https://github.com/user-attachments/assets/57de8088-09cf-42e2-8fd2-6fc9872bd94e" />
Author
Owner

@mYoCaRdiA commented on GitHub (Feb 6, 2025):

+1

<!-- gh-comment-id:2639200680 --> @mYoCaRdiA commented on GitHub (Feb 6, 2025): +1
Author
Owner

@35763670SpadeKing commented on GitHub (Feb 6, 2025):

一样 不知道怎么解决

<!-- gh-comment-id:2639200682 --> @35763670SpadeKing commented on GitHub (Feb 6, 2025): 一样 不知道怎么解决
Author
Owner

@mYoCaRdiA commented on GitHub (Feb 6, 2025):

what happened goooooooooooood

<!-- gh-comment-id:2639201109 --> @mYoCaRdiA commented on GitHub (Feb 6, 2025): what happened goooooooooooood
Author
Owner

@xavierchan commented on GitHub (Feb 6, 2025):

Just calm down, this is server‘s bug, just wait to be fixed.

<!-- gh-comment-id:2639201594 --> @xavierchan commented on GitHub (Feb 6, 2025): Just calm down, this is server‘s bug, just wait to be fixed.
Author
Owner

@codingforward commented on GitHub (Feb 6, 2025):

same here:
C:\Users\Administrator>ollama run deepseek-r1:7b
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639202809 --> @codingforward commented on GitHub (Feb 6, 2025): same here: C:\Users\Administrator>ollama run deepseek-r1:7b pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
Author
Owner

@dahuoshi commented on GitHub (Feb 6, 2025):

Image terrible

<!-- gh-comment-id:2639202841 --> @dahuoshi commented on GitHub (Feb 6, 2025): ![Image](https://github.com/user-attachments/assets/c8832fa0-562e-4bdf-8f95-6b9b141e1b64) terrible
Author
Owner

@aitransformer commented on GitHub (Feb 6, 2025):

waiting

<!-- gh-comment-id:2639203030 --> @aitransformer commented on GitHub (Feb 6, 2025): waiting
Author
Owner

@mYoCaRdiA commented on GitHub (Feb 6, 2025):

The servers on their website are down

<!-- gh-comment-id:2639205551 --> @mYoCaRdiA commented on GitHub (Feb 6, 2025): The servers on their website are down
Author
Owner

@mg-kell0806 commented on GitHub (Feb 6, 2025):

So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.很多人在同一时间犯了同样的错误。也许这不全是我们的问题。可能是 DeepSeek 服务器崩溃了,我们无法拉取模式。

Not only does the deepseek model fail to pull, other models also pull exceptions

<!-- gh-comment-id:2639205628 --> @mg-kell0806 commented on GitHub (Feb 6, 2025): > So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.很多人在同一时间犯了同样的错误。也许这不全是我们的问题。可能是 DeepSeek 服务器崩溃了,我们无法拉取模式。 Not only does the deepseek model fail to pull, other models also pull exceptions
Author
Owner

@TechEnthusiast41 commented on GitHub (Feb 6, 2025):

the same problem:
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639207072 --> @TechEnthusiast41 commented on GitHub (Feb 6, 2025): the same problem: pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
Author
Owner

@mYoCaRdiA commented on GitHub (Feb 6, 2025):

the ollama sever crashed ,not deepseek

<!-- gh-comment-id:2639208050 --> @mYoCaRdiA commented on GitHub (Feb 6, 2025): the ollama sever crashed ,not deepseek
Author
Owner

@AllenPu2020 commented on GitHub (Feb 6, 2025):

same problem
-> % ollama run deepseek-r1:14b
pulling manifest
Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639209546 --> @AllenPu2020 commented on GitHub (Feb 6, 2025): same problem -> % ollama run deepseek-r1:14b pulling manifest Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
Author
Owner

@TanShun commented on GitHub (Feb 6, 2025):

Same here, all models can't be pulled, not just deepseek.

<!-- gh-comment-id:2639210324 --> @TanShun commented on GitHub (Feb 6, 2025): Same here, all models can't be pulled, not just deepseek.
Author
Owner

@xiaosheng-conk commented on GitHub (Feb 6, 2025):

同样的问题,下载deepseek-r1:14b的时候

<!-- gh-comment-id:2639211907 --> @xiaosheng-conk commented on GitHub (Feb 6, 2025): 同样的问题,下载deepseek-r1:14b的时候
Author
Owner

@MoZiBai commented on GitHub (Feb 6, 2025):

the ollama sever crashed ,not deepseek

<!-- gh-comment-id:2639213480 --> @MoZiBai commented on GitHub (Feb 6, 2025): the ollama sever crashed ,not deepseek
Author
Owner

@wesley1211 commented on GitHub (Feb 6, 2025):

same here. might be too much pull for deepseek model

<!-- gh-comment-id:2639213698 --> @wesley1211 commented on GitHub (Feb 6, 2025): same here. might be too much pull for deepseek model
Author
Owner

@kuiyuboy commented on GitHub (Feb 6, 2025):

Why, I'm finally almost done, and suddenly this whole !!

<!-- gh-comment-id:2639214916 --> @kuiyuboy commented on GitHub (Feb 6, 2025): Why, I'm finally almost done, and suddenly this whole !!
Author
Owner

@ComradePenguin-1917 commented on GitHub (Feb 6, 2025):

same. You can try download from hugging face or 魔搭 and install manually.

<!-- gh-comment-id:2639216956 --> @ComradePenguin-1917 commented on GitHub (Feb 6, 2025): same. You can try download from hugging face or 魔搭 and install manually.
Author
Owner

@ElonMikeLi commented on GitHub (Feb 6, 2025):

So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.很多人在同一时间犯了同样的错误。也许这不全是我们的问题。可能是 DeepSeek 服务器崩溃了,我们无法拉取模式。

Not only does the deepseek model fail to pull, other models also pull exceptions

Oh,That's too bad,maybe just waiting

<!-- gh-comment-id:2639217934 --> @ElonMikeLi commented on GitHub (Feb 6, 2025): > > So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.很多人在同一时间犯了同样的错误。也许这不全是我们的问题。可能是 DeepSeek 服务器崩溃了,我们无法拉取模式。 > > Not only does the deepseek model fail to pull, other models also pull exceptions > Oh,That's too bad,maybe just waiting
Author
Owner

@TechEnthusiast41 commented on GitHub (Feb 6, 2025):

So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.很多人在同一时间犯了同样的错误。也许这不全是我们的问题。可能是 DeepSeek 服务器崩溃了,我们无法拉取模式。

Not only does the deepseek model fail to pull, other models also pull exceptions

Oh,That's too bad,maybe just waiting

you can only waiting/(ㄒoㄒ)/~~

<!-- gh-comment-id:2639219471 --> @TechEnthusiast41 commented on GitHub (Feb 6, 2025): > > > So many people have the same mistake at the same time. Maybe it's not our problem. Could it be that the DeepSeek server crashed and we can't pull mode.很多人在同一时间犯了同样的错误。也许这不全是我们的问题。可能是 DeepSeek 服务器崩溃了,我们无法拉取模式。 > > > > > > Not only does the deepseek model fail to pull, other models also pull exceptions > > Oh,That's too bad,maybe just waiting you can only waiting/(ㄒoㄒ)/~~
Author
Owner

@yang-fei commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639219701 --> @yang-fei commented on GitHub (Feb 6, 2025): same here
Author
Owner

@Rilfoyle commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639219992 --> @Rilfoyle commented on GitHub (Feb 6, 2025): same here
Author
Owner

@ruochen-yyb commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639220527 --> @ruochen-yyb commented on GitHub (Feb 6, 2025): same here
Author
Owner

@wangshan-aqi commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639220854 --> @wangshan-aqi commented on GitHub (Feb 6, 2025): same here
Author
Owner

@ycbing commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639221120 --> @ycbing commented on GitHub (Feb 6, 2025): same here
Author
Owner

@EvolvedGhost commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639221255 --> @EvolvedGhost commented on GitHub (Feb 6, 2025): same here
Author
Owner

@jackeyhao commented on GitHub (Feb 6, 2025):

这里也是一样的

<!-- gh-comment-id:2639221384 --> @jackeyhao commented on GitHub (Feb 6, 2025): 这里也是一样的
Author
Owner

@Eliot-Shen commented on GitHub (Feb 6, 2025):

The same. Let me guess. We are downloading some version of deepseek model right? hhh

<!-- gh-comment-id:2639221516 --> @Eliot-Shen commented on GitHub (Feb 6, 2025): The same. Let me guess. We are downloading some version of deepseek model right? hhh
Author
Owner

@SacribethGrass commented on GitHub (Feb 6, 2025):

same here. 我还以为是我的问题

<!-- gh-comment-id:2639221927 --> @SacribethGrass commented on GitHub (Feb 6, 2025): same here. 我还以为是我的问题
Author
Owner

@vatofichor commented on GitHub (Feb 6, 2025):

very interesting to see the this outage, its with any model pull

<!-- gh-comment-id:2639224350 --> @vatofichor commented on GitHub (Feb 6, 2025): very interesting to see the this outage, its with any model pull
Author
Owner

@qianxingkeji commented on GitHub (Feb 6, 2025):

Same here

<!-- gh-comment-id:2639224735 --> @qianxingkeji commented on GitHub (Feb 6, 2025): Same here
Author
Owner

@LonerDo commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639224787 --> @LonerDo commented on GitHub (Feb 6, 2025): same here
Author
Owner

@JudeNiroshan commented on GitHub (Feb 6, 2025):

Please stop commenting "same here".
It makes too much noise and doesn't help others at all. We all know it's broken. Give sometime they'll provide a solution or a workaround.

<!-- gh-comment-id:2639224874 --> @JudeNiroshan commented on GitHub (Feb 6, 2025): Please stop commenting "same here". It makes too much noise and doesn't help others at all. We all know it's broken. Give sometime they'll provide a solution or a workaround.
Author
Owner

@vatofichor commented on GitHub (Feb 6, 2025):

the llama2-uncensored model got nerfed

<!-- gh-comment-id:2639225104 --> @vatofichor commented on GitHub (Feb 6, 2025): the llama2-uncensored model got nerfed
Author
Owner

@NingNingRobot commented on GitHub (Feb 6, 2025):

hugging face servers were interrupted

<!-- gh-comment-id:2639227377 --> @NingNingRobot commented on GitHub (Feb 6, 2025): hugging face servers were interrupted
Author
Owner

@ColdWindScholar commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639228798 --> @ColdWindScholar commented on GitHub (Feb 6, 2025): same here
Author
Owner

@Se1ker commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639230159 --> @Se1ker commented on GitHub (Feb 6, 2025): same here
Author
Owner

@z-qh commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639230692 --> @z-qh commented on GitHub (Feb 6, 2025): same here
Author
Owner

@Tan-Yi commented on GitHub (Feb 6, 2025):

Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}

<!-- gh-comment-id:2639232130 --> @Tan-Yi commented on GitHub (Feb 6, 2025): Error: pull model manifest: 500: {"errors":[{"code":"INTERNAL_ERROR","message":"internal error"}]}
Author
Owner

@Zha-Miku commented on GitHub (Feb 6, 2025):

some here

<!-- gh-comment-id:2639232274 --> @Zha-Miku commented on GitHub (Feb 6, 2025): some here
Author
Owner

@Jessmin commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639232700 --> @Jessmin commented on GitHub (Feb 6, 2025): same here
Author
Owner

@hxlive commented on GitHub (Feb 6, 2025):

same here

<!-- gh-comment-id:2639233114 --> @hxlive commented on GitHub (Feb 6, 2025): same here
Author
Owner

@SacribethGrass commented on GitHub (Feb 6, 2025):

现在好像可以了,修复好了。
It seems Okay now.

<!-- gh-comment-id:2639233764 --> @SacribethGrass commented on GitHub (Feb 6, 2025): 现在好像可以了,修复好了。 It seems Okay now.
Author
Owner

@OneYiLei commented on GitHub (Feb 6, 2025):

It should work now.

<!-- gh-comment-id:2639234287 --> @OneYiLei commented on GitHub (Feb 6, 2025): It should work now.
Author
Owner

@Jessmin commented on GitHub (Feb 6, 2025):

It seems Okay

<!-- gh-comment-id:2639235081 --> @Jessmin commented on GitHub (Feb 6, 2025): It seems Okay
Author
Owner

@SacribethGrass commented on GitHub (Feb 6, 2025):

Image
<!-- gh-comment-id:2639235524 --> @SacribethGrass commented on GitHub (Feb 6, 2025): <img width="721" alt="Image" src="https://github.com/user-attachments/assets/135a111d-d5e3-48d5-8513-92497532dcdf" />
Author
Owner

@ClickListener commented on GitHub (Feb 6, 2025):

可以了

Image

<!-- gh-comment-id:2639236351 --> @ClickListener commented on GitHub (Feb 6, 2025): 可以了 ![Image](https://github.com/user-attachments/assets/78c0ce73-ef37-4a1a-a3b8-ceab9a694aae)
Author
Owner

@wangshan-aqi commented on GitHub (Feb 6, 2025):

Image现在可以了

<!-- gh-comment-id:2639236817 --> @wangshan-aqi commented on GitHub (Feb 6, 2025): <img width="361" alt="Image" src="https://github.com/user-attachments/assets/a0e94174-8ed7-4ec1-94f9-b72938b9d0d6" />现在可以了
Author
Owner

@ColdWindScholar commented on GitHub (Feb 6, 2025):

thanks sir!!! its okay now!

<!-- gh-comment-id:2639237184 --> @ColdWindScholar commented on GitHub (Feb 6, 2025): thanks sir!!! its okay now!
Author
Owner

@qianxingkeji commented on GitHub (Feb 6, 2025):

It is Okay

<!-- gh-comment-id:2639237311 --> @qianxingkeji commented on GitHub (Feb 6, 2025): It is Okay
Author
Owner

@vatofichor commented on GitHub (Feb 6, 2025):

yay everyone pull party, im sure they will love this right after a crash

Image

<!-- gh-comment-id:2639237540 --> @vatofichor commented on GitHub (Feb 6, 2025): yay everyone pull party, im sure they will love this right after a crash ![Image](https://github.com/user-attachments/assets/0a17dd05-38b8-4370-8fd5-9126bd602e73)
Author
Owner

@Zha-Miku commented on GitHub (Feb 6, 2025):

Are you all pulling the deepepseek-r1 model?😀

<!-- gh-comment-id:2639237661 --> @Zha-Miku commented on GitHub (Feb 6, 2025): Are you all pulling the deepepseek-r1 model?😀
Author
Owner

@MoZiBai commented on GitHub (Feb 6, 2025):

It is Okay now

<!-- gh-comment-id:2639238115 --> @MoZiBai commented on GitHub (Feb 6, 2025): It is Okay now
Author
Owner

@qianxingkeji commented on GitHub (Feb 6, 2025):

Are you all pulling the deepepseek-r1 model?😀

yes

<!-- gh-comment-id:2639238646 --> @qianxingkeji commented on GitHub (Feb 6, 2025): > Are you all pulling the deepepseek-r1 model?😀 yes
Author
Owner

@WeikangLin93 commented on GitHub (Feb 6, 2025):

It is Okay now

<!-- gh-comment-id:2639238831 --> @WeikangLin93 commented on GitHub (Feb 6, 2025): It is Okay now
Author
Owner

@OneYiLei commented on GitHub (Feb 6, 2025):

Are you all pulling the deepepseek-r1 model?😀

你们都在拉 deepepseek-r1 模型吗? 😀

deepepseek-r1 good!!!!!

<!-- gh-comment-id:2639242209 --> @OneYiLei commented on GitHub (Feb 6, 2025): > Are you all pulling the deepepseek-r1 model?😀 > 你们都在拉 deepepseek-r1 模型吗? 😀 deepepseek-r1 good!!!!!
Author
Owner

@Wetcue commented on GitHub (Feb 6, 2025):

just because of deepseek!

<!-- gh-comment-id:2639243676 --> @Wetcue commented on GitHub (Feb 6, 2025): just because of deepseek!
Author
Owner

@Eliot-Shen commented on GitHub (Feb 6, 2025):

Engineer/students worldwide do the same thing at the same time. Nice feeling.

<!-- gh-comment-id:2639244429 --> @Eliot-Shen commented on GitHub (Feb 6, 2025): Engineer/students worldwide do the same thing at the same time. Nice feeling.
Author
Owner

@Fackyhub commented on GitHub (Feb 6, 2025):

I already download 70%,spent all time,Damn!

<!-- gh-comment-id:2639244454 --> @Fackyhub commented on GitHub (Feb 6, 2025): I already download 70%,spent all time,Damn!
Author
Owner

@wjl1272165766 commented on GitHub (Feb 6, 2025):

It seems Okay

<!-- gh-comment-id:2639245441 --> @wjl1272165766 commented on GitHub (Feb 6, 2025): It seems Okay
Author
Owner

@Zha-Miku commented on GitHub (Feb 6, 2025):

Image

I will get it!!!

<!-- gh-comment-id:2639247767 --> @Zha-Miku commented on GitHub (Feb 6, 2025): ![Image](https://github.com/user-attachments/assets/567333d8-8855-4057-a816-defc3d228b73) I will get it!!!
Author
Owner

@xiaosheng-conk commented on GitHub (Feb 6, 2025):

Image真好,现在可以下载了

<!-- gh-comment-id:2639248836 --> @xiaosheng-conk commented on GitHub (Feb 6, 2025): ![Image](https://github.com/user-attachments/assets/f70d1600-98f4-407a-bc52-83d15ddd22db)真好,现在可以下载了
Author
Owner

@qwertyu45rtdj commented on GitHub (Feb 6, 2025):

How to re-download it

<!-- gh-comment-id:2639248933 --> @qwertyu45rtdj commented on GitHub (Feb 6, 2025): How to re-download it
Author
Owner

@wangybbj commented on GitHub (Feb 6, 2025):

It's ok now

<!-- gh-comment-id:2639250127 --> @wangybbj commented on GitHub (Feb 6, 2025): It's ok now
Author
Owner

@ElonMikeLi commented on GitHub (Feb 6, 2025):

imageits work

<!-- gh-comment-id:2639250424 --> @ElonMikeLi commented on GitHub (Feb 6, 2025): ![image](https://github.com/user-attachments/assets/cdceaa96-9967-4fd7-802f-6ca7a9ca9ffd)its work
Author
Owner

@jojochen81 commented on GitHub (Feb 6, 2025):

现在好了

<!-- gh-comment-id:2639252527 --> @jojochen81 commented on GitHub (Feb 6, 2025): 现在好了
Author
Owner

@AllenPu2020 commented on GitHub (Feb 6, 2025):

Image WORK! Continue with the previous download.
<!-- gh-comment-id:2639253102 --> @AllenPu2020 commented on GitHub (Feb 6, 2025): <img width="810" alt="Image" src="https://github.com/user-attachments/assets/1db37e62-5ea9-4043-81ba-4d98c91da99c" /> WORK! Continue with the previous download.
Author
Owner

@aka-keqing commented on GitHub (Feb 6, 2025):

it's ok now

<!-- gh-comment-id:2639261720 --> @aka-keqing commented on GitHub (Feb 6, 2025): it's ok now
Author
Owner

@dahuoshi commented on GitHub (Feb 6, 2025):

Service was restored

<!-- gh-comment-id:2639267955 --> @dahuoshi commented on GitHub (Feb 6, 2025): Service was restored
Author
Owner

@yingxiaaa7 commented on GitHub (Feb 6, 2025):

I've already downloaded 90%; now I have to redownload, and it is so slow. But still feel grateful to the developers.

<!-- gh-comment-id:2639269246 --> @yingxiaaa7 commented on GitHub (Feb 6, 2025): I've already downloaded 90%; now I have to redownload, and it is so slow. But still feel grateful to the developers.
Author
Owner

@wsjkx commented on GitHub (Feb 6, 2025):

It's ok now. I'm starting download now.

<!-- gh-comment-id:2639275126 --> @wsjkx commented on GitHub (Feb 6, 2025): It's ok now. I'm starting download now.
Author
Owner

@AllenPu2020 commented on GitHub (Feb 6, 2025):

If I want to save docker images, we use docker save -o my_image.tar my_image:tag
And then, we copy my_image.tar to other computer
Use docker load -i my_image.tar to load this docker image。

So,ollama save models? ollama load models

<!-- gh-comment-id:2639287842 --> @AllenPu2020 commented on GitHub (Feb 6, 2025): If I want to save docker images, we use ``docker save -o my_image.tar my_image:tag`` And then, we copy `my_image.tar` to other computer Use ``docker load -i my_image.tar`` to load this docker image。 So,``ollama save models``? ``ollama load models``
Author
Owner

@jmorganca commented on GitHub (Feb 6, 2025):

Hi folks, so sorry about this, ollama.com was impacted by last night's Cloudflare R2 outage. It should be back to normal now

<!-- gh-comment-id:2641075790 --> @jmorganca commented on GitHub (Feb 6, 2025): Hi folks, so sorry about this, ollama.com was impacted by last night's [Cloudflare R2](https://www.cloudflarestatus.com/incidents/pgz7g5xlpxzr) outage. It should be back to normal now
Author
Owner

@PixelSymbols commented on GitHub (Nov 18, 2025):

same issue: https://registry.ollama.ai/v2/library/llama3/manifests/latest
Internal server error Error code 500
Visit cloudflare.com for more information.
2025-11-18 14:16:09 UTC

<!-- gh-comment-id:3547829395 --> @PixelSymbols commented on GitHub (Nov 18, 2025): same issue: https://registry.ollama.ai/v2/library/llama3/manifests/latest Internal server error Error code 500 Visit [cloudflare.com](https://www.cloudflare.com/5xx-error-landing?utm_source=errorcode_500&utm_campaign=registry.ollama.ai) for more information. 2025-11-18 14:16:09 UTC
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#67807