# Intégration server fleet

**URL:** <https://discuss.elastic.co/t/integration-server-fleet/378296>\
**Category:** Endpoint Security\
**Tags:** fleet\
**Created:** [May 19, 2025, 11:50am UTC](https://discuss.elastic.co/t/integration-server-fleet/378296 "2025-05-19T11:50:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 27, 2025, 3:36pm UTC](https://discuss.elastic.co/t/integration-server-fleet/378296/2 "2025-05-27T15:36:44Z")

</div>

> [@rezgui](#):
>
> Elastic Package Registry

Hello @rezgui

Your issue seems similar to that one, [Kibana fleet - Error connecting to package registry](https://discuss.elastic.co/t/kibana-fleet-error-connecting-to-package-registry/257956)  
Providing the package registry cert when running kibana in the `NODE_EXTRA_CA_CERTS` environment variable may help to solve your issue.

---

_[View the full topic](https://discuss.elastic.co/t/integration-server-fleet/378296)._
