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 #15201] Ollama v0.19.0: 'ollama pull' fails with 'ssh: no key found' error on macOS ARM64 #71789

New Issue
Closed
opened 2026-05-05 02:30:04 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-05 02:30:04 -05:00
Owner
Copy Link

Originally created by @tcyxk on GitHub (Apr 1, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15201

Bug Description

On macOS ARM64 (Apple Silicon), after a fresh install of Ollama v0.19.0 via Homebrew, any attempt to pull a model fails immediately with the error:

Error: pull model manifest: ssh: no key found

This occurs with:

  • ollama pull bge-m3
  • ollama pull nomic-embed-text
  • ollama create (using a local Modelfile)

No SSH keys or credentials are configured, and the operation does not involve any SSH server.

Steps to Reproduce

  1. brew install ollama (installs v0.19.0 on macOS ARM64)
  2. ollama serve (daemon starts successfully)
  3. ollama pull bge-m3

Expected: Model downloads and installs
Actual: Error: pull model manifest: ssh: no key found

Environment

  • macOS (Apple Silicon, ARM64)
  • Ollama v0.19.0 (installed via Homebrew)
  • No SSH keys configured

Additional Context

  • OLLAMA_REGISTRY_HOST environment variable has no effect
  • Creating a dummy SSH key at ~/.ssh/id_ed25519 does not resolve the issue
  • Direct HTTP access to registry.ollama.ai works fine (verified with curl)
  • The /api/pull endpoint always returns {error: "pull model manifest: ssh: no key found"}
  • This appears to be an internal code path that unconditionally attempts SSH key resolution even for plain HTTPS registry downloads
Originally created by @tcyxk on GitHub (Apr 1, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15201 ## Bug Description On macOS ARM64 (Apple Silicon), after a fresh install of Ollama v0.19.0 via Homebrew, any attempt to pull a model fails immediately with the error: Error: pull model manifest: ssh: no key found This occurs with: - ollama pull bge-m3 - ollama pull nomic-embed-text - ollama create (using a local Modelfile) No SSH keys or credentials are configured, and the operation does not involve any SSH server. ## Steps to Reproduce 1. brew install ollama (installs v0.19.0 on macOS ARM64) 2. ollama serve (daemon starts successfully) 3. ollama pull bge-m3 Expected: Model downloads and installs Actual: Error: pull model manifest: ssh: no key found ## Environment - macOS (Apple Silicon, ARM64) - Ollama v0.19.0 (installed via Homebrew) - No SSH keys configured ## Additional Context - OLLAMA_REGISTRY_HOST environment variable has no effect - Creating a dummy SSH key at ~/.ssh/id_ed25519 does not resolve the issue - Direct HTTP access to registry.ollama.ai works fine (verified with curl) - The /api/pull endpoint always returns {error: "pull model manifest: ssh: no key found"} - This appears to be an internal code path that unconditionally attempts SSH key resolution even for plain HTTPS registry downloads
GiteaMirror commented 2026-05-05 02:30:06 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 1, 2026):

What's the output of

ls -l ~/.ollama/id*

Server logs will aid in debugging.

<!-- gh-comment-id:4173629283 --> @rick-github commented on GitHub (Apr 1, 2026): What's the output of ``` ls -l ~/.ollama/id* ``` [Server logs](https://docs.ollama.com/troubleshooting) will aid in debugging.
GiteaMirror commented 2026-05-05 02:30:07 -05:00
Author
Owner
Copy Link

@tcyxk commented on GitHub (Apr 2, 2026):

The issue is resolved. Here's what I found and the solution:

SSH key existed but was missing from known_hosts:

ls -la ~/.ollama/id_ed25519*
-rw------- 1 user staff 387 Apr  2 07:39 /Users/sq/.ollama/id_ed25519
-rw-r--r-- 1 user staff  81 Apr  2 07:39 /Users/sq/.ollama/id_ed25519.pub

Solution:
Adding GitHub's SSH host key to ~/.ssh/known_hosts fixed the issue:

ssh-keyscan github.com >> ~/.ssh/known_hosts 2>/dev/null

After adding the known_hosts entry, ollama pull works perfectly.

Root cause: Ollama v0.19.0 appears to resolve the GitHub registry via SSH even when downloading over HTTPS, requiring the host key to be in known_hosts.

<!-- gh-comment-id:4174227084 --> @tcyxk commented on GitHub (Apr 2, 2026): The issue is resolved. Here's what I found and the solution: **SSH key existed but was missing from known_hosts:** ``` ls -la ~/.ollama/id_ed25519* -rw------- 1 user staff 387 Apr 2 07:39 /Users/sq/.ollama/id_ed25519 -rw-r--r-- 1 user staff 81 Apr 2 07:39 /Users/sq/.ollama/id_ed25519.pub ``` **Solution:** Adding GitHub's SSH host key to ~/.ssh/known_hosts fixed the issue: ```bash ssh-keyscan github.com >> ~/.ssh/known_hosts 2>/dev/null ``` After adding the known_hosts entry, ollama pull works perfectly. **Root cause:** Ollama v0.19.0 appears to resolve the GitHub registry via SSH even when downloading over HTTPS, requiring the host key to be in known_hosts.
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
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#71789
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?