# Kibana dev wont startup

**URL:** <https://discuss.elastic.co/t/kibana-dev-wont-startup/366488>\
**Category:** Kibana\
**Tags:** kibana-plugin-development\
**Created:** [September 12, 2024, 4:20pm UTC](https://discuss.elastic.co/t/kibana-dev-wont-startup/366488 "2024-09-12T16:20:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![OAJ](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oaj/32/137265_2.png) [@OAJ](https://discuss.elastic.co/u/OAJ)\
**Post date:** [September 12, 2024, 4:20pm UTC](https://discuss.elastic.co/t/kibana-dev-wont-startup/366488/1 "2024-09-12T16:20:09Z")

</div>

Hi all,

So after running yarn build for my custom plugin. Only localhost:9200 works. But localhost:5601 wont startup for kibana dev

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [September 13, 2024, 11:20am UTC](https://discuss.elastic.co/t/kibana-dev-wont-startup/366488/2 "2024-09-13T11:20:20Z")

</div>

Added #kibana-plugin-development

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [September 13, 2024, 11:21am UTC](https://discuss.elastic.co/t/kibana-dev-wont-startup/366488/3 "2024-09-13T11:21:47Z")

</div>

Hi @OAJ,

That suggests that the local Kibana is not able to start. I assume you don't have another process running on that port? Do you see any errors at all?

---

<div class="post-metadata">

**Author:** ![OAJ](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oaj/32/137265_2.png) [@OAJ](https://discuss.elastic.co/u/OAJ)\
**Post date:** [September 15, 2024, 5:15pm UTC](https://discuss.elastic.co/t/kibana-dev-wont-startup/366488/4 "2024-09-15T17:15:33Z")

</div>

Ah yes the process was running on multiple instances thanks for your help
