Error connecting to package registry - No Internet connection

Elastic Stack Kibana
,
1

Hey,
I searched very long, is there a chance to prevent those warning for not able to connecting to package registry or if its clicked in Kibana I am getting errors in my cmd. The Server does not have internet access, so that is why I am getting these.

[2022-03-04T13:19:44.949+01:00][INFO ][status] Kibana is now degraded
[2022-03-04T13:19:47.691+01:00][INFO ][status] Kibana is now available (was degraded)
[2022-03-04T13:21:03.536+01:00][WARN ][plugins.fleet] Failed installing package [system] due to error: [RegistryConnectionError: Error connecting to package registry: request to https://epr.elastic.co/search?package=system&experimental=true&kibana.version=8.0.1 failed, reason: getaddrinfo EAI_AGAIN epr.elastic.co]
[2022-03-04T13:21:03.540+01:00][WARN ][plugins.fleet] Failed installing package [elastic_agent] due to error: [RegistryConnectionError: Error connecting to package registry: request to https://epr.elastic.co/search?package=elastic_agent&experimental=true&kibana.version=8.0.1 failed, reason: getaddrinfo EAI_AGAIN epr.elastic.co]
[2022-03-04T13:21:03.541+01:00][WARN ][plugins.fleet] Failed installing package [fleet_server] due to error: [RegistryConnectionError: Error connecting to package registry: request to https://epr.elastic.co/search?package=fleet_server&experimental=true&kibana.version=8.0.1 failed, reason: getaddrinfo EAI_AGAIN epr.elastic.co]
[2022-03-04T13:21:03.573+01:00][INFO ][plugins.fleet] Encountered non fatal errors during Fleet setup
[2022-03-04T13:21:03.577+01:00][INFO ][plugins.fleet] {"name":"RegistryConnectionError","message":"Error connecting to package registry: request to https://epr.elastic.co/search?package=system&experimental=true&kibana.version=8.0.1 failed, reason: getaddrinfo EAI_AGAIN epr.elastic.co"}
[2022-03-04T13:21:03.578+01:00][INFO ][plugins.fleet] {"name":"RegistryConnectionError","message":"Error connecting to package registry: request to https://epr.elastic.co/search?package=elastic_agent&experimental=true&kibana.version=8.0.1 failed, reason: getaddrinfo EAI_AGAIN epr.elastic.co"}
[2022-03-04T13:21:03.579+01:00][INFO ][plugins.fleet] {"name":"RegistryConnectionError","message":"Error connecting to package registry: request to https://epr.elastic.co/search?package=fleet_server&experimental=true&kibana.version=8.0.1 failed, reason: getaddrinfo EAI_AGAIN epr.elastic.co"}
[2022-03-04T13:21:03.580+01:00][INFO ][plugins.fleet] Fleet setup completed
[2022-03-04T13:21:03.583+01:00][INFO ][plugins.securitySolution] Dependent plugin setup complete - Starting ManifestTask
[2022-03-04T14:00:40.494+01:00][INFO ][plugins.securitySolution.endpoint:metadata-check-transforms-task:0.0.1] no endpoint metadata transforms found

Thank you.

2

If you'd like to use Fleet, you can configure an on-prem registry in your offline environment see: Air-gapped environments | Fleet and Elastic Agent Guide [8.0] | Elastic

Alternatively, you can disable logging for Fleet to avoid this by adding this to your kibana.yml file:

logging:
  loggers:
    - name: plugins.fleet
      level: off
3

Thanks.

4

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