# Kibana Status RED - {"code":"ECONNRESET"}

**URL:** <https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527>\
**Category:** Kibana\
**Created:** [June 19, 2018, 3:29pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527 "2018-06-19T15:29:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [June 19, 2018, 3:29pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527/1 "2018-06-19T15:29:33Z")

</div>

I was trying to access Kibana and I've got redirected to page with following message in red:

> plugin:elasticsearch@6.2.4 {"code":"ECONNRESET"}

Kibana's log:

`kibana-re-custom | {"type":"log","@timestamp":"2018-06-19T14:57:11Z","tags":["error","elasticsearch","admin"],"pid":1,"message":"Request error, retrying\nGET http://esc1:9200/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip => socket hang up"}`

yet when I looked at elasticsearch log, there is no errors and it seems to be working just fine. I restarted both of them elasticsearch and kibana and everything is back to normal.

Please advise.

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [June 19, 2018, 3:31pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527/2 "2018-06-19T15:31:51Z")

</div>

Hi,

is your kibana up now?

> [@alexus](#):
>
> yet when I looked at elasticsearch log, there is no errors and it seems to be working just fine. I restarted both of them elasticsearch and kibana and everything is back to normal.

Thanks,  
Bhavya

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [June 19, 2018, 3:47pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527/3 "2018-06-19T15:47:12Z")

</div>

As I stated earlier after restart both Elasticsearch and Kibana everything is back to normal, however I would like figure out what exactly went wrong and what can I do to prevent this in future or at least do better troubleshooting to help you guys figure out an actual cause...

---

<div class="post-metadata">

**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\
**Post date:** [June 19, 2018, 4:00pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527/4 "2018-06-19T16:00:10Z")

</div>

Hi @alexus,

It sounds like you might be experiencing the same problem that [another user reported](https://discuss.elastic.co/t/elasticsearch-kibana-econnreset-solved/130097/17?u=larry_gregory). His solution was to put a proxy in between Kibana and Elasticsearch, but an easier solution for you might be to set the `elasticsearch.healthcheck.delay` property to a higher value (see [linked issue](https://github.com/elastic/kibana/issues/16733#issuecomment-367047419)).

If this is in fact what you are experiencing, then I recommend voting for [https://github.com/elastic/kibana/issues/14163](https://github.com/elastic/kibana/issues/14163), which solves the underlying problem.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [June 19, 2018, 7:34pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527/5 "2018-06-19T19:34:09Z")

</div>

I appreciate your reply. I follow [Using Kibana in a production environment | Kibana User Guide](https://www.elastic.co/guide/en/kibana/current/production.html) (I don't see anything proxy related)

I'm more than willing to experiment with `elasticsearch.healthcheck.delay` value, however I can't find what's default value and how high should I increase it too?

Please advise.

---

<div class="post-metadata">

**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\
**Post date:** [June 19, 2018, 7:41pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527/6 "2018-06-19T19:41:23Z")

</div>

You're absolutely right, setting up a proxy is outside the scope of that setup document. I wouldn't advise going down that route right now, until we've exhausted other options.

The `elasticsearch.healthcheck.delay` defaults to `2500`, which is 2.5 minutes (it expects milliseconds). I would start by doubling that to `5000` (5 minutes), and see if that alleviates your symptoms. If not, try bumping that up to 8 or 10 minutes. If you're having issues after that, then there could be something else going on

---

<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 17, 2018, 7:41pm UTC](https://discuss.elastic.co/t/kibana-status-red-code-econnreset/136527/7 "2018-07-17T19:41:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
