# Kibana 6.1.0. and newer starts with error **URL:** \ **Category:** Kibana\ **Created:** [December 14, 2017, 11:21am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754 "2017-12-14T11:21:41Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\ **Post date:** [December 14, 2017, 11:21am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/1 "2017-12-14T11:21:41Z")
I've upgrade ES 6.0.0 to 6.1.0. The second step was to upgrade Kibana. When I start Kibana I get this error. ```auto TypeError: _reactcss.handleHover is not a function (http://_SERVER_:5601/bundles/kibana.bundle.js?v=16337:67) ``` Additional data: ```auto Version: 6.1.0 Build: 16337 ``` ```auto Error: TypeError: _reactcss.handleHover is not a function (http://_SERVER_:5601/bundles/kibana.bundle.js?v=16337:67) [2134]/window.onerror@http://_SERVER_:5601/bundles/commons.bundle.js?v=16337:45:8728 ``` Tried in IE 11 version 11.0.9600.18838 and FF 57.0.2 x64 ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 14, 2017, 7:35pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/2 "2017-12-14T19:35:13Z")
Hi I see the same error. From chrome: Uncaught TypeError: (0 , \_reactcss.handleHover) is not a function ([http://localhost:5601/bundles/kibana.bundle.js?v=16337:54](http://localhost:5601/bundles/kibana.bundle.js?v=16337:54)) ```auto Version: 6.1.0 Build: 16337 ``` ```auto Error: Uncaught TypeError: (0 , _reactcss.handleHover) is not a function (http://localhost:5601/bundles/kibana.bundle.js?v=16337:54) at window.onerror (http://localhost:5601/bundles/commons.bundle.js?v=16337:45:9804) ``` Regards Kim ---
**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\ **Post date:** [December 15, 2017, 8:24am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/3 "2017-12-15T08:24:51Z")
I've pushed Kibana to 6.0.1 and it's working. So it's just a problem of 6.1.0. Would one of the forums staff post this on gitHub, because everything I've posted there stalls. ---
**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\ **Post date:** [December 17, 2017, 5:06am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/4 "2017-12-17T05:06:31Z")
Kim, could you please share with us the OS you're on? Thank you, CJ ---
**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\ **Post date:** [December 17, 2017, 5:20am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/5 "2017-12-17T05:20:21Z")
Also, are either of you using X-Pack by any chance? Thanks, CJ ---
**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\ **Post date:** [December 17, 2017, 6:14am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/6 "2017-12-17T06:14:56Z")
No, I'm not using X-pack. And my OS is Windows server 2012 R2. ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 17, 2017, 8:19am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/7 "2017-12-17T08:19:26Z")
Hi CJ I am using windows 10 x,64 on my home dev box , x-pack with basic license. If you need other info, just let me know 🙂 Regards Kim ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 17, 2017, 8:20am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/8 "2017-12-17T08:20:21Z")
btw , I also downgraded to 6.0.1 , which works fine. Kim ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 19, 2017, 4:44pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/9 "2017-12-19T16:44:00Z")
Hi CJ, Any news on the progress with the troubleshooting? Regards Kim ---
**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\ **Post date:** [December 19, 2017, 10:11pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/10 "2017-12-19T22:11:49Z")
Hi, I'm sorry but we haven't been able to reproduce on either Windows 10 or Windows Server 2012. We think there may be something about your systems that's causing this issue but we're not sure what it could be. We're going to continue testing and trying to reproduce this error. In the meantime, if you could think of anything else that could help us pin down the source of this error, please let us know. Thanks, CJ ---
**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\ **Post date:** [December 20, 2017, 6:47am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/11 "2017-12-20T06:47:54Z")
Is there anything me and @Kim-Kruse-Hansen could do to test or narrow in this issue for you? ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 20, 2017, 10:06am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/12 "2017-12-20T10:06:08Z")
Hi I have another server on win2012r2, that I will try to upgrade later today. I will let you know , how it turns out. Regards Kim ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 20, 2017, 5:51pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/13 "2017-12-20T17:51:27Z")
Hi I have upgraded another server on windows server 2012 r2 from 6.0.0 , to 6.1.0. Same error. I then noticed that 6.1.1 had been released. So I tried that version also. Same error Tried IE11 , Edge , Firefox, chrome , all same error. Fatal Error Uncaught TypeError: (0 , \_reactcss.handleHover) is not a function ([http://localhost:5601/bundles/kibana.bundle.js?v=16350:54](http://localhost:5601/bundles/kibana.bundle.js?v=16350:54)) Version: 6.1.1 Build: 16350 Error: Uncaught TypeError: (0 , \_reactcss.handleHover) is not a function ([http://localhost:5601/bundles/kibana.bundle.js?v=16350:54](http://localhost:5601/bundles/kibana.bundle.js?v=16350:54)) at window.onerror ([http://localhost:5601/bundles/commons.bundle.js?v=16350:45:9804](http://localhost:5601/bundles/commons.bundle.js?v=16350:45:9804)) Kibana starts normal: PS C:\elastic\kibana\bin\> .\kibana log [17:44:48.192] [info][status][plugin:kibana@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.265] [info][status][plugin:elasticsearch@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [17:44:48.295] [info][status][plugin:xpack\_main@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [17:44:48.325] [info][status][plugin:monitoring@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.331] [info][status][plugin:searchprofiler@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [17:44:48.349] [info][status][plugin:ml@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [17:44:48.408] [info][status][plugin:tilemap@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [17:44:48.410] [info][status][plugin:elasticsearch@6.1.1] Status changed from yellow to green - Ready log [17:44:48.416] [info][status][plugin:watcher@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [17:44:48.449] [info][status][plugin:grokdebugger@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.457] [info][status][plugin:dashboard\_mode@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.461] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: basic | status: active | expiry date: 2018-04-02T01:59:59+02:00 log [17:44:48.469] [info][status][plugin:xpack\_main@6.1.1] Status changed from yellow to green - Ready log [17:44:48.473] [info][status][plugin:searchprofiler@6.1.1] Status changed from yellow to green - Ready log [17:44:48.474] [info][status][plugin:ml@6.1.1] Status changed from yellow to green - Ready log [17:44:48.475] [info][status][plugin:tilemap@6.1.1] Status changed from yellow to green - Ready log [17:44:48.477] [info][status][plugin:watcher@6.1.1] Status changed from yellow to green - Ready log [17:44:48.481] [info][status][plugin:logstash@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.522] [info][status][plugin:apm@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.529] [info][status][plugin:license\_management@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.531] [info][license][xpack] Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: active | expiry date: 2018-04-02T01:59:59+02:00 log [17:44:48.562] [info][status][plugin:console@6.1.1] Status changed from uninitialized to green - Ready log [17:44:48.600] [info][status][plugin:metrics@6.1.1] Status changed from uninitialized to green - Ready log [17:44:51.906] [info][status][plugin:timelion@6.1.1] Status changed from uninitialized to green - Ready Seems to me that every version from 6.1.x and above are seriously broken on the windows platform. Regards Kim ---
**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\ **Post date:** [December 21, 2017, 6:20am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/14 "2017-12-21T06:20:04Z")
According to error, could we assume that there was a change within `reactcss`. A new version or sth? Could this be our start point? ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 21, 2017, 6:25pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/15 "2017-12-21T18:25:44Z")
Hi I have managed to get it working by uninstalling x-pack and adding it back again. I will do some further experiments Regards Kim ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 21, 2017, 8:40pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/16 "2017-12-21T20:40:15Z")
Hi Mojster. Try this fix: Goto /optimize You shouldlsee a .cache / bundles/.babelcache.json Clear all contents of this directory Restart kibana Upon restart it will rebuild the the optimize directory with a new version. Let me know if it helps. Regards Kim ---
**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\ **Post date:** [December 21, 2017, 8:53pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/17 "2017-12-21T20:53:55Z")
If this has fixed it, you can safely delete the whole `optimize` folder, no need to check for something specifically. Kibana rebuilds the folder at start when it's not present. Probably why I couldn't manage to reproduce it the past days, because I didn't have any babel.cache in my optimize folder. ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [December 21, 2017, 9:03pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/18 "2017-12-21T21:03:24Z")
Hi Marius You are shipping a .cache directory with every version from 6.1.0 , included in the download file. In 6.0.1 there is no .cache directory. Looks like a packaking problem . Isn't that the root cause of this problem? Regards Kim ---
**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\ **Post date:** [December 22, 2017, 12:14am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/19 "2017-12-22T00:14:24Z")
Great work, Kim-Kruse-Hansen! I'm so glad you were able to figure out a solution. Thank you for sharing it. And thank you for mentioning the .cache directory. We're looking into it. CJ ---
**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\ **Post date:** [December 22, 2017, 6:54am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/20 "2017-12-22T06:54:10Z")
@Kim-Kruse-Hansen Nice to hear that you've got it solved. I've tried this, but it's not working for me. I've deleted optimize folder, I've take the optimize folder from 6.0.1, I've pushed LS to 6.1.1 and did this all again. Always the same error. @Marius_Dragomir & @cjcenizal: What if I've put up my optimize folder and you could try running with it? [Next page](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754.md?page=2)