Apologies for resurrecting an old thread, just wanted to highlight that this worked for me. I was fronting K3 with Apache, tried enabling all the options within elasticsearch.yml, then also in Apache and finally, in desperation, with ngnix but enabling just that one line as Drew says works.
On Monday, 10 November 2014 05:01:18 UTC-8, Drew Town wrote: > > I got it to work by adding > > http.cors.enabled: true > > and leaving the allow-origin out and the allow-credentials out. > allow-origin seems to default to anything if it is not present. cors is > disabled by default. > > Drew > > On Monday, November 10, 2014 4:16:32 AM UTC-6, Prakash Dutta wrote: >> >> Hi >> >> I am also facing same issues. Read some where that elasticsearch in not >> running but when I tried with the url : http://localhost:9200, it is >> showing the below message >> >> { >> "status" : 200, >> "name" : "Tzabaoth", >> "cluster_name" : "elasticsearch", >> "version" : { >> "number" : "1.4.0", >> "build_hash" : "bc94bd81298f81c656893ab1ddddd30a99356066", >> "build_timestamp" : "2014-11-05T14:26:12Z", >> "build_snapshot" : false, >> "lucene_version" : "4.10.2" >> }, >> "tagline" : "You Know, for Search" >> } >> >> it means, elasticsearch is running. Added below two lines in >> elasticsearch.yml >> >> http.cors.allow-origin: "/.*/" >> http.cors.allow-credentials: true >> >> After doing all this steps also, facing same issues. >> >> Please suggest me the way to solve this. >> >> Thanks in advance to all. >> >> Regards >> Prakash >> >> >> >> >> >> >> On Thursday, October 30, 2014 2:51:12 AM UTC+5:30, versne...@gmail.com >> wrote: >>> >>> Hello there, >>> >>> I keep getting this message when i start Kibana. But if i go look on my >>> server i see that elasticsearch is running perfectly >>> >>> *root@server:~# service elasticsearch status* >>> * * elasticsearch is running* >>> >>> >>> >>> >>> >>> *Connection FailedPossibility #1: Your elasticsearch server is down or >>> unreachableThis 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 >>> higherElasticsearch 1.4 ships with a security setting that prevents Kibana >>> from connecting. 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 >>> <http://mycompany.com:8080>, not http://mycompany.com:8080/kibana >>> <http://mycompany.com:8080/kibana>.Click back, or the home button, when you >>> have resolved the connection issue* >>> >>> Plz some help >>> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/faf60ffa-153c-4c04-bd87-fd68595560ce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
