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 #3336] ollama.ai certificate has expired, not possible to download models #2054

New Issue
Closed
opened 2026-04-12 12:16:53 -05:00 by GiteaMirror · 80 comments
GiteaMirror commented 2026-04-12 12:16:53 -05:00
Owner
Copy Link

Originally created by @psy-q on GitHub (Mar 25, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3336

What is the issue?

The ollama.ai certificate has expired today, ollama now can't download models:

ollama run mistral
pulling manifest 
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/mistral/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z

What did you expect to see?

You should be able to pull models using the ollama command.

Steps to reproduce

Try to pull a model.

Are there any recent changes that introduced the issue?

No response

OS

Linux

Architecture

amd64

Platform

No response

Ollama version

0.1.29

GPU

Nvidia

GPU info

No response

CPU

No response

Other software

No response

Originally created by @psy-q on GitHub (Mar 25, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3336 ### What is the issue? The ollama.ai certificate has expired today, ollama now can't download models: ``` ollama run mistral pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/mistral/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z ``` ### What did you expect to see? You should be able to pull models using the `ollama` command. ### Steps to reproduce Try to pull a model. ### Are there any recent changes that introduced the issue? _No response_ ### OS Linux ### Architecture amd64 ### Platform _No response_ ### Ollama version 0.1.29 ### GPU Nvidia ### GPU info _No response_ ### CPU _No response_ ### Other software _No response_
GiteaMirror added the bug label 2026-04-12 12:16:53 -05:00
GiteaMirror commented 2026-04-12 12:16:55 -05:00
Author
Owner
Copy Link

@mteletin commented on GitHub (Mar 25, 2024):

Could it be a validation bug? One time is UTC, the other one is not and the error says that the time is in the future basically.
It's clear that one has Z (UTC) the other one does not.

This "current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z" is obviously not true. (I'm having the exact same issue now and it will probably go away in a couple of hours once the time zone difference does not produce this effect any more).

<!-- gh-comment-id:2017390994 --> @mteletin commented on GitHub (Mar 25, 2024): Could it be a validation bug? One time is UTC, the other one is not and the error says that the time is in the future basically. It's clear that one has Z (UTC) the other one does not. This "current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z" is obviously not true. (I'm having the exact same issue now and it will probably go away in a couple of hours once the time zone difference does not produce this effect any more).
GiteaMirror commented 2026-04-12 12:16:55 -05:00
Author
Owner
Copy Link

@ssams commented on GitHub (Mar 25, 2024):

Could it be a validation bug? One time is UTC, the other one is not and the error says that the time is in the future basically. It's clear that one has Z (UTC) the other one does not.

This "current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z" is obviously not true. (I'm having the exact same issue now and it will probably go away in a couple of hours once the time zone difference does not produce this effect any more).

2024-03-25T08:28:33+01:00 is equal to 2024-03-25T07:28:33Z ... 07:28 > 07:17. this is not about timezones, the certificate really has expired just a few minutes ago. we'll need to wait until an admin of the service can update the certificate.

<!-- gh-comment-id:2017395878 --> @ssams commented on GitHub (Mar 25, 2024): > Could it be a validation bug? One time is UTC, the other one is not and the error says that the time is in the future basically. It's clear that one has Z (UTC) the other one does not. > > This "current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z" is obviously not true. (I'm having the exact same issue now and it will probably go away in a couple of hours once the time zone difference does not produce this effect any more). 2024-03-25T08:28:33+01:00 is equal to 2024-03-25T07:28:33Z ... 07:28 > 07:17. this is not about timezones, the certificate really has expired just a few minutes ago. we'll need to wait until an admin of the service can update the certificate.
GiteaMirror commented 2026-04-12 12:16:56 -05:00
Author
Owner
Copy Link

@mteletin commented on GitHub (Mar 25, 2024):

Could it be a validation bug? One time is UTC, the other one is not and the error says that the time is in the future basically. It's clear that one has Z (UTC) the other one does not.
This "current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z" is obviously not true. (I'm having the exact same issue now and it will probably go away in a couple of hours once the time zone difference does not produce this effect any more).

2024-03-25T08:28:33+01:00 is equal to 2024-03-25T07:28:33Z ... 07:28 > 07:17. this is not about timezones, the certificate really has expired just a few minutes ago. we'll need to wait until an admin of the service can update the certificate.

you are right, was thinking about beginning dates not end dates... my bad

<!-- gh-comment-id:2017396913 --> @mteletin commented on GitHub (Mar 25, 2024): > > Could it be a validation bug? One time is UTC, the other one is not and the error says that the time is in the future basically. It's clear that one has Z (UTC) the other one does not. > > This "current time 2024-03-25T08:28:33+01:00 is after 2024-03-25T07:17:47Z" is obviously not true. (I'm having the exact same issue now and it will probably go away in a couple of hours once the time zone difference does not produce this effect any more). > > 2024-03-25T08:28:33+01:00 is equal to 2024-03-25T07:28:33Z ... 07:28 > 07:17. this is not about timezones, the certificate really has expired just a few minutes ago. we'll need to wait until an admin of the service can update the certificate. you are right, was thinking about beginning dates not end dates... my bad
GiteaMirror commented 2026-04-12 12:16:56 -05:00
Author
Owner
Copy Link

@agentgill commented on GitHub (Mar 25, 2024):

I downloaded only this morning, was able to successfully download mistral, then went to download gemma and hit this error

<!-- gh-comment-id:2017398686 --> @agentgill commented on GitHub (Mar 25, 2024): I downloaded only this morning, was able to successfully download mistral, then went to download gemma and hit this error
GiteaMirror commented 2026-04-12 12:16:57 -05:00
Author
Owner
Copy Link

@luckrnx09 commented on GitHub (Mar 25, 2024):

same here.

<!-- gh-comment-id:2017409771 --> @luckrnx09 commented on GitHub (Mar 25, 2024): same here.
GiteaMirror commented 2026-04-12 12:16:57 -05:00
Author
Owner
Copy Link

@BothSavage commented on GitHub (Mar 25, 2024):

i hit this error too,waiting.....

<!-- gh-comment-id:2017409977 --> @BothSavage commented on GitHub (Mar 25, 2024): i hit this error too,waiting.....
GiteaMirror commented 2026-04-12 12:16:58 -05:00
Author
Owner
Copy Link

@Henmanolc commented on GitHub (Mar 25, 2024):

Not really helpful, I guess, but I am facing the issue as well.

<!-- gh-comment-id:2017411952 --> @Henmanolc commented on GitHub (Mar 25, 2024): Not really helpful, I guess, but I am facing the issue as well.
GiteaMirror commented 2026-04-12 12:16:58 -05:00
Author
Owner
Copy Link

@MMHHRR commented on GitHub (Mar 25, 2024):

waiting...

<!-- gh-comment-id:2017412242 --> @MMHHRR commented on GitHub (Mar 25, 2024): waiting...
GiteaMirror commented 2026-04-12 12:16:59 -05:00
Author
Owner
Copy Link

@eramax commented on GitHub (Mar 25, 2024):

same here.

<!-- gh-comment-id:2017413033 --> @eramax commented on GitHub (Mar 25, 2024): same here.
GiteaMirror commented 2026-04-12 12:16:59 -05:00
Author
Owner
Copy Link

@Officialstrike commented on GitHub (Mar 25, 2024):

Please refrain from commenting "+1", "waiting," "me too," "same here," or any derivative thereof; instead, please like the original post! The comments should be used to add valuable contributions, and liking the original post makes it clear that you are also affected.

<!-- gh-comment-id:2017415251 --> @Officialstrike commented on GitHub (Mar 25, 2024): Please refrain from commenting "+1", "waiting," "me too," "same here," or any derivative thereof; instead, please like the original post! The comments should be used to add valuable contributions, and liking the original post makes it clear that you are also affected.
GiteaMirror commented 2026-04-12 12:17:00 -05:00
Author
Owner
Copy Link

@renhiyama commented on GitHub (Mar 25, 2024):

@Officialstrike is it possible to bypass this warning/error by some --force command or changing timezone temporarily?

<!-- gh-comment-id:2017426068 --> @renhiyama commented on GitHub (Mar 25, 2024): @Officialstrike is it possible to bypass this warning/error by some `--force` command or changing timezone temporarily?
GiteaMirror commented 2026-04-12 12:17:00 -05:00
Author
Owner
Copy Link

@Officialstrike commented on GitHub (Mar 25, 2024):

Current temporary workaround: set your clock a couple of hours before Mon, 25 Mar 2024 07:17:47 GMT.

Please note: your visual clock may be different from the system clock, it is important that your system clock is used!

For Linux, you can do the following(you may have to change it to a higher value depending on when you read this)

<!-- gh-comment-id:2017427499 --> @Officialstrike commented on GitHub (Mar 25, 2024): Current temporary workaround: set your clock a couple of hours before `Mon, 25 Mar 2024 07:17:47 GMT`. **Please note: your visual clock may be different from the system clock, it is important that your system clock is used!** [For Linux, you can do the following(you may have to change it to a higher value depending on when you read this)](https://github.com/ollama/ollama/issues/3336#issuecomment-2017428194)
GiteaMirror commented 2026-04-12 12:17:01 -05:00
Author
Owner
Copy Link

@khera-shanu commented on GitHub (Mar 25, 2024):

same here

<!-- gh-comment-id:2017428034 --> @khera-shanu commented on GitHub (Mar 25, 2024): same here
GiteaMirror commented 2026-04-12 12:17:01 -05:00
Author
Owner
Copy Link

@kaetemi commented on GitHub (Mar 25, 2024):

sudo systemctl stop systemd-timesyncd
sudo date -s '-2 hours'

To turn your clock back on Ubuntu

<!-- gh-comment-id:2017428194 --> @kaetemi commented on GitHub (Mar 25, 2024): sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours' To turn your clock back on Ubuntu
GiteaMirror commented 2026-04-12 12:17:02 -05:00
Author
Owner
Copy Link

@Officialstrike commented on GitHub (Mar 25, 2024):

@Officialstrike is it possible to bypass this warning/error by some --force command or changing timezone temporarily?

Yes, see my comment about setting your clock backwards

<!-- gh-comment-id:2017429145 --> @Officialstrike commented on GitHub (Mar 25, 2024): > @Officialstrike is it possible to bypass this warning/error by some `--force` command or changing timezone temporarily? Yes, see my comment about setting your clock backwards
GiteaMirror commented 2026-04-12 12:17:02 -05:00
Author
Owner
Copy Link

@renhiyama commented on GitHub (Mar 25, 2024):

Thanks it worked for me!

(I changed time via gnome settings. Prefer to not use terminal because its really unnecessary everywhere)

<!-- gh-comment-id:2017429245 --> @renhiyama commented on GitHub (Mar 25, 2024): Thanks it worked for me! (I changed time via gnome settings. Prefer to not use terminal because its really unnecessary everywhere)
GiteaMirror commented 2026-04-12 12:17:03 -05:00
Author
Owner
Copy Link

@SuperSonnix71 commented on GitHub (Mar 25, 2024):

I figured that workaround would be to change the date to before 2024-02-09T20:53:22Z. I changed the data using GUI
and still i cannot pull any models.....
pulling manifest
Error: pull model manifest: 401

on the other hand doing this through the terminal works!

sudo systemctl stop systemd-timesyncd
sudo date -s '-2 hours

<!-- gh-comment-id:2017439962 --> @SuperSonnix71 commented on GitHub (Mar 25, 2024): I figured that workaround would be to change the date to before 2024-02-09T20:53:22Z. I changed the data using GUI and still i cannot pull any models..... pulling manifest Error: pull model manifest: 401 on the other hand doing this through the terminal works! sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours
GiteaMirror commented 2026-04-12 12:17:03 -05:00
Author
Owner
Copy Link

@hhyqhh commented on GitHub (Mar 25, 2024):

sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours'

To turn your clock back on Ubuntu

The method was incredible but it did solve the problem!! 😀

<!-- gh-comment-id:2017441639 --> @hhyqhh commented on GitHub (Mar 25, 2024): > sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours' > > To turn your clock back on Ubuntu The method was incredible but it did solve the problem!! 😀
GiteaMirror commented 2026-04-12 12:17:04 -05:00
Author
Owner
Copy Link

@soone commented on GitHub (Mar 25, 2024):

I am waiting

<!-- gh-comment-id:2017451192 --> @soone commented on GitHub (Mar 25, 2024): I am waiting
GiteaMirror commented 2026-04-12 12:17:05 -05:00
Author
Owner
Copy Link

@raazuregai commented on GitHub (Mar 25, 2024):

same here.
Waiting.

<!-- gh-comment-id:2017458321 --> @raazuregai commented on GitHub (Mar 25, 2024): same here. Waiting.
GiteaMirror commented 2026-04-12 12:17:05 -05:00
Author
Owner
Copy Link

@Officialstrike commented on GitHub (Mar 25, 2024):

Please refrain from commenting "+1", "waiting," "me too," "same here," or any derivative thereof; instead, please like the original post! The comments should be used to add valuable contributions, and liking the original post makes it clear that you are also affected.

repost (so please are seeing it)

<!-- gh-comment-id:2017459358 --> @Officialstrike commented on GitHub (Mar 25, 2024): **Please refrain from commenting "+1", "waiting," "me too," "same here," or any derivative thereof**; instead, **please like the original post!** The comments should be used to add valuable contributions, and liking the original post makes it clear that you are also affected. *repost (so please are seeing it)*
GiteaMirror commented 2026-04-12 12:17:06 -05:00
Author
Owner
Copy Link

@dafei1288 commented on GitHub (Mar 25, 2024):

same too:

ollama run starcoder
pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/starcoder/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid:

<!-- gh-comment-id:2017460896 --> @dafei1288 commented on GitHub (Mar 25, 2024): same too: ollama run starcoder pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/starcoder/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid:
GiteaMirror commented 2026-04-12 12:17:07 -05:00
Author
Owner
Copy Link

@SlumberDemon commented on GitHub (Mar 25, 2024):

same too:

ollama run starcoder pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/starcoder/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid:

Stop commenting that, it won't fix the issue

<!-- gh-comment-id:2017461453 --> @SlumberDemon commented on GitHub (Mar 25, 2024): > same too: > > ollama run starcoder pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/starcoder/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: Stop commenting that, it won't fix the issue
GiteaMirror commented 2026-04-12 12:17:07 -05:00
Author
Owner
Copy Link

@MoonRide303 commented on GitHub (Mar 25, 2024):

@jmorganca Guys, seriously - you need to either manage and renew your certificates on time, or configure some automation for that (certbot / whatever).

<!-- gh-comment-id:2017463903 --> @MoonRide303 commented on GitHub (Mar 25, 2024): @jmorganca Guys, seriously - you need to either manage and renew your certificates on time, or configure some automation for that (certbot / whatever).
GiteaMirror commented 2026-04-12 12:17:08 -05:00
Author
Owner
Copy Link

@alperhankendi commented on GitHub (Mar 25, 2024):

Please refrain from commenting "+1", "waiting," "me too," "same here," or any derivative thereof; instead, please like the original post! The comments should be used to add valuable contributions, and liking the original post makes it clear that you are also affected.

repost (so please are seeing it)

same here

<!-- gh-comment-id:2017466289 --> @alperhankendi commented on GitHub (Mar 25, 2024): > **Please refrain from commenting "+1", "waiting," "me too," "same here," or any derivative thereof**; instead, **please like the original post!** The comments should be used to add valuable contributions, and liking the original post makes it clear that you are also affected. > > _repost (so please are seeing it)_ same here
GiteaMirror commented 2026-04-12 12:17:08 -05:00
Author
Owner
Copy Link

@Lase9 commented on GitHub (Mar 25, 2024):

same

<!-- gh-comment-id:2017466303 --> @Lase9 commented on GitHub (Mar 25, 2024): same
GiteaMirror commented 2026-04-12 12:17:09 -05:00
Author
Owner
Copy Link

@awillSoftwares commented on GitHub (Mar 25, 2024):

sudo systemctl stop systemd-timesyncd
sudo date -s '-2 hours'
solves this

<!-- gh-comment-id:2017467210 --> @awillSoftwares commented on GitHub (Mar 25, 2024): sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours' solves this
GiteaMirror commented 2026-04-12 12:17:10 -05:00
Author
Owner
Copy Link

@dafei1288 commented on GitHub (Mar 25, 2024):

sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours' solves this

itworks !!

<!-- gh-comment-id:2017472586 --> @dafei1288 commented on GitHub (Mar 25, 2024): > sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours' solves this itworks !!
GiteaMirror commented 2026-04-12 12:17:11 -05:00
Author
Owner
Copy Link

@BothSavage commented on GitHub (Mar 25, 2024):

image

macos -2 hours really works ,thanks

<!-- gh-comment-id:2017479353 --> @BothSavage commented on GitHub (Mar 25, 2024): <img width="689" alt="image" src="https://github.com/ollama/ollama/assets/38107458/f27f36fc-0683-40a2-a9e4-2f4d1d2d4b8c"> macos -2 hours really works ,thanks
GiteaMirror commented 2026-04-12 12:17:11 -05:00
Author
Owner
Copy Link

@Henmanolc commented on GitHub (Mar 25, 2024):

Also works on Windows 11 when manually changing the time through system settings. Thanks, downloading right now :)

<!-- gh-comment-id:2017480069 --> @Henmanolc commented on GitHub (Mar 25, 2024): Also works on Windows 11 when manually changing the time through system settings. Thanks, downloading right now :)
GiteaMirror commented 2026-04-12 12:17:12 -05:00
Author
Owner
Copy Link

@MMHHRR commented on GitHub (Mar 25, 2024):

wind 10 work, -2 hours really works ,thanks

<!-- gh-comment-id:2017487788 --> @MMHHRR commented on GitHub (Mar 25, 2024): wind 10 work, -2 hours really works ,thanks
GiteaMirror commented 2026-04-12 12:17:12 -05:00
Author
Owner
Copy Link

@WShawnMing commented on GitHub (Mar 25, 2024):

root@DESKTOP-ShawnMing:/home/shawn# timedatectl
Local time: Mon 2024-03-25 16:51:35 CST
Universal time: Mon 2024-03-25 08:51:35 UTC
RTC time: Mon 2024-03-25 08:51:35
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no i used the commands above ,System clock synchronized status is still yes,why?

<!-- gh-comment-id:2017493406 --> @WShawnMing commented on GitHub (Mar 25, 2024): root@DESKTOP-ShawnMing:/home/shawn# timedatectl Local time: Mon 2024-03-25 16:51:35 CST Universal time: Mon 2024-03-25 08:51:35 UTC RTC time: Mon 2024-03-25 08:51:35 Time zone: Asia/Shanghai (CST, +0800) System clock synchronized: yes NTP service: inactive RTC in local TZ: no i used the commands above ,System clock synchronized status is still yes,why?
GiteaMirror commented 2026-04-12 12:17:13 -05:00
Author
Owner
Copy Link

@WShawnMing commented on GitHub (Mar 25, 2024):

root@DESKTOP-ShawnMing:/home/shawn# timedatectl Local time: Mon 2024-03-25 16:51:35 CST Universal time: Mon 2024-03-25 08:51:35 UTC RTC time: Mon 2024-03-25 08:51:35 Time zone: Asia/Shanghai (CST, +0800) System clock synchronized: yes NTP service: inactive RTC in local TZ: no i used the commands above ,System clock synchronized status is still yes,why?

ok ,my fool,i have finished it

<!-- gh-comment-id:2017497184 --> @WShawnMing commented on GitHub (Mar 25, 2024): > root@DESKTOP-ShawnMing:/home/shawn# timedatectl Local time: Mon 2024-03-25 16:51:35 CST Universal time: Mon 2024-03-25 08:51:35 UTC RTC time: Mon 2024-03-25 08:51:35 Time zone: Asia/Shanghai (CST, +0800) System clock synchronized: yes NTP service: inactive RTC in local TZ: no i used the commands above ,System clock synchronized status is still yes,why? ok ,my fool,i have finished it
GiteaMirror commented 2026-04-12 12:17:13 -05:00
Author
Owner
Copy Link

@ShamithaReddy commented on GitHub (Mar 25, 2024):

Current temporary workaround: set your clock a couple of hours before Mon, 25 Mar 2024 07:17:47 GMT.

Setting it around 25th March 7: 20 AM IST is only working, and when i tried any other time, its giving the below error

Error: pull model manifest: 401

<!-- gh-comment-id:2017501664 --> @ShamithaReddy commented on GitHub (Mar 25, 2024): > Current temporary workaround: set your clock a couple of hours before `Mon, 25 Mar 2024 07:17:47 GMT`. Setting it around 25th March 7: 20 AM IST is only working, and when i tried any other time, its giving the below error `Error: pull model manifest: 401`
GiteaMirror commented 2026-04-12 12:17:14 -05:00
Author
Owner
Copy Link

@erictroebs commented on GitHub (Mar 25, 2024):

Setting it around 25th March 7: 20 AM IST is only working, and when i tried any other time, its giving the below error

Error: pull model manifest: 401

Do not increase the offset to more than a few hours. I tried two days first and it did not work.

<!-- gh-comment-id:2017507179 --> @erictroebs commented on GitHub (Mar 25, 2024): > Setting it around 25th March 7: 20 AM IST is only working, and when i tried any other time, its giving the below error > > `Error: pull model manifest: 401` Do not increase the offset to more than a few hours. I tried two days first and it did not work.
GiteaMirror commented 2026-04-12 12:17:14 -05:00
Author
Owner
Copy Link

@Officialstrike commented on GitHub (Mar 25, 2024):

Current temporary workaround: set your clock a couple of hours before Mon, 25 Mar 2024 07:17:47 GMT.

Setting it around 25th March 7: 20 AM IST is only working, and when i tried any other time, its giving the below error

Error: pull model manifest: 401

It is important you change your system clock, not your visual clock!

<!-- gh-comment-id:2017507562 --> @Officialstrike commented on GitHub (Mar 25, 2024): > > Current temporary workaround: set your clock a couple of hours before `Mon, 25 Mar 2024 07:17:47 GMT`. > > Setting it around 25th March 7: 20 AM IST is only working, and when i tried any other time, its giving the below error > > `Error: pull model manifest: 401` It is important you change your system clock, not your visual clock!
GiteaMirror commented 2026-04-12 12:17:15 -05:00
Author
Owner
Copy Link

@edisonzf2020 commented on GitHub (Mar 25, 2024):

Is the administrator here? Your registry.ollama.ai certificate has expired today. If it is not updated, the model cannot be pulled.

<!-- gh-comment-id:2017520467 --> @edisonzf2020 commented on GitHub (Mar 25, 2024): Is the administrator here? Your registry.ollama.ai certificate has expired today. If it is not updated, the model cannot be pulled.
GiteaMirror commented 2026-04-12 12:17:15 -05:00
Author
Owner
Copy Link

@WShawnMing commented on GitHub (Mar 25, 2024):

if you run in wsl2 , please set time '-2h' of windows

<!-- gh-comment-id:2017523583 --> @WShawnMing commented on GitHub (Mar 25, 2024): if you run in wsl2 , please set time '-2h' of windows
GiteaMirror commented 2026-04-12 12:17:16 -05:00
Author
Owner
Copy Link

@dongwang22 commented on GitHub (Mar 25, 2024):

Come on. Somebody fix it! This is the first time I have tried LLama. I even thought it was my fault to cause the error.

<!-- gh-comment-id:2017535091 --> @dongwang22 commented on GitHub (Mar 25, 2024): Come on. Somebody fix it! This is the first time I have tried LLama. I even thought it was my fault to cause the error.
GiteaMirror commented 2026-04-12 12:17:16 -05:00
Author
Owner
Copy Link

@fjibj commented on GitHub (Mar 25, 2024):

oh, my god, it's terrible.

<!-- gh-comment-id:2017537496 --> @fjibj commented on GitHub (Mar 25, 2024): oh, my god, it's terrible.
GiteaMirror commented 2026-04-12 12:17:17 -05:00
Author
Owner
Copy Link

@AryaFeng commented on GitHub (Mar 25, 2024):

sudo date -s '-2 hours'

At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error

<!-- gh-comment-id:2017560064 --> @AryaFeng commented on GitHub (Mar 25, 2024): > sudo date -s '-2 hours' At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error
GiteaMirror commented 2026-04-12 12:17:17 -05:00
Author
Owner
Copy Link

@thoda-dev commented on GitHub (Mar 25, 2024):

sudo date -s '-2 hours'

At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error

Just remove some more hours, the certificate expired at 7:19 (UTC) this morning.
It will work till you are earlier on your system.

<!-- gh-comment-id:2017567145 --> @thoda-dev commented on GitHub (Mar 25, 2024): > > sudo date -s '-2 hours' > > At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error Just remove some more hours, the certificate expired at 7:19 (UTC) this morning. It will work till you are earlier on your system.
GiteaMirror commented 2026-04-12 12:17:18 -05:00
Author
Owner
Copy Link

@vcredit-azure commented on GitHub (Mar 25, 2024):

the same problem

<!-- gh-comment-id:2017571006 --> @vcredit-azure commented on GitHub (Mar 25, 2024): the same problem
GiteaMirror commented 2026-04-12 12:17:18 -05:00
Author
Owner
Copy Link

@AryaFeng commented on GitHub (Mar 25, 2024):

sudo date -s '-2 hours'

At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error

Just remove some more hours, the certificate expired at 7:19 (UTC) this morning. It will work till you are earlier on your system.

thanks! it is work

<!-- gh-comment-id:2017573211 --> @AryaFeng commented on GitHub (Mar 25, 2024): > > > sudo date -s '-2 hours' > > > > > > At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error > > Just remove some more hours, the certificate expired at 7:19 (UTC) this morning. It will work till you are earlier on your system. thanks! it is work
GiteaMirror commented 2026-04-12 12:17:19 -05:00
Author
Owner
Copy Link

@gillbates commented on GitHub (Mar 25, 2024):

same issue here ...

<!-- gh-comment-id:2017576034 --> @gillbates commented on GitHub (Mar 25, 2024): same issue here ...
GiteaMirror commented 2026-04-12 12:17:19 -05:00
Author
Owner
Copy Link

@MaxTheTurtle0 commented on GitHub (Mar 25, 2024):

same issue here

<!-- gh-comment-id:2017579056 --> @MaxTheTurtle0 commented on GitHub (Mar 25, 2024): same issue here
GiteaMirror commented 2026-04-12 12:17:19 -05:00
Author
Owner
Copy Link

@DevRaeph commented on GitHub (Mar 25, 2024):

no fix yet

<!-- gh-comment-id:2017581937 --> @DevRaeph commented on GitHub (Mar 25, 2024): no fix yet
GiteaMirror commented 2026-04-12 12:17:20 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 25, 2024):

