Got a similiar issue with the beta, getting the  "*This version of Kibana 
requires at least Elasticsearch 1.4.0.Beta1*". 
I've got kibana and elasticsearch(ie. http://localhost:9200)  running on 
the same box
It seems from what I can see in the logs, that Kibana is pushing the 
requests to http://localhost:9200/elasticsearch/ instead of just 
http://localhost:9200/

{"@timestamp":"2014-10-09T14:10:01+02:00","status":"200","level":"INFO","name":"Kibana","request_method":"HEAD","request":"/elasticsearch/","path":"/elasticsearch/","query_string":"","remote_addr":"172.16.5.90","remote_user":null,"http_version":"HTTP/1.1","content_length":"-","response_time":32,"message":"HEAD
 
/elasticsearch/ 200 32ms - -"}

Maybe somebody left something hardcoded in the beta, don't know. Just my 2 
cents :)


On Thursday, 9 October 2014 04:05:04 UTC+2, Konstantin Erman wrote:
>
> Well, at least I got my Kibana 3.1.1 back! The trick was 
> "http.cors.enabled: true" setting in elasticsearch.yml which I found about 
> by reading the source code as it is not mentioned on that Kibana 3.1.1 
> "Connection Failed" screen, where it would be extremely useful. 
>
> Kibana 4 Beta still wants ES version which I already have, but... you 
> cannot have it all, can you?
>
> Konstantin
> On Wednesday, October 8, 2014 5:54:59 PM UTC-7, Konstantin Erman wrote:
>>
>> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/3ca43818-a154-4c20-aee8-4bd42de69814%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to