An easy work around is to request elastic search under a sub-domain that is not configured for https. If there is a documented way to change the request from kibana from http to https I as of yet have not found it, however it could be as simple as changing the base url structure somewhere in kibana and setting up a reverse proxy from apache or nginx to the elasticsearch server, that should allow you to setup client certificates and https as per usual with apache or nginx.
On Tuesday, February 17, 2015 at 4:01:40 PM UTC-6, Shital Patel wrote: > > What was the solution. I have the same issue. I am running a nginx proxy > which redirects all http traffic to https and then kibana is complaining > that the request was https and we are trying to get elasticsearch over http. > > thanks > > > On Sunday, January 25, 2015 at 8:45:58 PM UTC-8, Shawn Nicholas Stark > wrote: >> >> Using kibana-3.0.0milestone4 >> Cannot Load Data from elasticsearch with queries that work from shell >> Receive Error : TypeError: Cannot read property 'length' of undefined >> (Attached) >> ElasticSearch can be queried via the browser URL bar and terminal >> >> The gist that shows exactly what data I am using and recreates the query >> from kibana. >> The query showed in the gist is working in the terminal localy and >> remotely (Attached with Results) >> https://gist.github.com/anonymous/3f07f1bd9f0598bb5a0b >> >> >> -- 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/922d3fc9-9518-44ac-82d4-4bbf970c4657%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
