IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Set the proxy URL of the Elastic Package Registry
editSet the proxy URL of the Elastic Package Registry
editFleet might be unable to access the Elastic Package Registry because Kibana is behind a proxy server.
Also your organization might have network traffic restrictions that prevent Kibana
from reaching the public Elastic Package Registry (EPR) endpoints, like
epr.elastic.co, to download package metadata and
content. You can route traffic to the public endpoint of EPR through a network
gateway, then configure proxy settings in the
Kibana configuration file, kibana.yml. For
example:
xpack.fleet.registryProxyUrl: your-nat-gateway.corp.net