# Is the repo broken?

**URL:** <https://discuss.elastic.co/t/is-the-repo-broken/355043>\
**Category:** Elasticsearch\
**Created:** [March 8, 2024, 3:12pm UTC](https://discuss.elastic.co/t/is-the-repo-broken/355043 "2024-03-08T15:12:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [March 8, 2024, 3:12pm UTC](https://discuss.elastic.co/t/is-the-repo-broken/355043/1 "2024-03-08T15:12:03Z")

</div>

On an existing system running 8.12, I'm getting this error:

dnf --enablerepo=elasticsearch update  
Elasticsearch repository for 8.x packages 0.0 B/s | 0 B 00:00  
Errors during downloading metadata for repository 'elasticsearch':

- Curl error (60): SSL peer certificate or SSH remote key was not OK for [https://artifacts.elastic.co/packages/8.x/yum/repodata/repomd.xml](https://artifacts.elastic.co/packages/8.x/yum/repodata/repomd.xml) [SSL certificate problem: certificate is not yet valid]  
Error: Failed to download metadata for repo 'elasticsearch': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Is their repo broken again?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 8, 2024, 9:03pm UTC](https://discuss.elastic.co/t/is-the-repo-broken/355043/2 "2024-03-08T21:03:38Z")

</div>

Are you sure your system clock is accurate? `SSL certificate problem: certificate is not yet valid` implies that it thinks the certificate validity starts in the future, but it definitely doesn't:

```auto
$ openssl s_client -showcerts -host artifacts.elastic.co -port 443 | openssl x509 -noout -text | grep 'Not Before'
Warning: Reading certificate from stdin since no -in or -new option is given
depth=2 C=US, O=Internet Security Research Group, CN=ISRG Root X1
verify return:1
depth=1 C=US, O=Let's Encrypt, CN=R3
verify return:1
depth=0 CN=elastic.co
verify return:1
            Not Before: Feb 23 17:52:22 2024 GMT

```

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [March 8, 2024, 9:29pm UTC](https://discuss.elastic.co/t/is-the-repo-broken/355043/3 "2024-03-08T21:29:25Z")

</div>

Odd, it was a VM, the host time is correct, but the guest was many weeks behind. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 5, 2024, 9:30pm UTC](https://discuss.elastic.co/t/is-the-repo-broken/355043/4 "2024-04-05T21:30:20Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.