Kibana 3 & Elasticsearch 1.4.0 beta 1

[rashidkpc]

When using older versions of Kibana 3 you may receive an error that it can not connect to Elasticsearch 1.4.0 beta 1. This is due to security settings changes made in Elasticsearch 1.4.0 beta 1. Unfortunately due to browser behavior it is not possible for Kibana to differentiate between a down instance of Elasticsearch, and one with overly restrictive CORS settings.

To resolve this issue you will need to set http.cors.allow-origin in your elasticsearch.yml 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.

You will also need http.cors.enabled: true

[pcreux]

Thanks for the heads up!

[tomrade]

Feel like im missing something, however i cannot seem to get this working on ES 1.4.1 and Kibana 3.1.2. My test machine is a all in one vm, I used the debian package for es install, I couldnt find the options in my /etc/elasticsearch/elasticsearch.yml file, so added to the following to the end

http.cors.enabled: true
http.cors.allow-origin: "http://192.168.226.128"

I also tried "localhost", "127.0.0.1" and "hostname" , however I seemed to still get this error

[tomrade]

Sods law, I fixed it by using the following
http.cors.allow-origin: "/.*/"
http.cors.enabled: true

which is less than ideal, to let any, could have been the order will try some other options

[tomrade]

After playing a bit, the first fix doesnt work, :S, May try rebuilding the vm

[tomrade]

Ive reinstalled now with no issues, might have been a corrupt deb hopefully