sudo date -s '-2 hours'

At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error

Just remove some more hours, the certificate expired at 7:19 (UTC) this morning. It will work till you are earlier on your system.

thanks! it is work

no it doesn't work

<!-- gh-comment-id:2017587227 --> @ghost commented on GitHub (Mar 25, 2024): > > > > sudo date -s '-2 hours' > > > > > > > > > At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error > > > > > > Just remove some more hours, the certificate expired at 7:19 (UTC) this morning. It will work till you are earlier on your system. > > thanks! it is work no it doesn't work
GiteaMirror commented 2026-04-12 12:17:21 -05:00
Author
Owner
Copy Link

@SangeloDev commented on GitHub (Mar 25, 2024):

@DevRaeph
@XiandanErizo

you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC).
this is a workaround until the system administrators renew the certificate.

<!-- gh-comment-id:2017589777 --> @SangeloDev commented on GitHub (Mar 25, 2024): @DevRaeph @XiandanErizo you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC). this is a workaround until the system administrators renew the certificate.
GiteaMirror commented 2026-04-12 12:17:21 -05:00
Author
Owner
Copy Link

@MaxTheTurtle0 commented on GitHub (Mar 25, 2024):

@DevRaeph @XiandanErizo

you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC). this is a workaround until the system administrators renew the certificate.

