# Bad cert when accessing the General registry

**URL:** <https://discourse.julialang.org/t/bad-cert-when-accessing-the-general-registry/112738>\
**Category:** Package Management\
**Created:** [April 9, 2024, 3:51pm UTC](https://discourse.julialang.org/t/bad-cert-when-accessing-the-general-registry/112738 "2024-04-09T15:51:53Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [April 10, 2024, 8:53pm UTC](https://discourse.julialang.org/t/bad-cert-when-accessing-the-general-registry/112738/13 "2024-04-10T20:53:52Z")

</div>

The root certificate for [https://storage.julialang.net](https://storage.julialang.net) (which [https://us-east.pkg.julialang.org](https://us-east.pkg.julialang.org) redirects to) is _ISRG Root X2_ and the root certificate for [https://us-west.pkg.julialang.org](https://us-west.pkg.julialang.org) (and [https://us-east.pkg.julialang.org](https://us-east.pkg.julialang.org) too) is _ISRG Root X1_. Is it possible that the former isn’t trusted (yet) by your system?

See [https://letsencrypt.org/certificates/](https://letsencrypt.org/certificates/) for some more details. In particular they list a couple of test pages where you can verify the theory above. For example, [https://valid-isrgrootx1.letsencrypt.org/](https://valid-isrgrootx1.letsencrypt.org/) present a valid certificate signed by ISRG Root X1 and [https://valid-isrgrootx2.letsencrypt.org/](https://valid-isrgrootx2.letsencrypt.org/) a valid cert signed by ISRG Root X2.

---

_[View the full topic](https://discourse.julialang.org/t/bad-cert-when-accessing-the-general-registry/112738)._