# Cluster crashed: "Server gave HTTP response to HTTPS client"

**URL:** <https://discuss.elastic.co/t/cluster-crashed-server-gave-http-response-to-https-client/255762>\
**Category:** Elasticsearch\
**Created:** [November 17, 2020, 9:18pm UTC](https://discuss.elastic.co/t/cluster-crashed-server-gave-http-response-to-https-client/255762 "2020-11-17T21:18:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![realscout](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/realscout/32/16161_2.png) [@realscout](https://discuss.elastic.co/u/realscout)\
**Post date:** [November 17, 2020, 9:18pm UTC](https://discuss.elastic.co/t/cluster-crashed-server-gave-http-response-to-https-client/255762/1 "2020-11-17T21:18:04Z")

</div>

Today, our ElasticSearch cluster stopped responding. We were not performing any sort of maintenance or making any changes.

Any request to the cluster caused it to respond with:

`"Get "https://X.X.X.X:X/": http: server gave HTTP response to HTTPS client".`

(IP Address filtered out for privacy, just in case)

Checking the logs, I see that right before the crash, the system logged:

`[instance-0000000030] reloaded [/app/config/node.crt] and updated ssl contexts using this file`

We performed a rolling restart, and the cluster started responding correctly as the nodes restarted.

This cluster is on 6.X still, and has been running fine for many years. I've never seen anything like this before. Anyone have any insight on what may have happened, why this may have happened? I've searched around, but never seen anyone talk about anything like this.

---

<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:** [November 17, 2020, 10:27pm UTC](https://discuss.elastic.co/t/cluster-crashed-server-gave-http-response-to-https-client/255762/2 "2020-11-17T22:27:19Z")

</div>

Welcome to our community! 😃

Can you share more of your logs please. Exactly what version of 6.X are you running? What are you using to provide TLS for Elasticsearch?

---

<div class="post-metadata">

**Author:** ![realscout](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/realscout/32/16161_2.png) [@realscout](https://discuss.elastic.co/u/realscout)\
**Post date:** [November 17, 2020, 10:48pm UTC](https://discuss.elastic.co/t/cluster-crashed-server-gave-http-response-to-https-client/255762/3 "2020-11-17T22:48:13Z")

</div>

I just heard back from the ElasticCloud support team that this issue did affect multiple customers today, and wasn't unique to my instance. They've updated the status page with this issue (502 Bad Gateway).

I'll leave this issue here, in case other customers have had this issue today, to let them know that that this was identified by the ElasticCloud team as an issue affecting multiple customers.

---

<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:** [December 15, 2020, 10:48pm UTC](https://discuss.elastic.co/t/cluster-crashed-server-gave-http-response-to-https-client/255762/4 "2020-12-15T22:48:21Z")

</div>

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