# 6.2.0 starts with error **URL:** \ **Category:** Kibana\ **Created:** [February 6, 2018, 7:41pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706 "2018-02-06T19:41:07Z")\ **Posts on this page:** 16\ **Page:** 1
**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:** [February 6, 2018, 7:41pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/1 "2018-02-06T19:41:07Z")
Hi The bug that was present in Kibana 6.1.x is also present in 6.2.0 , albeit in a slightly different way,. This time it is present like this Oops! Looks like something went wrong. Refreshing may do the trick. Go back Clear your session Fatal Error Uncaught TypeError: ace.require is not a function ([http://localhost:5601/bundles/kibana.bundle.js?v=16562:1](http://localhost:5601/bundles/kibana.bundle.js?v=16562:1)) Version: 6.2.0 Build: 16562 Error: Uncaught TypeError: ace.require is not a function ([http://localhost:5601/bundles/kibana.bundle.js?v=16562:1](http://localhost:5601/bundles/kibana.bundle.js?v=16562:1)) at window.onerror ([http://localhost:5601/bundles/commons.bundle.js?v=16562:11:495755](http://localhost:5601/bundles/commons.bundle.js?v=16562:11:495755)) I will try to find a workaround again. Regards Kim ---
**Author:** ![dsnider](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dsnider/32/44068_2.png) [@dsnider](https://discuss.elastic.co/u/dsnider)\ **Post date:** [February 6, 2018, 8:31pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/2 "2018-02-06T20:31:54Z")
Hey there. Sorry you're running into trouble. When you say you ran into it before, can you let us know whether this was a issue you already reported (or saw in our issues list)? Offhand, my guess is there's some issue with the Ace editor we're using and the compile itself. Anything weird you have setup or any more information you can give? Assume you saw this on the open source version? ---
**Author:** ![paulp1](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@paulp1](https://discuss.elastic.co/u/paulp1)\ **Post date:** [February 7, 2018, 4:45am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/3 "2018-02-07T04:45:20Z")
Hi, This is my first attempt at deploying an Elastic Stack and I am seeing the same error message when I open the Kibana homepage. In setting up my deployment, I followed the instructions here: [https://www.elastic.co/start](https://www.elastic.co/start) Can you please advise? Many thanks, Paul. ---
**Author:** ![Krunal\_kalaria](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krunal_kalaria/32/23862_2.png) [@Krunal\_kalaria](https://discuss.elastic.co/u/Krunal_kalaria)\ **Post date:** [February 7, 2018, 5:59am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/4 "2018-02-07T05:59:18Z")
Hi @Kim-Kruse-Hansen, Did you change or modify in any Elastic Stack plugins ? ---
**Author:** ![Krunal\_kalaria](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krunal_kalaria/32/23862_2.png) [@Krunal\_kalaria](https://discuss.elastic.co/u/Krunal_kalaria)\ **Post date:** [February 7, 2018, 6:05am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/5 "2018-02-07T06:05:42Z")
Hi @paulp1, If you have installed X-pack then following instruction you have to follow: In this Elastic Stack 6.x version doesn't provide default username and password like elasstic and changeme if you have to see your Elastic Stack Default x-pack passwords then you used following command: elasticsearch/bin/x-pack/setup-passwords auto -u "http://elasticsearch\_IP:9200" After this You have to change in your kibana.yml file elasticsearch.username: elastic-username elassticsearch.password: elastic-password Thanks & Regards, Krunal. ---
**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:** [February 9, 2018, 8:55am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/6 "2018-02-09T08:55:00Z")
Hi David, The error is very similar to this > [@Kibana 6.1.0. and newer starts with error](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754): > > 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. TypeError: \_reactcss.handleHover is not a function (http://\_SERVER\_:5601/bundles/kibana.bundle.js?v=16337:67) Additional data: Version: 6.1.0 Build: 16337 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.… My old workaround still works , you have to be very careful from where you launch kibana and its working directory. Regards Kim ---
**Author:** ![vinkhub](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinkhub/32/28582_2.png) [@vinkhub](https://discuss.elastic.co/u/vinkhub)\ **Post date:** [March 8, 2018, 5:27pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/7 "2018-03-08T17:27:27Z")
> [@Kim-Kruse-Hansen](#): > > Uncaught TypeError: ace.require is not a function I get this error "Uncaught TypeError: ace.require is not a function" as soon as I install x-pack in Kibana v6.2.2 as well as v6.1.1 on a windows 10 machine. ---
**Author:** ![Henk\_Nijveld](https://avatars.discourse-cdn.com/v4/letter/h/e19b73/32.png) [@Henk\_Nijveld](https://discuss.elastic.co/u/Henk_Nijveld)\ **Post date:** [March 23, 2018, 12:38pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/8 "2018-03-23T12:38:34Z")
I had the same issue when I used a lowercase driverletter d:\app\kibana\kibana.bat (within nssm) when I change it to the correct case, the optimize step works (after a clean unzip), and the error is gone. ---
**Author:** ![Ashirwad](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@Ashirwad](https://discuss.elastic.co/u/Ashirwad)\ **Post date:** [March 28, 2018, 4:02am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/9 "2018-03-28T04:02:23Z")
Hi, I'm giving the correct case while executing kibana.exe, but still observing the error: Uncaught TypeError: ace.require is not a function ([http://localhost:5601/bundles/kibana.bundle.js?v=16573:22](http://localhost:5601/bundles/kibana.bundle.js?v=16573:22) P.S.: I observed that on Win7 Home edition, kibana worked; but failed on Win7 ultimate. Is Elastic search/Kibana does not support to specific OS edition? Regards, A S Vyawahare ---
**Author:** ![Viorel\_Florian](https://avatars.discourse-cdn.com/v4/letter/v/58956e/32.png) [@Viorel\_Florian](https://discuss.elastic.co/u/Viorel_Florian)\ **Post date:** [April 3, 2018, 1:55pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/10 "2018-04-03T13:55:50Z")
This is a very similar issue to [Kibana 6.1.0. and newer starts with error](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/57) I tried starting kibana version 6.2.3 (with x-pack installed) as a service, manually unsuccessfully, both times making sure the working directory is kibana\_home (d:\ELK\apps\kibana-6.2.3-windows-x86\_64) not the bin directory. I also removed the "optimize" directory without success. ---
**Author:** ![Jaret](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@Jaret](https://discuss.elastic.co/u/Jaret)\ **Post date:** [April 3, 2018, 2:26pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/11 "2018-04-03T14:26:23Z")
I have same problem. Windows 8.1 Enterprise Java 1.8.0\_162 Elastic + Kibana: 6.2.3 I have followed video tutorial and stack in this error: Uncaught TypeError: ace.require is not a function ([http://localhost:5601/bundles/kibana.bundle.js?v=16562:12](http://localhost:5601/bundles/kibana.bundle.js?v=16562:12)) Is it a way to properly and successfully install elastic + kibana under windows ? Regards -Jaret ---
**Author:** ![Viorel\_Florian](https://avatars.discourse-cdn.com/v4/letter/v/58956e/32.png) [@Viorel\_Florian](https://discuss.elastic.co/u/Viorel_Florian)\ **Post date:** [April 4, 2018, 7:34am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/12 "2018-04-04T07:34:13Z")
Any word on a workaround? ---
**Author:** ![jloc141](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@jloc141](https://discuss.elastic.co/u/jloc141)\ **Post date:** [April 9, 2018, 12:23pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/13 "2018-04-09T12:23:47Z")
I have the same issue, is there a fix/workaround for this? I have tried on Windows 10/Windows Server 2016 Java 1.8.0\_161 Elastic (via MSI) + Kibana: 6.2.3 I was using the vanilla install following the elastic instructions ---
**Author:** ![mlashbro](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@mlashbro](https://discuss.elastic.co/u/mlashbro)\ **Post date:** [April 20, 2018, 3:33pm UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/14 "2018-04-20T15:33:12Z")
Maybe I figured this out. I think you have to run this from PowerShell not the command line. At least on my Windows 2016 Server, it wouldn't work until I used PowerShell to launch it. My guess would be that the optimize is creating paths that are too deep for the standard command prompt to handle. ---
**Author:** ![sm-biz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sm-biz/32/30636_2.png) [@sm-biz](https://discuss.elastic.co/u/sm-biz)\ **Post date:** [May 1, 2018, 3:19am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/15 "2018-05-01T03:19:40Z")
FYI - this solution is correct. Plugin activity performed in Kibana on Windows must be done in PowerShell, not cmd Thanks mlashbro ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 29, 2018, 3:19am UTC](https://discuss.elastic.co/t/6-2-0-starts-with-error/118706/16 "2018-05-29T03:19:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.