# Problem after elasticsearch upgrade to 6.0

**URL:** <https://discuss.elastic.co/t/problem-after-elasticsearch-upgrade-to-6-0/116361>\
**Category:** Elasticsearch\
**Created:** [January 20, 2018, 11:41pm UTC](https://discuss.elastic.co/t/problem-after-elasticsearch-upgrade-to-6-0/116361 "2018-01-20T23:41:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![picasta](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@picasta](https://discuss.elastic.co/u/picasta)\
**Post date:** [January 20, 2018, 11:41pm UTC](https://discuss.elastic.co/t/problem-after-elasticsearch-upgrade-to-6-0/116361/1 "2018-01-20T23:41:17Z")

</div>

Hello,

First I must say that I'm totally noob with Elasticsearch, so please take my apologies if this is basic question.

After upgrading elasticsearch on my server to 6.0 version my site breaks.

Can someone please tell me what is wrong and what I need to do?

Thanks!

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [January 20, 2018, 11:43pm UTC](https://discuss.elastic.co/t/problem-after-elasticsearch-upgrade-to-6-0/116361/2 "2018-01-20T23:43:47Z")

</div>

All requests with bodies [must send a valid content-type header](https://www.elastic.co/blog/strict-content-type-checking-for-elasticsearch-rest-requests). The error message is telling you that you’re not sending a valid non-empty content-type header.

---

<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:** [February 17, 2018, 11:43pm UTC](https://discuss.elastic.co/t/problem-after-elasticsearch-upgrade-to-6-0/116361/3 "2018-02-17T23:43:56Z")

</div>

Closed on February 17, 2018, 11:43pm UTC

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