# Using --plugin-dir parameter when starting Kibana **URL:** \ **Category:** Kibana\ **Created:** [March 2, 2017, 2:44pm UTC](https://discuss.elastic.co/t/using-plugin-dir-parameter-when-starting-kibana/77156 "2017-03-02T14:44:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vincentforiter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincentforiter/32/16146_2.png) [@vincentforiter](https://discuss.elastic.co/u/vincentforiter)\ **Post date:** [March 2, 2017, 2:44pm UTC](https://discuss.elastic.co/t/using-plugin-dir-parameter-when-starting-kibana/77156/1 "2017-03-02T14:44:58Z")
I am developing plugins for Kibana 5.2.1 on Windows 10, and I have problems when starting Kibana with the `--plugin-dir` parameter. I have the following directory structure: - _KibanaAll_ - _Kibana_ (this is the regular Kibana installation) - _Plugins_ - _MyPlugin1_ - _MyPlugin2_ To start Kibana with a single plugin, I go to the _Kibana_ directory in a terminal (Windows PowerShell), and use the following command: ``` .\bin\kibana.bat --dev --plugin-path "../plugins/MyPlugin1" ``` This works fine, using the `plugin-path` parameter. _Note: I have some paths problems with_ `npm start` _since it uses the linux script, so I use the bat script directly_ * * * Now, I want Kibana to use all my plugins, so I use the `plugin-dir` parameter with the following command `.\bin\kibana.bat --dev --plugin-dir "../plugins"` But then I get this error: `Error: Unmet requirement "elasticsearch" for plugin "MyPlugin1"` See the [full error dump here](http://pastebin.com/Wg9M7Hvy). MyPlugin1 is indeed requiring elasticsearch, but I do not get this error when using `plugin-path` parameter. Am I using the `--plugin-dir` parameter incorrectly? How can I make it work? Thanks in advance! ---
**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:** [March 2, 2017, 7:47pm UTC](https://discuss.elastic.co/t/using-plugin-dir-parameter-when-starting-kibana/77156/2 "2017-03-02T19:47:01Z")
@vincentforiter Would you mind sharing your plugin? I can see if I can reproduce it here on my Windows 10. thx, ---
**Author:** ![vincentforiter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincentforiter/32/16146_2.png) [@vincentforiter](https://discuss.elastic.co/u/vincentforiter)\ **Post date:** [March 3, 2017, 8:12am UTC](https://discuss.elastic.co/t/using-plugin-dir-parameter-when-starting-kibana/77156/3 "2017-03-03T08:12:11Z")
Thanks for your time Thomas. [Here is the plugin.](https://drive.google.com/open?id=0B3S-JlCJ0Q5rZjNodEJlVFFxZ00) I stripped it down so that it's just a visualization showing "myplugin1". I verified that the bug still occurs with this stripped down version. And just so you know, I have the bug without "MyPlugin2" being in the _plugins_ directory. ---
**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:** [March 7, 2017, 10:40pm UTC](https://discuss.elastic.co/t/using-plugin-dir-parameter-when-starting-kibana/77156/4 "2017-03-07T22:40:27Z")
thx @vincentforiter! sorry for the little delay, I was OOO. I'm going to try this out soon ... plz stay tuned ---
**Author:** ![vincentforiter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincentforiter/32/16146_2.png) [@vincentforiter](https://discuss.elastic.co/u/vincentforiter)\ **Post date:** [March 10, 2017, 1:03pm UTC](https://discuss.elastic.co/t/using-plugin-dir-parameter-when-starting-kibana/77156/5 "2017-03-10T13:03:13Z")
Thanks Thomas, I'm looking forward to your response. I have some more informations that might help you solve this: I have problems when running Kibana with two plugins, by using this command: `.\bin\kibana.bat --dev --plugin-path "../plugins/MyPlugin1" --plugin-path "../plugins/MyPlugin2"` Then I get this error: `server log [12:44:21.946] [error][status][ui settings] Status changed from uninitialized to red - UI Settings requires the elasticsearch plugin` The weird thing is: I have no problems running Kibana with only one of those plugins at a time; I only get this error when using both. In this case, you can assume that MyPlugin2 is pretty much identical to MyPlugin1. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 7, 2017, 1:03pm UTC](https://discuss.elastic.co/t/using-plugin-dir-parameter-when-starting-kibana/77156/6 "2017-04-07T13:03:13Z")
Closed on April 7, 2017, 1:03pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.