I tried that on wsl 2 but it didnt fix it

<!-- gh-comment-id:2017593570 --> @MaxTheTurtle0 commented on GitHub (Mar 25, 2024): > @DevRaeph @XiandanErizo > > you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC). this is a workaround until the system administrators renew the certificate. I tried that on wsl 2 but it didnt fix it
GiteaMirror commented 2026-04-12 12:17:22 -05:00
Author
Owner
Copy Link

@Lase9 commented on GitHub (Mar 25, 2024):

it works on 1:43 am 03/25/2024 (windows)

<!-- gh-comment-id:2017596120 --> @Lase9 commented on GitHub (Mar 25, 2024): it works on 1:43 am 03/25/2024 (windows)
GiteaMirror commented 2026-04-12 12:17:22 -05:00
Author
Owner
Copy Link

@SangeloDev commented on GitHub (Mar 25, 2024):

@DevRaeph @XiandanErizo
you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC). this is a workaround until the system administrators renew the certificate.

I tried that on wsl 2 but it didnt fix it

have you tried setting the windows system clock? in your settings.

<!-- gh-comment-id:2017601279 --> @SangeloDev commented on GitHub (Mar 25, 2024): > > @DevRaeph @XiandanErizo > > you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC). this is a workaround until the system administrators renew the certificate. > > I tried that on wsl 2 but it didnt fix it have you tried setting the windows system clock? in your settings.
GiteaMirror commented 2026-04-12 12:17:23 -05:00
Author
Owner
Copy Link

