# Starting Kibana 5.0 with dev flag throws resource unavailable **URL:** \ **Category:** Kibana\ **Created:** [November 7, 2016, 3:14pm UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238 "2016-11-07T15:14:01Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![satya\_fury](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@satya\_fury](https://discuss.elastic.co/u/satya_fury)\ **Post date:** [November 7, 2016, 3:14pm UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/1 "2016-11-07T15:14:01Z")
Hi, I seem to face a peculiar problem with kibana 5.0 GR. It seems to be working fine when I start the kibana server normally. But when I start with the dev flag it throws a **403 forbidden error** and nothing more. log in console as follow(with verbose **true** ): _log [15:10:28.095] [debug][connection][econnreset] ECONNRESET: Socket was closed by the client (probably the browser) before it could be read completely_ Things were great when I was developing with the alpha versions, donot seem to understand the problem with the stable release. ![](https://us1.discourse-cdn.com/elastic/original/2X/e/e4476bc879857cf21f1a3242f1072d3426e29654.PNG) ![](https://us1.discourse-cdn.com/elastic/original/2X/8/892ddae4fa4203eb150e4047863d42db67f0ef8a.PNG) thanks S ---
**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\ **Post date:** [November 7, 2016, 4:45pm UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/2 "2016-11-07T16:45:32Z")
hi @satya_fury, what does your Kibana startup command look like? ---
**Author:** ![satya\_fury](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@satya\_fury](https://discuss.elastic.co/u/satya_fury)\ **Post date:** [November 8, 2016, 2:41am UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/3 "2016-11-08T02:41:08Z")
It's cd bin && kibana -- dev ---
**Author:** ![satya\_fury](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@satya\_fury](https://discuss.elastic.co/u/satya_fury)\ **Post date:** [November 12, 2016, 1:56pm UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/4 "2016-11-12T13:56:47Z")
Is it only me who is facing the problem? Regards S ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [November 17, 2016, 10:03pm UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/5 "2016-11-17T22:03:25Z")
I'm not sure this a supported way of running Kibana in dev mode. Typically, that process is: - clone the Kibana git repository - run `npm install` - run `npm start` Running `npm start` from the kibana directory where you have the source code internally runs: ```auto sh ./bin/kibana --dev ``` So the problem could be that you should not `cd bin` before running the kibana command. The Contributing to Kibana documentation will tell you everything you need to know about running in a dev mode: [https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md) ---
**Author:** ![satya\_fury](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@satya\_fury](https://discuss.elastic.co/u/satya_fury)\ **Post date:** [December 3, 2016, 6:13am UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/6 "2016-12-03T06:13:41Z")
I am using `cd bin` as I am developing in windows. ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [December 6, 2016, 4:33pm UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/7 "2016-12-06T16:33:46Z")
Hi Satya, The contributing guide I linked to above is also meant for developers who use Windows. Is there are specific problem you have when you use the commands given in the guide? Let us know what you get when you set up NVM and Node/NPM and then do: ```auto nvm install "$(cat .node-version)" npm install npm run elasticsearch npm start ``` Refer to the "Setting Up Your Development Environment" section: [https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#setting-up-your-development-environment](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#setting-up-your-development-environment) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 3, 2017, 4:34pm UTC](https://discuss.elastic.co/t/starting-kibana-5-0-with-dev-flag-throws-resource-unavailable/65238/8 "2017-01-03T16:34:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.