# Kibana fleet - Error connecting to package registry

**URL:** <https://discuss.elastic.co/t/kibana-fleet-error-connecting-to-package-registry/257956>\
**Category:** Kibana\
**Tags:** fleet\
**Created:** [December 8, 2020, 8:56am UTC](https://discuss.elastic.co/t/kibana-fleet-error-connecting-to-package-registry/257956 "2020-12-08T08:56:14Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![nchaulet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nchaulet/32/77896_2.png) [@nchaulet](https://discuss.elastic.co/u/nchaulet)\
**Post date:** [December 9, 2020, 7:09pm UTC](https://discuss.elastic.co/t/kibana-fleet-error-connecting-to-package-registry/257956/7 "2020-12-09T19:09:58Z")

</div>

I guess we are missing some options while doing our call from Kibana to EPR.  
Can you try to add your company certificate authority to node, it's possible to do so by specifying the environment variable NODE\_EXTRA\_CA\_CERTS while running Kibana?

---

_[View the full topic](https://discuss.elastic.co/t/kibana-fleet-error-connecting-to-package-registry/257956)._