# Logstash-ES communication issue and Kibana not coming up

**URL:** <https://discuss.elastic.co/t/logstash-es-communication-issue-and-kibana-not-coming-up/55613>\
**Category:** Logstash\
**Created:** [July 15, 2016, 11:56am UTC](https://discuss.elastic.co/t/logstash-es-communication-issue-and-kibana-not-coming-up/55613 "2016-07-15T11:56:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vienodp](https://avatars.discourse-cdn.com/v4/letter/v/46a35a/32.png) [@vienodp](https://discuss.elastic.co/u/vienodp)\
**Post date:** [July 15, 2016, 11:56am UTC](https://discuss.elastic.co/t/logstash-es-communication-issue-and-kibana-not-coming-up/55613/1 "2016-07-15T11:56:35Z")

</div>

I have 2 nodes in a cluster , 35 and 72 with ELK/Shield installed on it. After enabling the Shield parameters in elasticsearch.yml, Logstash to ES communications not working and Kibana is not starting up.

I have enabled Shield plugin and configured the SSL/TLS encryption. Now my kibana is not starting up.

I can see these entries in logstash logs -

> timestamp=\>"2016-07-15T13:01:51.995000+0530", :message=\>"Attempted to send a bulk request to Elasticsearch configured at '["[https://9.126.112.72:9200/\](https://9.126.112.72:9200/%5C)"]', but Elasticsearch appears to be unreachable or down!", :error\_message=\>"Connection refused", :class=\>"Manticore::SocketException", :client\_config=\>{:hosts=\>["[https://9.126.112.72:9200/](https://9.126.112.72:9200/)"], :ssl=\>{:enabled=\>true, :ca\_file=\>"/etc/logstash/cert.pem"}, :transport\_options=\>{:socket\_timeout=\>0, :request\_timeout=\>0, :proxy=\>nil, :ssl=\>{:enabled=\>true, :ca\_file=\>"/etc/logstash/cert.pem"}}, :transport\_class=\>Elasticsearch::Transport::Transport::HTTP::Manticore, :headers=\>{"Authorization"=\>"Basic dmlub2RhcjNAaW4uaWJtLmNvbTp0aWdlUkAzMjE="}, :logger=\>nil, :tracer=\>nil, :reload\_connections=\>false, :retry\_on\_failure=\>false, :reload\_on\_failure=\>false, :randomize\_hosts=\>false}, :level=\>:error

and these entries in elastcisearch logs

> [2016-07-15 14:07:25,129][WARN][shield.transport.netty] [irldxvm022] received plaintext http traffic on a https channel, closing connection [id: 0x3d9f3207, /9.126.112.35:45330 =\> /9.126.112.72:9200]

---

<div class="post-metadata">

**Author:** ![vienodp](https://avatars.discourse-cdn.com/v4/letter/v/46a35a/32.png) [@vienodp](https://discuss.elastic.co/u/vienodp)\
**Post date:** [July 15, 2016, 12:02pm UTC](https://discuss.elastic.co/t/logstash-es-communication-issue-and-kibana-not-coming-up/55613/2 "2016-07-15T12:02:41Z")

</div>

This is continuation of

[https://discuss.elastic.co/t/ssl-tls-on-elk-cluster/54641/](https://discuss.elastic.co/t/ssl-tls-on-elk-cluster/54641/)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 17, 2016, 7:44am UTC](https://discuss.elastic.co/t/logstash-es-communication-issue-and-kibana-not-coming-up/55613/3 "2016-07-17T07:44:47Z")

</div>

It might be easier to continue the discussion in the other thread.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:47am UTC](https://discuss.elastic.co/t/logstash-es-communication-issue-and-kibana-not-coming-up/55613/4 "2017-07-06T04:47:42Z")

</div>


