# Kibana can't connect to package directory

**URL:** <https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919>\
**Category:** Kibana\
**Created:** [October 18, 2022, 4:31pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919 "2022-10-18T16:31:14Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpedroza2k20](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jpedroza2k20](https://discuss.elastic.co/u/jpedroza2k20)\
**Post date:** [October 18, 2022, 4:31pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/1 "2022-10-18T16:31:14Z")

</div>

I have seen this same issue on the forums twice (English and French) and there is no resolution listed. I get the following error:

 ![Kibana error](https://us1.discourse-cdn.com/elastic/original/3X/9/1/91974d7e80713a940d569e02ef9a1d58a7143096.png)  
I can access the URL from the server in question (self hosted stack) and there is no proxy in between, and I see nothing in the Kibana log regarding a failed connection. I am sure I failed to configure something, but can't find out what I need to fix. Any help is appreciated.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 19, 2022, 10:20pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/2 "2022-10-19T22:20:49Z")

</div>

Welcome to our community! 😃

What do the Kibana logs show?

---

<div class="post-metadata">

**Author:** ![jpedroza2k20](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jpedroza2k20](https://discuss.elastic.co/u/jpedroza2k20)\
**Post date:** [October 20, 2022, 2:21pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/3 "2022-10-20T14:21:49Z")

</div>

There is nothing in the logs about any connection failures.

```auto
{"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.4.0"},"@timestamp":"2022-10-20T07:48:32.677-06:00","message":"Task ML:saved-objects-sync-task: No ML saved objects in need of synchronization","log":{"level":"INFO","logger":"plugins.ml"},"process":{"pid":75271},"trace":{"id":"04dbca5be63806a85b67f8766a46cbce"},"transaction":{"id":"a0e1cc766fb7848b"}}

```

That is repeated over and over about once an hour.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [October 20, 2022, 2:35pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/4 "2022-10-20T14:35:29Z")

</div>

I have the same issue from time to time and what I do is refresh until it works, but it is really annoying.

I also have no proxy between my Kibana and the package registry endpoint, it seems that there is some issue in Elastic side.

Sometimes I have a timeout in Kibana Logs, other times I have a 502 Bad Gateway error.

Those are the more recent errors.

```auto
{"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.4.0"},"@timestamp":"2022-10-17T20:39:54.145+00:00","message":"Failed to fetch latest version of ti_util from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=ti_util&experimental=true&kibana.version=8.4.2 failed, reason: connect ETIMEDOUT 34.120.127.130:443","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1028},"trace":{"id":"c3d41dbbd916c33a305d6c4d8e5213af"},"transaction":{"id":"384ecc583afaf0d0"}}
{"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.4.0"},"@timestamp":"2022-10-18T20:51:23.609+00:00","message":"'502 Bad Gateway' error response from package registry at https://epr.elastic.co/package/zoom/1.5.0/img/zoom_blue.svg","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1028},"trace":{"id":"07e30f769fc698dc6267c367ec6dea0e"},"transaction":{"id":"8696acd22120787c"}}
{"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.4.0"},"@timestamp":"2022-10-18T23:52:39.671+00:00","message":"Failed to fetch latest version of ti_abusech from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=ti_abusech&experimental=true&kibana.version=8.4.2 failed, reason: connect ETIMEDOUT 34.120.127.130:443","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1709},"trace":{"id":"9ad5885527f2837667b5e3a29c25af39"},"transaction":{"id":"c6d86b39ed82fbc0"}}
{"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.4.0"},"@timestamp":"2022-10-19T02:23:35.927+00:00","message":"Failed to fetch latest version of aws from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=aws&experimental=true&kibana.version=8.4.2 failed, reason: connect ETIMEDOUT 34.120.127.130:443","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1709},"trace":{"id":"fe99a21b61253a0243676e8568878153"},"transaction":{"id":"8420ba6ec05ca9be"}}

```

Should I open an issue? In which repo?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 21, 2022, 1:43am UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/5 "2022-10-21T01:43:14Z")

</div>

> **[GitHub - elastic/package-registry: Elastic Package Registry (EPR)](https://github.com/elastic/package-registry)**
>
> Elastic Package Registry (EPR). Contribute to elastic/package-registry development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![jpedroza2k20](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jpedroza2k20](https://discuss.elastic.co/u/jpedroza2k20)\
**Post date:** [October 21, 2022, 1:53pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/6 "2022-10-21T13:53:01Z")

</div>

Is it possible to just install these on the command line and deal with the issue that way?

Thanks,

Jared

---

<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:** [November 18, 2022, 4:11am UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/7 "2022-11-18T04:11:24Z")

</div>



---

<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:** [December 16, 2022, 12:57am UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/8 "2022-12-16T00:57:18Z")

</div>



---

<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:** [January 12, 2023, 9:12pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/9 "2023-01-12T21:12:30Z")

</div>



---

<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:** [February 9, 2023, 9:12pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/10 "2023-02-09T21:12:44Z")

</div>

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