Hello, I've upgraded to Elasticsearch 1.5.2 and Kibana 4.0.2 which I am deploying in a Kubernetes <http://kubernetes.io/> cluster. Specifically, I am running Elasticsearch in one "pod" (a Kubernetes container with its own IP) and I am running Kibana in another pod (again with a distinct IP address). The Kubernetes cluster runs a DNS service which will map the name "elasticsearch-logging.default:9200" to the pod running Elasticsearch. This works fine: I can exec into any Docker container in a pod and run "curl http://elasticsearch-logging.default:9200"; and the right thing happens. I've configured Kibana to let it know where Elasticsearch is running:
elasticsearch_url: "http://elasticsearch-logging.default:9200"; elasticsearch_preserve_host: true Since I want to access Kibana from outside the cluster I use a proxy running on the master node of the cluster (after adding certificates to my browser for the SSL connection) e.g. https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/ Sadly, this does not work. I get the error: Error: Unable to check for Kibana index ".kibana" Error: unknown error at respond (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:81693:15) at checkRespForFailure (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:81659:7) at https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:80322:7 at deferred.promise.then.wrappedErrback (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:20897:78) at deferred.promise.then.wrappedErrback (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:20897:78) at deferred.promise.then.wrappedErrback (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:20897:78) at https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:21030:76 at Scope.$get.Scope.$eval (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:22017:28) at Scope.$get.Scope.$digest (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:21829:31) at Scope.$get.Scope.$apply (https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/index.js?_b=6004:22121:24) And this is what the console shows: <https://lh3.googleusercontent.com/-hvUxjiNbpWU/VT_7XwsyMXI/AAAAAAAATYk/8ttLRY4rE58/s1600/Screenshot%2Bfrom%2B2015-04-28%2B14%3A27%3A40.png> Visiting https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/kibana-logging/elasticsearch works (i.e. returns the status of Elasticsearch). So does visiting Elasticsearch via the proxy i.e. https://104.197.26.147/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging/ I wonder if anyone has some advice about what is going wrong here? Thank you kindly. Cheers, Satnam -- 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/44f86cfe-4844-42b9-9823-b3adb95b834f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
