I want the front end of ES (kibana) to run on SSL but keep the
backend connection from Kibana to ES unencrypted since both are
running on the same host. I configured Apache2 to accept SSL
connections and it works but when Kibana populates the dashboard it
get the below error. Any help is very much appreciated. Could not
reach [1]http://ec2-XX-XX-XX-XX.compute-1.amazonaws.com/elasticsearch/_
nodes. If you are using a proxy, ensure it is configured correctly
Which version of Kibana is this?
--
Magnus Bäck | Software Engineer, Development Tools magnus.back@sonymobile.com | Sony Mobile Communications
On Tuesday, January 20, 2015 at 2:17:49 AM UTC-5, Magnus Bäck wrote:
On Monday, January 19, 2015 at 15:45 CET,
Karthik M <karth...@gmail.com <javascript:>> wrote:
I want the front end of ES (kibana) to run on SSL but keep the
backend connection from Kibana to ES unencrypted since both are
running on the same host. I configured Apache2 to accept SSL
connections and it works but when Kibana populates the dashboard it
get the below error. Any help is very much appreciated. Could not
reach [1]http://ec2-XX-XX-XX-XX.compute-1.amazonaws.com/elasticsearch/_
nodes. If you are using a proxy, ensure it is configured correctly
Which version of Kibana is this?
--
Magnus Bäck | Software Engineer, Development Tools magnu...@sonymobile.com <javascript:> | Sony Mobile Communications
On Tuesday, January 20, 2015 at 2:17:49 AM UTC-5, Magnus Bäck wrote:
I want the front end of ES (kibana) to run on SSL but keep the
backend connection from Kibana to ES unencrypted since both are
running on the same host. I configured Apache2 to accept SSL
connections and it works but when Kibana populates the dashboard
it get the below error. Any help is very much appreciated. Could
not reach http://ec2-XX-XX-XX-XX.compute-1.amazonaws.com/elasticsearch/_
nodes. If you are using a proxy, ensure it is configured correctly
Which version of Kibana is this?
Kibana version 3
Kibana 3 doesn't have a backend. The connections to Elasticsearch
originate from your browser so you'll want to encrypt them as well.
Placing just the Kibana files behind HTTPS isn't useful.
--
Magnus Bäck | Software Engineer, Development Tools magnus.back@sonymobile.com | Sony Mobile Communications
On Tuesday, January 20, 2015 at 2:17:49 AM UTC-5, Magnus Bäck wrote:
I want the front end of ES (kibana) to run on SSL but keep the
backend connection from Kibana to ES unencrypted since both are
running on the same host. I configured Apache2 to accept SSL
connections and it works but when Kibana populates the dashboard
it get the below error. Any help is very much appreciated. Could
not reach http://ec2-XX-XX-XX-XX.compute-1.amazonaws.com/elasticsearch/_
nodes. If you are using a proxy, ensure it is configured correctly
Which version of Kibana is this?
Kibana version 3
Kibana 3 doesn't have a backend. The connections to Elasticsearch
originate from your browser so you'll want to encrypt them as well.
Placing just the Kibana files behind HTTPS isn't useful.
--
Magnus Bäck | Software Engineer, Development Tools magnus.back@sonymobile.com | Sony Mobile Communications
Kibana 3 doesn't have a backend. The connections to Elasticsearch
originate from your browser so you'll want to encrypt them as well.
Placing just the Kibana files behind HTTPS isn't useful.
Thanks Magnus. Would be able to point me towards on how to set that up?
Googling "kibana reverse proxy" should yield some useful results,
but start with the blog post from the Elasticsearch team.
--
Magnus Bäck | Software Engineer, Development Tools magnus.back@sonymobile.com | Sony Mobile Communications
Kibana 3 doesn't have a backend. The connections to Elasticsearch
originate from your browser so you'll want to encrypt them as well.
Placing just the Kibana files behind HTTPS isn't useful.
Thanks Magnus. Would be able to point me towards on how to set that up?
Googling "kibana reverse proxy" should yield some useful results,
but start with the blog post from the Elasticsearch team.
I'm also working through the same process (see my post at https://groups.google.com/d/msg/elasticsearch/S4LQQrbZAb4/r8bnxIwgkGUJ),
but the ES blog link you provided doesn't touch on Kibana access to ES
sitting behind a reverse proxy. This is where I'm having problems. Any
ideas welcome.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.