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

[GH-ISSUE #5974] tls: failed to verify certificate: x509: certificate is valid for ollama.com, www.ollama.com, registry.ollama.com, not registry.ollama.ai #65771

New Issue
Closed
opened 2026-05-03 22:37:36 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-03 22:37:36 -05:00
Owner
Copy Link

Originally created by @zmiimz on GitHub (Jul 26, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5974

What is the issue?

Error message on attempt to pull some model:

Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/llama3.1/manifests/latest": tls: failed to verify certificate: x509: certificate is valid for ollama.com, www.ollama.com, registry.ollama.com, not registry.ollama.ai

checked

openssl s_client -connect registry.ollama.ai:443 -showcerts </dev/null 2>/dev/null | openssl x509 -noout -text | grep -A1 "Subject Alternative Name"
X509v3 Subject Alternative Name:
DNS:ollama.ai, DNS:*.ollama.ai

linked lib in binary seeems to ignore the settings DNS:*.ollama.ai ?

./ollama-linux-amd64 --version
ollama version is 0.3.0

openssl -v
OpenSSL 3.3.1 4 Jun 2024 (Library: OpenSSL 3.3.1 4 Jun 2024)

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.3.0, 0.2.8, 0.2.7

Originally created by @zmiimz on GitHub (Jul 26, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5974 ### What is the issue? Error message on attempt to pull some model: >Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/llama3.1/manifests/latest": tls: failed to verify certificate: x509: certificate is valid for ollama.com, www.ollama.com, registry.ollama.com, not registry.ollama.ai checked >openssl s_client -connect registry.ollama.ai:443 -showcerts </dev/null 2>/dev/null | openssl x509 -noout -text | grep -A1 "Subject Alternative Name" X509v3 Subject Alternative Name: DNS:ollama.ai, DNS:*.ollama.ai linked lib in binary seeems to ignore the settings DNS:*.ollama.ai ? >./ollama-linux-amd64 --version ollama version is 0.3.0 >openssl -v OpenSSL 3.3.1 4 Jun 2024 (Library: OpenSSL 3.3.1 4 Jun 2024) ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.3.0, 0.2.8, 0.2.7
GiteaMirror added the bug label 2026-05-03 22:37:36 -05:00
GiteaMirror commented 2026-05-03 22:37:44 -05:00
Author
Owner
Copy Link

@zmiimz commented on GitHub (Jul 26, 2024):

Sorry, locally found an outdated entry in /etc/hosts that was manually added some time ago for registry.ollama.ai. After commenting it out, everything works.
#34.120.132.20 registry.ollama.ai

<!-- gh-comment-id:2252233895 --> @zmiimz commented on GitHub (Jul 26, 2024): Sorry, locally found an outdated entry in /etc/hosts that was manually added some time ago for registry.ollama.ai. After commenting it out, everything works. #34.120.132.20 registry.ollama.ai
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#65771
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?