### Author:  [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)
#### Post date: [December 3, 2014, 11:51pm UTC](https://discuss.elastic.co/t/this-version-of-kibana-requires-at-least-elasticsearch-1-4-0-beta1-but-using-1-4-1/21055/6 "2014-12-03T23:51:28Z")
>
>
> When using older versions of Kibana 3 you may receive an error that it can not c…onnect 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\`
--
Itamar Syn-Hershko
[http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko)
Freelance Developer & Consultant
Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/)
On Thu, Dec 4, 2014 at 1:49 AM, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)
wrote:
> I am kibana 4.0.0-BETA2
>
> On Wednesday, December 3, 2014 7:30:03 PM UTC+8, Mark Walkom wrote:
>
> > What version of Kibana?
> >
> > On 3 December 2014 at 21:48, David Montgomery [davidmo...@gmail.com](mailto:davidmo...@gmail.com)
> > wrote:
> >
> > > Hi,
> > >
> > > This version of Kibana requires at least Elasticsearch 1.4.0.Beta1
> > >
> > > SetupError@[http://monitor-development-east.test.com](http://monitor-development-east.test.com):
> > > 5601/index.js?\_b=3998:42905:51
> > > checkEsVersion/\<@[http://monitor-development-east.test](http://monitor-development-east.test).
> > > com:5601/index.js?\_b=3998:43091:14
> > > qFactory/defer/deferred.promise.then/wrappedCallback@h
> > > ttp://monitor-development-east.test.com:5601/index.js?\_b=3998:20764:15
> > > qFactory/ref/\<.then/\<@[http://monitor-development-east.test](http://monitor-development-east.test).
> > > com:5601/index.js?\_b=3998:20850:11
> > > $RootScopeProvider/this.$get\ > > [monitor-development-east.test.com:5601/index.js?\_b=3998:21893:9](http://monitor-development-east.test.com:5601/index.js?_b=3998:21893:9)
> > > $RootScopeProvider/this.$get\ > > /monitor-development-east.test.com:5601/index.js?\_b=3998:21705:15
> > > $RootScopeProvider/this.$get\ > > [monitor-development-east.test.com:5601/index.js?\_b=3998:21997:13](http://monitor-development-east.test.com:5601/index.js?_b=3998:21997:13)
> > > done@[http://monitor-development-east.test.com](http://monitor-development-east.test.com):
> > > 5601/index.js?\_b=3998:17570:34
> > > completeRequest@[http://monitor-development-east.test](http://monitor-development-east.test).
> > > com:5601/index.js?\_b=3998:17784:7
> > > createHttpBackend/\ > > [monitor-development-east.test.com:5601/index.js?\_b=3998:17727:1](http://monitor-development-east.test.com:5601/index.js?_b=3998:17727:1)
> > >
> > > I am using 1.4.1. Clearly kibana is not working. Why?
> > >
> > > Here is my ES server
> > > {
> > > "status" : 200,
> > > "name" : "Controller",
> > > "cluster\_name" : "elasticsearch",
> > > "version" : {
> > > "number" : "1.4.1",
> > > "build\_hash" : "89d3241d670db65f994242c8e8383b169779e2d4",
> > > "build\_timestamp" : "2014-11-26T15:49:29Z",
> > > "build\_snapshot" : false,
> > > "lucene\_version" : "4.10.2"
> > > },
> > > "tagline" : "You Know, for Search"
> > > }
> > >
> > > Thaks
> > >
> > > --
> > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).
> > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/)
> > > msgid/elasticsearch/CACF%2B8roTzNMtt5FJGQqGQSUQBaMXvVSP
> > > s4phpcLDCbM-Baek0g%[40mail.gmail.com](http://40mail.gmail.com)
> > > [https://groups.google.com/d/msgid/elasticsearch/CACF%2B8roTzNMtt5FJGQqGQSUQBaMXvVSPs4phpcLDCbM-Baek0g%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8roTzNMtt5FJGQqGQSUQBaMXvVSPs4phpcLDCbM-Baek0g%40mail.gmail.com?utm_medium=email&utm_source=footer)
> > > .
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> >
> > --
> > 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](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > To view this discussion on the web visit
> > [https://groups.google.com/d/msgid/elasticsearch/35e05f7f-4275-4a15-bfca-518afc4e1cc7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/35e05f7f-4275-4a15-bfca-518afc4e1cc7%40googlegroups.com)
> > [https://groups.google.com/d/msgid/elasticsearch/35e05f7f-4275-4a15-bfca-518afc4e1cc7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/35e05f7f-4275-4a15-bfca-518afc4e1cc7%40googlegroups.com?utm_medium=email&utm_source=footer)
> > .
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zu7x9Ouaa2YMttO%3D-h1R5LvZAZFFbwGDACB5qgZ6r8ZEQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zu7x9Ouaa2YMttO%3D-h1R5LvZAZFFbwGDACB5qgZ6r8ZEQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)
#### Post date: [December 3, 2014, 11:53pm UTC](https://discuss.elastic.co/t/this-version-of-kibana-requires-at-least-elasticsearch-1-4-0-beta1-but-using-1-4-1/21055/7 "2014-12-03T23:53:50Z")
Hi,
have no agents as of yet. Just logstash server with the below config
input {
redis {
host =\> "\<%=@redis\_host%\>"
data\_type =\> "list"
key =\> "logstash"
codec =\> json
}
}
output {
stdout { }
elasticsearch {
host =\> "\<%=node[:ipaddress]%\>"
}
}
On Thursday, December 4, 2014 6:19:36 AM UTC+8, Jack Judge wrote:
> This tripped me up too.
>
> Are your logstash agents using the elasticsearch output ? If so, they'll
> be running the embedded version of ES that comes with Logstash, and that's
> the version that's stopping kibana from working. Basically _any_ ES node
> that connects to your cluster in any form must be 1.4.x
> My solution was to change the logstash output to elasticsearch\_http
>
> JJ
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1980ac96-edef-4df6-8ec5-38671718fafc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1980ac96-edef-4df6-8ec5-38671718fafc%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 4, 2014, 12:35am UTC](https://discuss.elastic.co/t/this-version-of-kibana-requires-at-least-elasticsearch-1-4-0-beta1-but-using-1-4-1/21055/8 "2014-12-04T00:35:25Z")
You still need to set the protocol to either HTTP or transport though.
On 4 December 2014 at 10:53, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)
wrote:
> Hi,
>
> have no agents as of yet. Just logstash server with the below config
>
> input {
> redis {
> host =\> "\<%=@redis\_host%\>"
> data\_type =\> "list"
> key =\> "logstash"
> codec =\> json
> }
> }
>
> output {
> stdout { }
> elasticsearch {
> host =\> "\<%=node[:ipaddress]%\>"
> }
> }
>
> On Thursday, December 4, 2014 6:19:36 AM UTC+8, Jack Judge wrote:
>
> > This tripped me up too.
> >
> > Are your logstash agents using the elasticsearch output ? If so, they'll
> > be running the embedded version of ES that comes with Logstash, and that's
> > the version that's stopping kibana from working. Basically _any_ ES node
> > that connects to your cluster in any form must be 1.4.x
> > My solution was to change the logstash output to elasticsearch\_http
> >
> > JJ
>
> --
> 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](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/1980ac96-edef-4df6-8ec5-38671718fafc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1980ac96-edef-4df6-8ec5-38671718fafc%40googlegroups.com)
> [https://groups.google.com/d/msgid/elasticsearch/1980ac96-edef-4df6-8ec5-38671718fafc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1980ac96-edef-4df6-8ec5-38671718fafc%40googlegroups.com?utm_medium=email&utm_source=footer)
> .
>
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9X0LKydXear5FwjhFTttGG6xPUr0HqSU2egcciAEVG%2BQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9X0LKydXear5FwjhFTttGG6xPUr0HqSU2egcciAEVG%2BQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)
#### Post date: [December 4, 2014, 7:01am UTC](https://discuss.elastic.co/t/this-version-of-kibana-requires-at-least-elasticsearch-1-4-0-beta1-but-using-1-4-1/21055/9 "2014-12-04T07:01:09Z")
I added the below to elasticsearch.ymk config. Still kibana provides the
same error
http.cors.enabled: true
http.cors.allow-origin: [http://monitor-development-east.test.com:5601](http://monitor-development-east.test.com:5601)
For those at elastiseaerch..can you provide me color on what my be going
on?
Thanks
On Thursday, December 4, 2014 7:53:50 AM UTC+8, David Montgomery wrote:
> Hi,
>
> have no agents as of yet. Just logstash server with the below config
>
> input {
> redis {
> host =\> "\<%=@redis\_host%\>"
> data\_type =\> "list"
> key =\> "logstash"
> codec =\> json
> }
> }
>
> output {
> stdout { }
> elasticsearch {
> host =\> "\<%=node[:ipaddress]%\>"
> }
> }
>
> On Thursday, December 4, 2014 6:19:36 AM UTC+8, Jack Judge wrote:
>
> > This tripped me up too.
> >
> > Are your logstash agents using the elasticsearch output ? If so, they'll
> > be running the embedded version of ES that comes with Logstash, and that's
> > the version that's stopping kibana from working. Basically _any_ ES node
> > that connects to your cluster in any form must be 1.4.x
> > My solution was to change the logstash output to elasticsearch\_http
> >
> > JJ
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/caf7c2cf-3a02-4b31-8d3c-1b2c9ce52ed2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/caf7c2cf-3a02-4b31-8d3c-1b2c9ce52ed2%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Stefan\_Meisner\_Larse](https://discuss.elastic.co/u/Stefan_Meisner_Larse)
#### Post date: [December 4, 2014, 9:48am UTC](https://discuss.elastic.co/t/this-version-of-kibana-requires-at-least-elasticsearch-1-4-0-beta1-but-using-1-4-1/21055/10 "2014-12-04T09:48:45Z")
I had the same problem when I accidentially joined in cluster with a
collegue who was using an older version of elasticsearch.
Changed the cluster name and everything worked perfectly 😉
/Stefan
Den torsdag den 4. december 2014 08.01.09 UTC+1 skrev David Montgomery:
> I added the below to elasticsearch.ymk config. Still kibana provides the
> same error
>
> http.cors.enabled: true
> http.cors.allow-origin: [http://monitor-development-east.test.com:5601](http://monitor-development-east.test.com:5601)
>
> For those at elastiseaerch..can you provide me color on what my be going
> on?
>
> Thanks
>
> On Thursday, December 4, 2014 7:53:50 AM UTC+8, David Montgomery wrote:
>
> > Hi,
> >
> > have no agents as of yet. Just logstash server with the below config
> >
> > input {
> > redis {
> > host =\> "\<%=@redis\_host%\>"
> > data\_type =\> "list"
> > key =\> "logstash"
> > codec =\> json
> > }
> > }
> >
> > output {
> > stdout { }
> > elasticsearch {
> > host =\> "\<%=node[:ipaddress]%\>"
> > }
> > }
> >
> > On Thursday, December 4, 2014 6:19:36 AM UTC+8, Jack Judge wrote:
> >
> > > This tripped me up too.
> > >
> > > Are your logstash agents using the elasticsearch output ? If so, they'll
> > > be running the embedded version of ES that comes with Logstash, and that's
> > > the version that's stopping kibana from working. Basically _any_ ES node
> > > that connects to your cluster in any form must be 1.4.x
> > > My solution was to change the logstash output to elasticsearch\_http
> > >
> > > JJ
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5dad34dc-fe0f-4ab4-86bb-a33571fc434c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5dad34dc-fe0f-4ab4-86bb-a33571fc434c%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:46am UTC](https://discuss.elastic.co/t/this-version-of-kibana-requires-at-least-elasticsearch-1-4-0-beta1-but-using-1-4-1/21055/11 "2017-07-06T00:46:00Z")