# Upstream prematurely closed connection while connecting to Kibana

**URL:** <https://discuss.elastic.co/t/upstream-prematurely-closed-connection-while-connecting-to-kibana/329056>\
**Category:** Kibana\
**Created:** [March 31, 2023, 1:33pm UTC](https://discuss.elastic.co/t/upstream-prematurely-closed-connection-while-connecting-to-kibana/329056 "2023-03-31T13:33:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ravi\_Prakash1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_prakash1/32/119287_2.png) [@Ravi\_Prakash1](https://discuss.elastic.co/u/Ravi_Prakash1)\
**Post date:** [March 31, 2023, 1:33pm UTC](https://discuss.elastic.co/t/upstream-prematurely-closed-connection-while-connecting-to-kibana/329056/1 "2023-03-31T13:33:19Z")

</div>

Hello ,

Need some help with issue which we are facing while connecting to Kibana via Nginx using **proxy\_pass.**

We are using ECK operator on Openshift ( Elasticsearch (ECK) Operator 2.6.2 provided by Elastic ) .

While doing proxy \_pass to kibana service , below error can be seen in nginx error logs:

\*360#360: _575 upstream prematurely closed connection while reading response header from upstream,_

The proxy\_pass to some other service ( which also serves a UI ) works fine using same nginx. Only while proxying to Kibana, this issue is encountered.

Tried many configurations on the nginx side like various proxy related timeout params, keep-alive etc , but in vain.

Suspicion is that something on the Kibana side needs to be tuned. Perhaps related to HTTP/TCP.

Pls help. Thanks

---

<div class="post-metadata">

**Author:** ![Ravi\_Prakash1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_prakash1/32/119287_2.png) [@Ravi\_Prakash1](https://discuss.elastic.co/u/Ravi_Prakash1)\
**Post date:** [April 2, 2023, 2:26pm UTC](https://discuss.elastic.co/t/upstream-prematurely-closed-connection-while-connecting-to-kibana/329056/2 "2023-04-02T14:26:03Z")

</div>

Solution/workaround which worked :

_proxy\_pass_ was to **http** but TLS was not disabled on Kibana side.

After disabling TLS on Kibana side, was able to login to Kibana Dashboard.

---

<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:** [April 30, 2023, 2:26pm UTC](https://discuss.elastic.co/t/upstream-prematurely-closed-connection-while-connecting-to-kibana/329056/3 "2023-04-30T14:26:20Z")

</div>

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