# Upgrade from 6.3.2 to 6.3.5 causing serveral issues

**URL:** <https://discuss.elastic.co/t/upgrade-from-6-3-2-to-6-3-5-causing-serveral-issues/159614>\
**Category:** Kibana\
**Created:** [December 5, 2018, 10:28pm UTC](https://discuss.elastic.co/t/upgrade-from-6-3-2-to-6-3-5-causing-serveral-issues/159614 "2018-12-05T22:28:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![memelet](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@memelet](https://discuss.elastic.co/u/memelet)\
**Post date:** [December 5, 2018, 10:28pm UTC](https://discuss.elastic.co/t/upgrade-from-6-3-2-to-6-3-5-causing-serveral-issues/159614/1 "2018-12-05T22:28:19Z")

</div>

The first problem I ran into was the xpack user bug ([https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0](https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0)). Thought that would have been fixed by 6.5.2.

After deleting the indices and creating the hack user kibana is back up. But of course I lost all the configuration (should have realized this was going to be the case).

So first step is to recreate the index patterns. But just clicking thru "Index Patterns" in management resulted in the "Payload content length greater than maximum allowed" error. So I tripled the value to 3145728 and still get the error.

I'm starting to think I have some other problems.

---

<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:** [January 2, 2019, 10:28pm UTC](https://discuss.elastic.co/t/upgrade-from-6-3-2-to-6-3-5-causing-serveral-issues/159614/2 "2019-01-02T22:28:19Z")

</div>

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