Today I have upgraded 3 machines development ES cluster from 1.3.2 to 4.0.0
BETA1. As far as I can tell it went successfully - cluster state is green,
it responds to commands and all the data seems intact. New data keep coming
in and indexing.
BUT somehow I completely lost Kibana cooperation! I have Kibana 3.1.1
running on port 80 in IIS and when I try access it as usual
(http://tukc-devlog-1) I get back that new for 3.1.1 "Connection Failed"
screen and whatever I do it does not connect!
It says: "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." ES, Kibana and browser are all on the same
box, so I went to elasticsearch-1.4.0.Beta1\config\elasticsearch.yml and
added this line:
http.cors.allow-origin: "http://TUKC-DEVLOG-1"
Restarted the node. Still same Connection Failed screen is all I get.
Out of curiosity I tried Kibana 4.0.0 Beta1 too and the result was also
negative, but even more confusing - "This version of Kibana requires at
least Elasticsearch 1.4.0.Beta1" But that's exactly what I have running!
I'm temporary out of ideas how to make either of them work.
Any advice how to troubleshoot those two separate and probably different
issues with Kibana?
Thank you!
Konstantin
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3fc58d4a-0b6a-4548-bc7a-e162f289d398%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.