@AryaFeng commented on GitHub (Mar 25, 2024):

sudo date -s '-2 hours'

At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error

Just remove some more hours, the certificate expired at 7:19 (UTC) this morning. It will work till you are earlier on your system.

thanks! it is work

no it doesn't work

i dont know why you not work, it does work, i change -2 to -10 make sure time early the 7:19 (UTC) 。"sudo date -s '-10 hours'"。 hope for help you

<!-- gh-comment-id:2017627652 --> @AryaFeng commented on GitHub (Mar 25, 2024): > > > > > sudo date -s '-2 hours' > > > > > > > > > > > > At first, it had an effect. However, about halfway through the download, the error was reported again. And then re-execute, still error > > > > > > > > > Just remove some more hours, the certificate expired at 7:19 (UTC) this morning. It will work till you are earlier on your system. > > > > > > thanks! it is work > > no it doesn't work i dont know why you not work, it does work, i change -2 to -10 make sure time early the 7:19 (UTC) 。"sudo date -s '-10 hours'"。 hope for help you
GiteaMirror commented 2026-04-12 12:17:24 -05:00
Author
Owner
Copy Link

@ghzgod commented on GitHub (Mar 25, 2024):

I think the issue is that the registry pulls from ollama.ai and not ollama.com and that is with the latest docker container image

