Getting "Unable to revive connection" on SSL-configured setup

Kibana v4.5.4
ES v2.4.1

I see similar issues on the forum, but they pertain to an http://localhost:9200 connection.

I have Elasticsearch running through SSL, and I can do this

curl -I https://es_ip_addr:9200 --cacert /path_to_cert/my_cert.pem 
HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Content-Length: 0

However, I see these in my kibana.log file

{"type":"log","@timestamp":"2016-10-27T16:30:49+00:00","tags":["warning","elasticsearch"],"pid":5611,"message":"Unable to revive connection: https://es_ip_addr:9200/"}
{"type":"log","@timestamp":"2016-10-27T16:30:49+00:00","tags":["warning","elasticsearch"],"pid":5611,"message":"No living connections"}

Here is my kibana.yml file, with most of the comments removed to ease reading.

# The Elasticsearch instance to use for all your queries.
elasticsearch.url: "https://es_ip_addr:9200"

# username and pw
elasticsearch.username: "kibanaserver"
elasticsearch.password: "pw"

# If you need to provide a CA certificate for your Elasticsearch instance, put
# the path of the pem file here.
elasticsearch.ssl.ca: /path_to_cert/my_cert.pem

# If you would like to send the log output to a file you can set the path below.
logging.dest: /var/log/kibana/kibana.log

What am I missing?

I do see these logs, which are earlier than logs I see above

{"type":"log","@timestamp":"2016-10-27T16:37:36+00:00","tags":["status","plugin:spyModes","info"],"pid":5747,"name":"plugin:spyModes","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-27T16:37:36+00:00","tags":["error","elasticsearch"],"pid":5747,"message":"Request error, retrying -- self signed certificate in certificate chain"}
{"type":"log","@timestamp":"2016-10-27T16:37:36+00:00","tags":["status","plugin:statusPage","info"],"pid":5747,"name":"plugin:statusPage","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}

In my case, I was using the SG-SSL plugin, and forgot to set the ES CA path per this page https://github.com/floragunncom/search-guard-docs/blob/master/kibana.md. Once I did the problem went away.

Hi Zilla,

Thanks for updating with your solution!

Regards,
Lee