Kibana can't connect to package directory

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


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.

Welcome to our community! :smiley:

What do the Kibana logs show?

There is nothing in the logs about any connection failures.

{"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.

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.

{"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?

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

Thanks,

Jared

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