I wonder as a workaround for the future somehow bypassing certificate validation via a CLI flag

<!-- gh-comment-id:2017628022 --> @ghzgod commented on GitHub (Mar 25, 2024): I think the issue is that the registry pulls from ollama.ai and not ollama.com and that is with the latest docker container image I wonder as a workaround for the future somehow bypassing certificate validation via a CLI flag
GiteaMirror commented 2026-04-12 12:17:25 -05:00
Author
Owner
Copy Link

@MaxTheTurtle0 commented on GitHub (Mar 25, 2024):

@DevRaeph @XiandanErizo
you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC). this is a workaround until the system administrators renew the certificate.

I tried that on wsl 2 but it didnt fix it

have you tried setting the windows system clock? in your settings.

was trying that rn and now it works

<!-- gh-comment-id:2017628240 --> @MaxTheTurtle0 commented on GitHub (Mar 25, 2024): > > > @DevRaeph @XiandanErizo > > > you can set back your system clock to trick your system into thinking that the certificate is still valid. the certificate expired at 7:19 (UTC). this is a workaround until the system administrators renew the certificate. > > > > > > I tried that on wsl 2 but it didnt fix it > > have you tried setting the windows system clock? in your settings. was trying that rn and now it works
GiteaMirror commented 2026-04-12 12:17:26 -05:00
Author
Owner
Copy Link

