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

[GH-ISSUE #5298] Internal error at url manifests/sha256: #29083

New Issue
Open
opened 2026-04-22 07:43:41 -05:00 by GiteaMirror · 16 comments
GiteaMirror commented 2026-04-22 07:43:41 -05:00
Owner
Copy Link

Originally created by @alexeu1994 on GitHub (Jun 26, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5298

What is the issue?

Sonatype nexus proxy was configured and worked, but 2 weeks ago it started giving an error when requesting a manifest.

2024-06-24 22:19:00,375+0300 DEBUG [nexus-httpclient-eviction-thread]  *SYSTEM org.apache.http.impl.conn.CPool - Connection [id:3377][route:{s}->[https://registry.ollama.ai:443](https://registry.ollama.ai/)][state:null] expired @ Mon Jun 24 22:18:56 MSK 2024
2024-06-24 22:20:23,263+0300 DEBUG [qtp1079333755-4212]  anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/latest > GET /v2/library/all-minilm/manifests/latest HTTP/1.1
2024-06-24 22:20:25,591+0300 DEBUG [qtp1079333755-4212]  anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/latest < HTTP/1.1 200 OK @ 2.329 s
2024-06-24 22:20:25,594+0300 DEBUG [qtp1079333755-4212]  anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb > GET /v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb HTTP/1.1
2024-06-24 22:20:25,953+0300 DEBUG [qtp1079333755-4212]  anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb < HTTP/1.1 500 Internal Server Error @ 358.1 ms
2024-06-24 22:20:25,953+0300 INFO  [qtp1079333755-4212]  anonymous org.sonatype.nexus.repository.httpclient.internal.HttpClientFacetImpl - Repository status for ollamaio-docker-proxy changed from AVAILABLE to UNAVAILABLE - reason Internal Server Error for https://registry.ollama.ai/

Nexus tries to get sha file but gets an error
https://registry.ollama.ai/v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb

registry.ollama.ai can`t handle colon at url manifests

any link with colon response error
https://registry.ollama.ai/v2/library/all-minilm/manifests/anyurl:a
500 Internal Server Error
{"errors":[{"code":"INTERNAL_ERROR","message":"internal error","detail":null}]}

any link without colon work correctly
404 Not Found
https://registry.ollama.ai/v2/library/all-minilm/manifests/anyurl
{"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown"}]}

Can you fix "500 Internal Server Error"?

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @alexeu1994 on GitHub (Jun 26, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5298 ### What is the issue? Sonatype nexus proxy was configured and worked, but 2 weeks ago it started giving an error when requesting a manifest. ``` 2024-06-24 22:19:00,375+0300 DEBUG [nexus-httpclient-eviction-thread] *SYSTEM org.apache.http.impl.conn.CPool - Connection [id:3377][route:{s}->[https://registry.ollama.ai:443](https://registry.ollama.ai/)][state:null] expired @ Mon Jun 24 22:18:56 MSK 2024 2024-06-24 22:20:23,263+0300 DEBUG [qtp1079333755-4212] anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/latest > GET /v2/library/all-minilm/manifests/latest HTTP/1.1 2024-06-24 22:20:25,591+0300 DEBUG [qtp1079333755-4212] anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/latest < HTTP/1.1 200 OK @ 2.329 s 2024-06-24 22:20:25,594+0300 DEBUG [qtp1079333755-4212] anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb > GET /v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb HTTP/1.1 2024-06-24 22:20:25,953+0300 DEBUG [qtp1079333755-4212] anonymous org.sonatype.nexus.httpclient.outbound - https://registry.ollama.ai/v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb < HTTP/1.1 500 Internal Server Error @ 358.1 ms 2024-06-24 22:20:25,953+0300 INFO [qtp1079333755-4212] anonymous org.sonatype.nexus.repository.httpclient.internal.HttpClientFacetImpl - Repository status for ollamaio-docker-proxy changed from AVAILABLE to UNAVAILABLE - reason Internal Server Error for https://registry.ollama.ai/ ``` Nexus tries to get sha file but gets an error https://registry.ollama.ai/v2/library/all-minilm/manifests/sha256:e05286252610b4a128ff0f46cff09a65898dfff124afd0778b5a3705947869cb registry.ollama.ai can`t handle colon at url manifests **any link with colon response error** https://registry.ollama.ai/v2/library/all-minilm/manifests/anyurl:a 500 Internal Server Error {"errors":[{"code":"INTERNAL_ERROR","message":"internal error","detail":null}]} **any link without colon work correctly** 404 Not Found https://registry.ollama.ai/v2/library/all-minilm/manifests/anyurl {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown"}]} Can you fix "500 Internal Server Error"? ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-22 07:43:41 -05:00
GiteaMirror commented 2026-04-22 07:43:42 -05:00
Author
Owner
Copy Link

@ajacward commented on GitHub (Jul 5, 2024):

We are encountering a similar issue with our Sonatype Nexus proxy. Which version of Sonatype Nexus was this last working successfully and which version was it discovered that it no longer worked?

<!-- gh-comment-id:2211332232 --> @ajacward commented on GitHub (Jul 5, 2024): We are encountering a similar issue with our Sonatype Nexus proxy. Which version of Sonatype Nexus was this last working successfully and which version was it discovered that it no longer worked?
GiteaMirror commented 2026-04-22 07:43:42 -05:00
Author
Owner
Copy Link

@mikhail-fedotovsky commented on GitHub (Jul 11, 2024):

Nexus Version - 3.41.1-01
We haven`t update from 2022

<!-- gh-comment-id:2222694060 --> @mikhail-fedotovsky commented on GitHub (Jul 11, 2024): Nexus Version - 3.41.1-01 We haven`t update from 2022
GiteaMirror commented 2026-04-22 07:43:43 -05:00
Author
Owner
Copy Link

@rbah31 commented on GitHub (Jul 16, 2024):

Hello, I am also encountering the same issue with my Sonatype Nexus Proxy (v3.64) since a few days now.

<!-- gh-comment-id:2230195424 --> @rbah31 commented on GitHub (Jul 16, 2024): Hello, I am also encountering the same issue with my Sonatype Nexus Proxy (v3.64) since a few days now.
GiteaMirror commented 2026-04-22 07:43:43 -05:00
Author
Owner
Copy Link

@Freydiere commented on GitHub (Jul 16, 2024):

Hi, I've been synchronizing models successfully for a few weeks and I noticed ~2 weeks ago that replications were not working anymore. Similar issue as the above. I'm using a Sonatype Nexus instance too to connect to ollama.

<!-- gh-comment-id:2230412878 --> @Freydiere commented on GitHub (Jul 16, 2024): Hi, I've been synchronizing models successfully for a few weeks and I noticed ~2 weeks ago that replications were not working anymore. Similar issue as the above. I'm using a Sonatype Nexus instance too to connect to ollama.
GiteaMirror commented 2026-04-22 07:43:44 -05:00
Author
Owner
Copy Link

@bmizerany commented on GitHub (Aug 23, 2024):

It seems something on the client end is trying to address the manifest by digest, which isn't supported. If I curl https://registry.ollama.ai/v2/library/all-minilm/manifests/latest I get the manifest as expected.

Can you confirm nothing is meddling with the request on your end or in between?

<!-- gh-comment-id:2307881573 --> @bmizerany commented on GitHub (Aug 23, 2024): It seems something on the client end is trying to address the manifest by digest, which isn't supported. If I ` curl https://registry.ollama.ai/v2/library/all-minilm/manifests/latest` I get the manifest as expected. Can you confirm nothing is meddling with the request on your end or in between?
GiteaMirror commented 2026-04-22 07:43:44 -05:00
Author
Owner
Copy Link

@rbah31 commented on GitHub (Aug 27, 2024):

In my case, the Docker proxy instance is not returning a 502 Bad Gateway anymore since a few days. I have updated too my Nexus to v3.70.1.

From my Nexus logs, I see that when I try to replicate any Ollama image, I have aorg.sonatype.nexus.httpclient.outbound - https://ollama.com/v2/library/llama3.1/tags/list < HTTP/1.1 404 Not Found.

I was wondering if there was any change that have been done on the ollama registry APIs.

<!-- gh-comment-id:2312605370 --> @rbah31 commented on GitHub (Aug 27, 2024): In my case, the Docker proxy instance is not returning a `502 Bad Gateway` anymore since a few days. I have updated too my Nexus to v3.70.1. From my Nexus logs, I see that when I try to replicate any Ollama image, I have a`org.sonatype.nexus.httpclient.outbound - https://ollama.com/v2/library/llama3.1/tags/list < HTTP/1.1 404 Not Found`. I was wondering if there was any change that have been done on the ollama registry APIs.
GiteaMirror commented 2026-04-22 07:43:45 -05:00
Author
Owner
Copy Link

@cniweb commented on GitHub (Nov 27, 2024):

@rbah31 Does it work now?
Were you able to find a solution to proxy the registry via Nexus Repository Manager?

<!-- gh-comment-id:2503093090 --> @cniweb commented on GitHub (Nov 27, 2024): @rbah31 Does it work now? Were you able to find a solution to proxy the registry via Nexus Repository Manager?
GiteaMirror commented 2026-04-22 07:43:45 -05:00
Author
Owner
Copy Link

@zxbuzzy commented on GitHub (Dec 25, 2024):

we are still have issues with it, however the error itself has changed
Error: pull model manifest: 400 DIGEST INVALID, message: "provided sigest did not match uploaded content
which seems a bit odd

<!-- gh-comment-id:2561653461 --> @zxbuzzy commented on GitHub (Dec 25, 2024): we are still have issues with it, however the error itself has changed `Error: pull model manifest: 400 DIGEST INVALID, message: "provided sigest did not match uploaded content` which seems a bit odd
GiteaMirror commented 2026-04-22 07:43:46 -05:00
Author
Owner
Copy Link

@zxbuzzy commented on GitHub (Dec 25, 2024):

by the way, @cniweb can you tell, please, have you found the solution?

<!-- gh-comment-id:2561653961 --> @zxbuzzy commented on GitHub (Dec 25, 2024): by the way, @cniweb can you tell, please, have you found the solution?
GiteaMirror commented 2026-04-22 07:43:46 -05:00
Author
Owner
Copy Link

@cniweb commented on GitHub (Dec 26, 2024):

@zxbuzzy Unfortunately not.
I think this would have to be built into the Ollama registry implementation.

<!-- gh-comment-id:2562986178 --> @cniweb commented on GitHub (Dec 26, 2024): @zxbuzzy Unfortunately not. I think this would have to be built into the Ollama registry implementation.
GiteaMirror commented 2026-04-22 07:43:47 -05:00
Author
Owner
Copy Link

@cniweb commented on GitHub (Jan 9, 2025):

It seems something on the client end is trying to address the manifest by digest, which isn't supported. If I curl https://registry.ollama.ai/v2/library/all-minilm/manifests/latest I get the manifest as expected.

Can you confirm nothing is meddling with the request on your end or in between?

Can you test it on Sonatype Nexus (OSS Version is free!)?

<!-- gh-comment-id:2579350262 --> @cniweb commented on GitHub (Jan 9, 2025): > It seems something on the client end is trying to address the manifest by digest, which isn't supported. If I ` curl https://registry.ollama.ai/v2/library/all-minilm/manifests/latest` I get the manifest as expected. > > Can you confirm nothing is meddling with the request on your end or in between? Can you test it on Sonatype Nexus (OSS Version is free!)?
GiteaMirror commented 2026-04-22 07:43:47 -05:00
Author
Owner
Copy Link

@zxbuzzy commented on GitHub (Jan 9, 2025):

It seems something on the client end is trying to address the manifest by digest, which isn't supported. If I curl https://registry.ollama.ai/v2/library/all-minilm/manifests/latest I get the manifest as expected.
Can you confirm nothing is meddling with the request on your end or in between?

Can you test it on Sonatype Nexus (OSS Version is free!)?

yep, I've tested and get an error mentioned above
Error: pull model manifest: 400 DIGEST INVALID, message: "provided sigest did not match uploaded content"
this is a log from nexus (can't actually remember the path of log, but I think you get it)
I am confused because somehow Nexus tries to match different sha256 hash (not which registry returns)
and I just don't get why. I mean, we have a lot of different proxies of container registries: ICR, Google Artifactory, of course Docker Hub and they work as expected.

<!-- gh-comment-id:2580930194 --> @zxbuzzy commented on GitHub (Jan 9, 2025): > > It seems something on the client end is trying to address the manifest by digest, which isn't supported. If I ` curl https://registry.ollama.ai/v2/library/all-minilm/manifests/latest` I get the manifest as expected. > > Can you confirm nothing is meddling with the request on your end or in between? > > Can you test it on Sonatype Nexus (OSS Version is free!)? yep, I've tested and get an error mentioned above `Error: pull model manifest: 400 DIGEST INVALID, message: "provided sigest did not match uploaded content"` this is a log from nexus (can't actually remember the path of log, but I think you get it) I am confused because somehow Nexus tries to match different sha256 hash (not which registry returns) and I just don't get why. I mean, we have a lot of different proxies of container registries: ICR, Google Artifactory, of course Docker Hub and they work as expected.
GiteaMirror commented 2026-04-22 07:43:48 -05:00
Author
Owner
Copy Link

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

same......

<!-- gh-comment-id:2639217899 --> @bdytx5 commented on GitHub (Feb 6, 2025): same......
GiteaMirror commented 2026-04-22 07:43:49 -05:00
Author
Owner
Copy Link

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

same on Mac, is it a server side issue?

<!-- gh-comment-id:2639233941 --> @skyairmj commented on GitHub (Feb 6, 2025): same on Mac, is it a server side issue?
GiteaMirror commented 2026-04-22 07:43:49 -05:00
Author
Owner
Copy Link

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

same on Mac, is it a server side issue?

There was a server issue it is working fine now

<!-- gh-comment-id:2639265393 --> @suazhanif commented on GitHub (Feb 6, 2025): > same on Mac, is it a server side issue? There was a server issue it is working fine now
GiteaMirror commented 2026-04-22 07:43:49 -05:00
Author
Owner
Copy Link

@maratkh commented on GitHub (Mar 19, 2025):

UP

<!-- gh-comment-id:2737155944 --> @maratkh commented on GitHub (Mar 19, 2025): UP
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#29083
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?