# Fails to launch Kibana 6 with ES tribe url after upgrading from 5 **URL:** \ **Category:** Kibana\ **Created:** [July 6, 2019, 12:45pm UTC](https://discuss.elastic.co/t/fails-to-launch-kibana-6-with-es-tribe-url-after-upgrading-from-5/189204 "2019-07-06T12:45:24Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\ **Post date:** [July 8, 2019, 3:56pm UTC](https://discuss.elastic.co/t/fails-to-launch-kibana-6-with-es-tribe-url-after-upgrading-from-5/189204/4 "2019-07-08T15:56:11Z")
Can you share which version of 6 you're migrating to? The stack trace in the original post looks like a bug. For good measure can we take a look at your kibana config? Double checking indentation may help. Other notes - tribe should work in 6 but is deprecated in favor of cross cluster cluster search, if that's an option. Index creation issues can be caused by creating the index on the tribe node instead of directly to one of the clusters. Index migrations are probably getting in the way, so we may have to run migrations directly on one of the clusters first and then configure tribe. --- _[View the full topic](https://discuss.elastic.co/t/fails-to-launch-kibana-6-with-es-tribe-url-after-upgrading-from-5/189204)._