@tevino commented on GitHub (Mar 25, 2024):

Also --insecure is not working:

> ollama pull mistral --insecure
pulling manifest 
Error: pull model manifest: Get "https://registry.ollama.ai:443/v2/library/mistral/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: “ollama.ai” certificate is expired

According to the help, it should be able to ignore the expired certificate:

> ollama pull --help
Pull a model from a registry

Usage:
  ollama pull MODEL [flags]

Flags:
  -h, --help       help for pull
      --insecure   Use an insecure registry

Environment Variables:
      OLLAMA_HOST        The host:port or base URL of the Ollama server (e.g. http://localhost:11434)

Version:

> ollama --version
ollama version is 0.1.29

This issue is getting too many comments, a dedicated issue was submitted for tracking: #3340

<!-- gh-comment-id:2017673901 --> @tevino commented on GitHub (Mar 25, 2024): Also `--insecure` is not working: ```shell > ollama pull mistral --insecure pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai:443/v2/library/mistral/manifests/latest": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: “ollama.ai” certificate is expired ``` According to the help, it should be able to ignore the expired certificate: ```shell > ollama pull --help Pull a model from a registry Usage: ollama pull MODEL [flags] Flags: -h, --help help for pull --insecure Use an insecure registry Environment Variables: OLLAMA_HOST The host:port or base URL of the Ollama server (e.g. http://localhost:11434) ``` Version: ``` > ollama --version ollama version is 0.1.29 ``` --- This issue is getting too many comments, a dedicated issue was submitted for tracking: #3340
GiteaMirror commented 2026-04-12 12:17:27 -05:00
Author
Owner
Copy Link

@Ust-Waylon commented on GitHub (Mar 25, 2024):

Is there a solution other than changing the system time? :-)

<!-- gh-comment-id:2017684818 --> @Ust-Waylon commented on GitHub (Mar 25, 2024): Is there a solution other than changing the system time? :-)
GiteaMirror commented 2026-04-12 12:17:27 -05:00
Author
Owner
Copy Link

@tushgaurav commented on GitHub (Mar 25, 2024):

I don't want to change my system time, is there any other workaround?

<!-- gh-comment-id:2017689430 --> @tushgaurav commented on GitHub (Mar 25, 2024): I don't want to change my system time, is there any other workaround?
GiteaMirror commented 2026-04-12 12:17:28 -05:00
Author
Owner
Copy Link

@thoda-dev commented on GitHub (Mar 25, 2024):

The problem seems solved for me

<!-- gh-comment-id:2017692065 --> @thoda-dev commented on GitHub (Mar 25, 2024): The problem seems solved for me
GiteaMirror commented 2026-04-12 12:17:28 -05:00
Author
Owner
Copy Link

@dadidelux commented on GitHub (Mar 25, 2024):

how to solve it?

<!-- gh-comment-id:2017693194 --> @dadidelux commented on GitHub (Mar 25, 2024): how to solve it?
GiteaMirror commented 2026-04-12 12:17:29 -05:00
Author
Owner
Copy Link

@viniciusfont commented on GitHub (Mar 25, 2024):

I fixed by setting the system clock to 6:36 UTC 25 March 2024

<!-- gh-comment-id:2017694792 --> @viniciusfont commented on GitHub (Mar 25, 2024): I fixed by setting the system clock to 6:36 UTC 25 March 2024
GiteaMirror commented 2026-04-12 12:17:30 -05:00
Author
Owner
Copy Link

@yuancjun commented on GitHub (Mar 25, 2024):

New problems have arisen.
···
ollama run qwen:14b
pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai:443/v2/library/qwen/manifests/14b": stopped after 10 redirects
···

<!-- gh-comment-id:2017700950 --> @yuancjun commented on GitHub (Mar 25, 2024): New problems have arisen. ··· ollama run qwen:14b pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai:443/v2/library/qwen/manifests/14b": stopped after 10 redirects ···
GiteaMirror commented 2026-04-12 12:17:31 -05:00
Author
Owner
Copy Link

@Nathanule commented on GitHub (Mar 25, 2024):

same problem here
ollama pull llama2
pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai:443/v2/library/llama2/manifests/latest": stopped after 10 redirects

<!-- gh-comment-id:2017702328 --> @Nathanule commented on GitHub (Mar 25, 2024): same problem here ollama pull llama2 pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai:443/v2/library/llama2/manifests/latest": stopped after 10 redirects
GiteaMirror commented 2026-04-12 12:17:31 -05:00
Author
Owner
Copy Link

