In order to install Integrations, the Fleet app needs to connect to an external service called the Elastic Package Registry. For this to work, the Kibana server must be able to connect to https://epr.elastic.co on port 443
But what if its a cluster thats not connected to the Internet?
Hi @teej - I am afraid that this is a current limitation in the product and it is documented here:
Requires internet access for Kibana to download integration packages
Our development team is looking into this and you can subscribe to the related Github issue for further updates.
There is actually a workaround proposed by our developer in this comment but this approach should only be used for development and it is not supported.
Hi Ropc
Yes, that is very helpful. Thank you very much. I look forward to seeing how they fix that. It sometimes feels that Elastic is trying to be too many things to too many people.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.