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

[GH-ISSUE #5456] ollama push suddenly not working / giving not authorized error #3412

New Issue
Closed
opened 2026-04-12 14:03:13 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-12 14:03:13 -05:00
Owner
Copy Link

Originally created by @ashokgit on GitHub (Jul 3, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5456

What is the issue?

Hi, I get the following error on push

ollama push myuseer/model-name

retrieving manifest
pushing 663944096011... 100% ▕█████████████████████████████▏ 667 MB
pushing c3be5dc5651b... 100% ▕█████████████████████████████▏ 54 B
pushing 1cb5df2a171b... 100% ▕█████████████████████████████▏ 32 B
pushing 395c6bda52c3... 100% ▕█████████████████████████████▏ 413 B
pushing manifest
Error: you are not authorized to push to this namespace, create the model under a namespace you own

I've followed the push model guidelines.
also copied ~/.ollama/id_ed25519.pub
and /usr/share/ollama/.ollama/id_ed25519.pub over to settings

was working just fine 2 days ago

I believe i only restarted ollama, should that cause this or am i missing something?

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.1.40

Originally created by @ashokgit on GitHub (Jul 3, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5456 ### What is the issue? Hi, I get the following error on push ollama push myuseer/model-name retrieving manifest pushing 663944096011... 100% ▕█████████████████████████████▏ 667 MB pushing c3be5dc5651b... 100% ▕█████████████████████████████▏ 54 B pushing 1cb5df2a171b... 100% ▕█████████████████████████████▏ 32 B pushing 395c6bda52c3... 100% ▕█████████████████████████████▏ 413 B pushing manifest Error: you are not authorized to push to this namespace, create the model under a namespace you own I've followed the push model guidelines. also copied ~/.ollama/id_ed25519.pub and /usr/share/ollama/.ollama/id_ed25519.pub over to settings was working just fine 2 days ago I believe i only restarted ollama, should that cause this or am i missing something? ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.1.40
GiteaMirror added the bug label 2026-04-12 14:03:13 -05:00
GiteaMirror commented 2026-04-12 14:03:14 -05:00
Author
Owner
Copy Link

@ashokgit commented on GitHub (Jul 3, 2024):

Update: I've narrowed down a potential cause. I had a running ollama instance running with

docker run -d -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama

but somehow the 'ollama push' commands from terminal were being sent over to this ollama docker instance ...

so when i ran docker logs for some other purpose, i got this
time=2024-07-03T13:17:31.057Z level=ERROR source=images.go:963 msg="jwt token does not contain 3 parts"
time=2024-07-03T13:17:31.087Z level=INFO source=images.go:794 msg="error uploading blob: 400: {"errors":[{"code":"ACCESS_DENIED","message":"access denied"}]}"
[GIN] 2024/07/03 - 13:17:31 | 200 | 804.021366ms | 172.17.0.1 | POST "/api/push"
[GIN] 2024/07/03 - 13:26:42 | 200 | 24.522µs | 172.17.0.1 | HEAD "/"
[GIN] 2024/07/03 - 13:26:42 | 200 | 1.015687ms | 172.17.0.1 | POST "/api/copy"
[GIN] 2024/07/03 - 13:26:52 | 200 | 19.598µs | 172.17.0.1 | HEAD "/"
time=2024-07-03T13:26:57.453Z level=ERROR source=images.go:963 msg="jwt token does not contain 3 parts"

<!-- gh-comment-id:2206097212 --> @ashokgit commented on GitHub (Jul 3, 2024): Update: I've narrowed down a potential cause. I had a running ollama instance running with docker run -d -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama but somehow the 'ollama push' commands from terminal were being sent over to this ollama docker instance ... so when i ran docker logs for some other purpose, i got this time=2024-07-03T13:17:31.057Z level=ERROR source=images.go:963 msg="jwt token does not contain 3 parts" time=2024-07-03T13:17:31.087Z level=INFO source=images.go:794 msg="error uploading blob: 400: {\"errors\":[{\"code\":\"ACCESS_DENIED\",\"message\":\"access denied\"}]}" [GIN] 2024/07/03 - 13:17:31 | 200 | 804.021366ms | 172.17.0.1 | POST "/api/push" [GIN] 2024/07/03 - 13:26:42 | 200 | 24.522µs | 172.17.0.1 | HEAD "/" [GIN] 2024/07/03 - 13:26:42 | 200 | 1.015687ms | 172.17.0.1 | POST "/api/copy" [GIN] 2024/07/03 - 13:26:52 | 200 | 19.598µs | 172.17.0.1 | HEAD "/" time=2024-07-03T13:26:57.453Z level=ERROR source=images.go:963 msg="jwt token does not contain 3 parts"
GiteaMirror commented 2026-04-12 14:03:16 -05:00
Author
Owner
Copy Link

@ashokgit commented on GitHub (Jul 3, 2024):

Solved after stopping ollama docker instance

<!-- gh-comment-id:2206125614 --> @ashokgit commented on GitHub (Jul 3, 2024): Solved after stopping ollama docker instance
GiteaMirror commented 2026-04-12 14:03:16 -05:00
Author
Owner
Copy Link

@Pravda77 commented on GitHub (Sep 17, 2025):

I am experiencing the exact same server-side error, level=ERROR source=images.go:963 msg="jwt token does not contain 3 parts", but in a different scenario without Docker.

My setup:

  • OS: MiniOS (a Debian-based Linux Live system)
  • Ollama Version: 0.1.41
  • Environment: Running the ollama binary directly from the shell, no Docker involved.

Client/Server Behavior:

  • The client fails with the misleading error: Error: pull model manifest: file does not exist.
  • The server logs the jwt token does not contain 3 parts error, but then incorrectly reports a 200 OK for the /api/pull request.
  • Basic network connectivity is fine (curl to ollama.ai works perfectly).

This confirms the JWT issue is not exclusively related to Docker and can be triggered on a standard Linux environment, possibly due to a specific OS configuration or networking stack.

<!-- gh-comment-id:3302955923 --> @Pravda77 commented on GitHub (Sep 17, 2025): I am experiencing the exact same server-side error, `level=ERROR source=images.go:963 msg="jwt token does not contain 3 parts"`, but in a different scenario without Docker. **My setup:** - **OS:** MiniOS (a Debian-based Linux Live system) - **Ollama Version:** 0.1.41 - **Environment:** Running the `ollama` binary directly from the shell, no Docker involved. **Client/Server Behavior:** - The client fails with the misleading error: `Error: pull model manifest: file does not exist`. - The server logs the `jwt token does not contain 3 parts` error, but then incorrectly reports a `200 OK` for the `/api/pull` request. - Basic network connectivity is fine (`curl` to `ollama.ai` works perfectly). This confirms the JWT issue is not exclusively related to Docker and can be triggered on a standard Linux environment, possibly due to a specific OS configuration or networking stack.
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#3412
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?