# Kibana\_plugin issues
**URL:** https://discuss.elastic.co/t/kibana-plugin-issues/99617
**Category:** Kibana
**Created:** [September 6, 2017, 5:40pm UTC](https://discuss.elastic.co/t/kibana-plugin-issues/99617 "2017-09-06T17:40:13Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@tbmorris78](https://discuss.elastic.co/u/tbmorris78)
#### Post date: [September 6, 2017, 5:40pm UTC](https://discuss.elastic.co/t/kibana-plugin-issues/99617/1 "2017-09-06T17:40:13Z")
I am using the kibana puppet module, and having some issues with plugin installation. I am on an isolated network and unable to install any plugins except from local file; however, not from the puppet manifest. This is the manifest that I am using:
```
kibana_plugin { 'searchguard-kibana':
url => 'file:///path/to/zip',
}
```
When I run the manifest, I get the following error:
```
Error: /Stage/[main]/uss_install_elk/Kibana_plugin[searchguard]: Could not evaluate:: Attempting to transfer from file:///path/to/zip
Transfering 1845207 bytes.................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Optimizing and caching browser bundles...
```
Any ideas what I am doing wrong?
---
### Author:  [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [September 6, 2017, 7:14pm UTC](https://discuss.elastic.co/t/kibana-plugin-issues/99617/2 "2017-09-06T19:14:01Z")
@tbmorris78 are you copying the files to the server before attempting to use the kibana\_plugin module with the "file:///" syntax? Also, which version of Kibana are you using and which OS are you provisioning?
---
### Author:  [@tbmorris78](https://discuss.elastic.co/u/tbmorris78)
#### Post date: [September 7, 2017, 12:42pm UTC](https://discuss.elastic.co/t/kibana-plugin-issues/99617/3 "2017-09-07T12:42:23Z")
Sorry about leaving that out. I am using Kibana 5.2.2 on CentOS 7.3. Yes, before executing the kibana\_plugin resource, I have a file resource that copies the file over. It would be nice if I could point it at a puppet:// resource, but that is for another venue.
---
### Author:  [@tylerjl](https://discuss.elastic.co/u/tylerjl)
#### Post date: [September 7, 2017, 3:38pm UTC](https://discuss.elastic.co/t/kibana-plugin-issues/99617/4 "2017-09-07T15:38:50Z")
As I mentioned in some messages between us, this is likely a timeout issue, but that's somewhat more tricky to debug, and I think there's a way to get around the error as a workaround since I'm not sure at the moment how to workaround waiting for the long command execution time.
The `kibana_plugin` resource type checks to see whether a plugin is installed by looking for a matching plugin name in the plugins directory. If the plugin ends up at `/usr/share/kibana/plugins/searchguard`, then the resource should be `kibana_plugin { 'searchguard':` in the example manifest you provided.
The example manifest and log output looks different to me, as the resource is named `searchguard-kibana` but the logs say it is `searchguard` - it should be `searchguard` in the manifest, and then hopefully Puppet will be able to detect that it's installed, even if the command exceeded some Puppet timeout and completed in the background.
---
### Author:  [@tbmorris78](https://discuss.elastic.co/u/tbmorris78)
#### Post date: [September 7, 2017, 4:22pm UTC](https://discuss.elastic.co/t/kibana-plugin-issues/99617/5 "2017-09-07T16:22:42Z")
As we discussed in the messages in between us, I had failed to use the `version` parameter. It is working now.
Thank you!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 5, 2017, 4:22pm UTC](https://discuss.elastic.co/t/kibana-plugin-issues/99617/6 "2017-10-05T16:22:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.