# Fresh install kibana Rejecting mapping update to \[.kibana\] as the final mapping would have more than 1 type: \[log, doc\]

**URL:** https://discuss.elastic.co/t/fresh-install-kibana-rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-log-doc/117413
**Category:** Kibana
**Created:** [January 29, 2018, 8:08am UTC](https://discuss.elastic.co/t/fresh-install-kibana-rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-log-doc/117413 "2018-01-29T08:08:19Z")
**Posts on this page:** 4
**Page:** 2

<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: [January 31, 2018, 2:39am UTC](https://discuss.elastic.co/t/fresh-install-kibana-rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-log-doc/117413/21 "2018-01-31T02:39:45Z")

</div>

> [@zzchen](#):
>
> BTW, i use reverse proxy and configured server path

Does it work without the proxy?

---

<div class="post-metadata">

### Author: ![zzchen](https://avatars.discourse-cdn.com/v4/letter/z/dbc845/32.png) [@zzchen](https://discuss.elastic.co/u/zzchen)
#### Post date: [January 31, 2018, 4:23am UTC](https://discuss.elastic.co/t/fresh-install-kibana-rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-log-doc/117413/22 "2018-01-31T04:23:39Z")

</div>

I don't think it the problem of proxy. There are two reason:

- The `server base path` setting works from Kibana 5.x.
- I test the same configuration with clean Kibana and Elasticsearch (a whole different cluster), all function works.

We might narrow down the problem to:

- Why kibana doesn't show any create `.kibana` index error while starting up?
- Why kibana automatically created template cannot create `.kibana`
- Does `old data` (my application data without reindex from 5.6 to 6.1 yet) cause any error like this?

Thanks!

---

<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: [January 31, 2018, 11:28am UTC](https://discuss.elastic.co/t/fresh-install-kibana-rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-log-doc/117413/23 "2018-01-31T11:28:40Z")

</div>

> [@zzchen](#):
>
> Does old data (my application data without reindex from 5.6 to 6.1 yet) cause any error like this?

Definitely. .kibana builds out of data types in your application data. So you need to reindex your data.

Thanks,  
Bhavya

---

<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 28, 2018, 11:28am UTC](https://discuss.elastic.co/t/fresh-install-kibana-rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-log-doc/117413/24 "2018-02-28T11:28:50Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/fresh-install-kibana-rejecting-mapping-update-to-kibana-as-the-final-mapping-would-have-more-than-1-type-log-doc/117413.md?page=1)
