# 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:** 1
**Showing post:** 22

<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!

---

_[View the full topic](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)._