# Certs are out of date

**URL:** https://discuss.ipfs.tech/t/certs-are-out-of-date/4131
**Category:** Help
**Tags:** js-ipfs
**Created:** [October 24, 2018, 12:17pm UTC](https://discuss.ipfs.tech/t/certs-are-out-of-date/4131 "2018-10-24T12:17:36Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![vongohren](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/vongohren/32/2393_2.png) [@vongohren](https://discuss.ipfs.tech/u/vongohren)
#### Post date: [October 24, 2018, 12:17pm UTC](https://discuss.ipfs.tech/t/certs-are-out-of-date/4131/1 "2018-10-24T12:17:37Z")

</div>

It seems like the browser version of syncing has out of date certs  
[https://node0.preload.ipfs.io/](https://node0.preload.ipfs.io/)

This is return invalid https. This make connecting to ipfs not possible

---

<div class="post-metadata">

### Author: ![stebalien](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/stebalien/32/156_2.png) [@stebalien](https://discuss.ipfs.tech/u/stebalien)
#### Post date: [October 24, 2018, 1:36pm UTC](https://discuss.ipfs.tech/t/certs-are-out-of-date/4131/2 "2018-10-24T13:36:29Z")

</div>

Reported: [https://github.com/ipfs/infrastructure/issues/443](https://github.com/ipfs/infrastructure/issues/443). The infra team will handle this ASAP.

---

<div class="post-metadata">

### Author: ![kyledrake](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/kyledrake/32/2390_2.png) [@kyledrake](https://discuss.ipfs.tech/u/kyledrake)
#### Post date: [October 25, 2018, 3:13am UTC](https://discuss.ipfs.tech/t/certs-are-out-of-date/4131/3 "2018-10-25T03:13:05Z")

</div>

This issue should be resolved, but let me know if you’re still having issues with it.