@Kapuzinaa commented on GitHub (Mar 25, 2024):

Certificate seems updated, now i get
pull model manifest: unauthorized

<!-- gh-comment-id:2017725630 --> @Kapuzinaa commented on GitHub (Mar 25, 2024): Certificate seems updated, now i get pull model manifest: unauthorized
GiteaMirror commented 2026-04-12 12:17:32 -05:00
Author
Owner
Copy Link

@meet447 commented on GitHub (Mar 25, 2024):

Certificate seems updated, now i get pull model manifest: unauthorized

facing the same issue

<!-- gh-comment-id:2017742494 --> @meet447 commented on GitHub (Mar 25, 2024): > Certificate seems updated, now i get pull model manifest: unauthorized facing the same issue
GiteaMirror commented 2026-04-12 12:17:32 -05:00
Author
Owner
Copy Link

@Kapuzinaa commented on GitHub (Mar 25, 2024):

updated: now, the following error is displayed.
pull model manifest: 500

<!-- gh-comment-id:2017747003 --> @Kapuzinaa commented on GitHub (Mar 25, 2024): updated: now, the following error is displayed. pull model manifest: 500
GiteaMirror commented 2026-04-12 12:17:33 -05:00
Author
Owner
Copy Link

@cr2007 commented on GitHub (Mar 25, 2024):

Update: I am able to pull the models successfully now.

The issue appears to be resolved now

Pulling Ollama models

Edit: Success

image

<!-- gh-comment-id:2017780299 --> @cr2007 commented on GitHub (Mar 25, 2024): **Update:** I am able to pull the models successfully now. The issue appears to be resolved now ![Pulling Ollama models](https://github.com/ollama/ollama/assets/73425927/f15b5f76-725b-46e4-aa98-ddfceac36ae4) **Edit:** Success ![image](https://github.com/ollama/ollama/assets/73425927/09f23674-14b4-4a3a-a24d-ca3394af3dc0)
GiteaMirror commented 2026-04-12 12:17:33 -05:00
Author
Owner
Copy Link

@mustafa-198 commented on GitHub (Mar 25, 2024):

guys after i changed the time new error apears "pull model manifest: unauthorized" and i solve it simply by restart my computer now it's downloading

<!-- gh-comment-id:2017799454 --> @mustafa-198 commented on GitHub (Mar 25, 2024): guys after i changed the time new error apears "pull model manifest: unauthorized" and i solve it simply by restart my computer now it's downloading
GiteaMirror commented 2026-04-12 12:17:33 -05:00
Author
Owner
Copy Link

@m4r1k commented on GitHub (Mar 25, 2024):

I'm still getting unauthorized

$ ollama pull llava:7b
pulling manifest
Error: pull model manifest: unauthorized
<!-- gh-comment-id:2017800280 --> @m4r1k commented on GitHub (Mar 25, 2024): I'm still getting `unauthorized` ```bash $ ollama pull llava:7b pulling manifest Error: pull model manifest: unauthorized ```
GiteaMirror commented 2026-04-12 12:17:34 -05:00
Author
Owner
Copy Link

@dylan2019 commented on GitHub (Mar 25, 2024):

pulling manifest
Error: pull model manifest: file does not exist

<!-- gh-comment-id:2017802431 --> @dylan2019 commented on GitHub (Mar 25, 2024): pulling manifest Error: pull model manifest: file does not exist
GiteaMirror commented 2026-04-12 12:17:34 -05:00
Author
Owner
Copy Link

@mteletin commented on GitHub (Mar 25, 2024):

Guys, it's working. Certificate issue was fixed. Whatever other issues you have must be something specific to your ISP or caches or other things. I'm just pulling some models for test right now just fine (see previous morning and now).
image

<!-- gh-comment-id:2017807152 --> @mteletin commented on GitHub (Mar 25, 2024): Guys, it's working. Certificate issue was fixed. Whatever other issues you have must be something specific to your ISP or caches or other things. I'm just pulling some models for test right now just fine (see previous morning and now). ![image](https://github.com/ollama/ollama/assets/10918175/216b8dbd-9544-44d9-b33c-193f2dd0338e)
GiteaMirror commented 2026-04-12 12:17:35 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Mar 25, 2024):

Hi everyone, this should be fixed now. I'll leave this issue open for a bit longer and provide a longer explanation on what happened here soon (we don't take availability issues like this lightly). Please let me know if you're seeing any more issues!

<!-- gh-comment-id:2017813131 --> @jmorganca commented on GitHub (Mar 25, 2024): Hi everyone, this should be fixed now. I'll leave this issue open for a bit longer and provide a longer explanation on what happened here soon (we don't take availability issues like this lightly). Please let me know if you're seeing any more issues!
GiteaMirror commented 2026-04-12 12:17:36 -05:00
Author
Owner
Copy Link

@taozhiyuai commented on GitHub (Mar 25, 2024):

sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours'

To turn your clock back on Ubuntu

