i installed Karaf + Decanter according to this:
with a Java8 JRE on Windows7 and another installation on Linux Suse enterprise with same result.
The collectors, appenders are running and i can access Kibana with a locally started Browswer with no problem showing dashboards etc.
Elasticsearch-Head and the cluster is available by non local Ip also.
The first Kibana page is shown, then an error page comes up saying it cannot connect to ES.
Error: Unknown error while connecting to Elasticsearch ErrorAbstract@http://:8181/kibana/index.js?_b=7562:84021:19
NoConnections@http://:8181/kibana/index.js?_b=7562:84044:3 sendReqWithConnection@http://:8181/kibana/index.js?_b=7562:85302:15 next@http://:8181/kibana/index.js?_b=7562:83802:1 </process.nextTick</<@http://<external IP>:8181/kibana/index.js?_b=7562:52880:21
The Kibana forum talks about Proxy-Settings but these are off already.
in elasticsearch.yml i tried network.host with localhost, 127.0.0.1 and external ip
i see in file "config" of the kibana bundle the ES access to localhost:9200 which is working with ES-Head.
How do i open the Kibana dashboards to other Ip addresses?
Thanks in advance,
RE: Decanter / Accessing Kibana with an external IP
This post has NOT been accepted by the mailing list yet.
I have the same issue.
I uninstall kibana bundle and installed kibana/3.1.1
now error message is :
Error Could not contact Elasticsearch at http://IP_address:9200. Please ensure that Elasticsearch is reachable from your system.
Possibility #1: Your elasticsearch server is down or unreachable
This can be caused by a network outage, or a failure of the Elasticsearch process. If you have recently run a query that required a terms facet to be executed it is possible the process has run out of memory and stopped. Be sure to check your Elasticsearch logs for any sign of memory pressure.
Possibility #2: You are running Elasticsearch 1.4 or higher
Elasticsearch 1.4 ships with a security setting that prevents Kibana from connecting. You will need to set the following in your elasticsearch.yml:
1. http.cors.enabled: true
2. http.cors.allow-origin to the correct protocol, hostname, and port (if not 80) that your access Kibana from. Note that if you are running Kibana in a sub-url, you should exclude the sub-url path and only include the protocol, hostname and port. For example, http://mycompany.com:8080, not http://mycompany.com:8080/kibana.
Click back, or the home button, when you have resolved the connection issue