Wrong in every fundamental aspect. This was a clusterfuck and still is. The K3 dashboards are used by our devs, network guys and management for a variety of tasks. When they stopped working we lost sight of large parts of our operation. Because of the lack of documentation and the time pressure, I don't have the luxury of sitting down, picking up a coffee and learning all about CORS, so yeah we've downgraded back to 1.3
Unless you know how to fix it, which I don't, then this is a clusterfuck, it rendered our system useless to us. On Thursday, 4 December 2014 07:40:47 UTC-8, Itamar Syn-Hershko wrote: > > Classic CORS error - maybe * is blocked by ES. Haven't had to deal with > this myself (yet) so can't help you here. All in all just a small rough > edge to smooth, not a clusterfuck. > > A quick solution would be to install K3 as a site plugin and use it > internally (don't expose it to the web) > > -- > > Itamar Syn-Hershko > http://code972.com | @synhershko <https://twitter.com/synhershko> > Freelance Developer & Consultant > Author of RavenDB in Action <http://manning.com/synhershko/> > > On Thu, Dec 4, 2014 at 3:20 AM, Jack Judge <[email protected] > <javascript:>> wrote: > >> Well you're right there's JS errors, CORS related; >> >> XMLHttpRequest cannot load >> http://10.5.41.120:9200/logstash-2014.12.04/_search. Request header >> field Content-Type is not allowed by Access-Control-Allow-Headers. >> >> In my elasticsearch.yml I've got this on all nodes, >> >> http.cors.allow-origin: "/.*/" >> http.cors.enabled: true >> >> Which google leads me to believe should open it up for anything. K3 is >> fronted by apache and a bit more googling prompted me to add this to the >> <Directory> section of httpd.conf >> >> Header set Access-Control-Allow-Origin "*" >> >> Still getting the same errors :( >> I'm at a loss to know what else to do now. >> >> >> >> On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote: >>> >>> I'm not aware of compat issues with K3 and ES 1.4 other than >>> https://github.com/elasticsearch/kibana/issues/1637 . I'd check for >>> javascript errors, and try to see what's going on under the hood, really. >>> When you have more data about this, you can either quickly resolve, or open >>> a concrete bug :) >>> >>> >>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