but how to fix this issue? :(

<!-- gh-comment-id:2018162383 --> @taozhiyuai commented on GitHub (Mar 25, 2024): > sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours' > > To turn your clock back on Ubuntu but how to fix this issue? :(
GiteaMirror commented 2026-04-12 12:17:36 -05:00
Author
Owner
Copy Link

@ipty commented on GitHub (Mar 25, 2024):

Hi there,
is there anything i need to do - i still get the mentioned ssl error.
This it what it looks like if i put the download link in a browser:
ssl

Kind regards
Erik

<!-- gh-comment-id:2018360825 --> @ipty commented on GitHub (Mar 25, 2024): Hi there, is there anything i need to do - i still get the mentioned ssl error. This it what it looks like if i put the download link in a browser: ![ssl](https://github.com/ollama/ollama/assets/9331981/d3b5846a-8cae-4815-9fc6-94bde5a1d365) Kind regards Erik
GiteaMirror commented 2026-04-12 12:17:37 -05:00
Author
Owner
Copy Link

@MoonRide303 commented on GitHub (Mar 25, 2024):

It works fine for me, now (ollama run correctly pulls models). Folks who still experience the problem - try to clear cache, or restart the machine.

<!-- gh-comment-id:2018389000 --> @MoonRide303 commented on GitHub (Mar 25, 2024): It works fine for me, now (ollama run correctly pulls models). Folks who still experience the problem - try to clear cache, or restart the machine.
GiteaMirror commented 2026-04-12 12:17:38 -05:00
Author
Owner
Copy Link

@Jagrmi-C commented on GitHub (Mar 25, 2024):

Fixed, I'm waiting 8 hours without efforts and ran again pull

<!-- gh-comment-id:2018485696 --> @Jagrmi-C commented on GitHub (Mar 25, 2024): Fixed, I'm waiting 8 hours without efforts and ran again pull
GiteaMirror commented 2026-04-12 12:17:38 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 10, 2024):

kill ollama serve and restart serve multi times, then run again

<!-- gh-comment-id:2047291214 --> @ghost commented on GitHub (Apr 10, 2024): kill ollama serve and restart serve multi times, then run again
GiteaMirror commented 2026-04-12 12:17:39 -05:00
Author
Owner
Copy Link

@Symbolk commented on GitHub (May 30, 2024):

sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours'

To turn your clock back on Ubuntu

Tried but with no luck, I am changing inside a Docker, not the ollama one, the Ubuntu 22.04

<!-- gh-comment-id:2139017056 --> @Symbolk commented on GitHub (May 30, 2024): > sudo systemctl stop systemd-timesyncd sudo date -s '-2 hours' > > To turn your clock back on Ubuntu Tried but with no luck, I am changing inside a Docker, not the ollama one, the Ubuntu 22.04
GiteaMirror commented 2026-04-12 12:17:39 -05:00
Author
Owner
Copy Link

@VeluAtHPE commented on GitHub (Jun 15, 2024):

how to resolve this issue:

(base) root@toolsvm:/var/www/html/playground/ollama# ollama pull dolphin-llama3 --insecure
pulling manifest
Error: Head "ea025c107c/data!F(MISSING)20240615%!F(MISSING)auto%!F(MISSING)s3%!F(MISSING)aws4_request&X-Amz-Date=20240615T114017Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=66ecd8cd6dfd1c992ba8f5e6bbd27e51f56663bcd8c7ffdf7ecb9f1ed7387b3b": tls: failed to verify certificate: x509: certificate signed by unknown authority
(base) root@toolsvm:/var/www/html/playground/ollama# ollama pull llava:7b
pulling manifest
Error: Head "170370233d/data!F(MISSING)20240615%!F(MISSING)auto%!F(MISSING)s3%!F(MISSING)aws4_request&X-Amz-Date=20240615T114123Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=2714941a56fd1fd1fe617dcff5223ca9bdd6cdd91ddc9516312ed92cb872cff7": tls: failed to verify certificate: x509: certificate signed by unknown authority
(base) root@toolsvm:/var/www/html/playground/ollama#

<!-- gh-comment-id:2169381686 --> @VeluAtHPE commented on GitHub (Jun 15, 2024): how to resolve this issue: (base) root@toolsvm:/var/www/html/playground/ollama# ollama pull dolphin-llama3 --insecure pulling manifest Error: Head "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/ea/ea025c107c1c3e5a87380b25e205db3b19a4d2ed56f1954f531573a963621580/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%!F(MISSING)20240615%!F(MISSING)auto%!F(MISSING)s3%!F(MISSING)aws4_request&X-Amz-Date=20240615T114017Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=66ecd8cd6dfd1c992ba8f5e6bbd27e51f56663bcd8c7ffdf7ecb9f1ed7387b3b": tls: failed to verify certificate: x509: certificate signed by unknown authority (base) root@toolsvm:/var/www/html/playground/ollama# ollama pull llava:7b pulling manifest Error: Head "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/17/170370233dd5c5415250a2ecd5c71586352850729062ccef1496385647293868/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%!F(MISSING)20240615%!F(MISSING)auto%!F(MISSING)s3%!F(MISSING)aws4_request&X-Amz-Date=20240615T114123Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=2714941a56fd1fd1fe617dcff5223ca9bdd6cdd91ddc9516312ed92cb872cff7": tls: failed to verify certificate: x509: certificate signed by unknown authority (base) root@toolsvm:/var/www/html/playground/ollama#
GiteaMirror commented 2026-04-12 12:17:40 -05:00
Author
Owner
Copy Link

@tagwato commented on GitHub (Jun 27, 2024):

Hi everyone, this should be fixed now. I'll leave this issue open for a bit longer and provide a longer explanation on what happened here soon (we don't take availability issues like this lightly). Please let me know if you're seeing any more issues!

Hi, @jmorganca.
The problem persists.
I managed to install ollama version 0.1.47 with a workaround (https://github.com/ollama/ollama/issues/5330).
But, subsequent ollama pull commands fail with "tls: failed to verify certificate: x509: certificate signed by unknown authority".

And the --insecure option has no effect (e.g: ollama pull phi3 --insecure).

== EDITED ==
The 2 commands below solved the problem ("tls: failed"). Now the command "ollama pull" works fine.

  sudo update-ca-certificates -v
  sudo dpkg-reconfigure ca-certificates

Note: maybe just the last command would have been enough, but I ran the 2 in sequence, when testing various solutions.
Looks like something was faulty with my Ubuntu-24.04 (which was a fresh install).

<!-- gh-comment-id:2195240952 --> @tagwato commented on GitHub (Jun 27, 2024): > Hi everyone, this should be fixed now. I'll leave this issue open for a bit longer and provide a longer explanation on what happened here soon (we don't take availability issues like this lightly). Please let me know if you're seeing any more issues! Hi, @jmorganca. The problem persists. I managed to install ollama version 0.1.47 with a workaround (https://github.com/ollama/ollama/issues/5330). But, subsequent ollama pull commands fail with "tls: failed to verify certificate: x509: certificate signed by unknown authority". And the --insecure option has no effect (e.g: ollama pull phi3 --insecure). == EDITED == The 2 commands below solved the problem ("tls: failed"). Now the command "ollama pull" works fine. ``` sudo update-ca-certificates -v sudo dpkg-reconfigure ca-certificates ``` Note: maybe just the last command would have been enough, but I ran the 2 in sequence, when testing various solutions. Looks like something was faulty with my Ubuntu-24.04 (which was a fresh install).
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#2054
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?