vannesa
September 19, 2017, 8:54am
1
After installing ROR Pro to Kibana 5.6.1 in development mode, I cannot access Security Setting Page.
ROR Version 1.16.10 for 5.6.0 package (available on pro version)
then I change the kibana version from 5.6.0 -> 5.6.1 in order to make it running.
Then I install it via
bin/kibana-plugin install file:///bla.bla.bla
The login screen is fine, but the plugin - Setting got the following issue when click in:
Kibana did not load properly. Check the server output for more information.
See is there is any solution to solve.
Thanks
sscarduzio
(Simone Scarduzio)
September 19, 2017, 9:19am
2
Hello @vannesa !
See the “touch” command in the Kibana plugin documentation, that would fix it.
---
description: User manual for ReadonlyREST Enterprise/PRO/Free
---
# For Kibana
🧙 **Are you using Kibana version 7.8.x or older? Go to the** [**old platform manual page**](details/kibana-7.8.x-and-older.md)**.**
### Kibana Plugin overview
ReadonlyREST plugin for Kibana is not open source, and it's offered as part of the [ReadonlyREST PRO](https://readonlyrest.com/pro.html) and [ReadonlyREST ENTERPRISE](https://readonlyrest.com/enterprise.html), and [ReadonlyREST Free](https://readonlyrest.com/free) packages. See product descriptions and a comparison chart in the official [ReadonlyREST website](https://readonlyrest.com)
ReadonlyREST plugins for Kibana **always require** ReadonlyREST opens source plugin to be installed in the Elasticsearch nodes your Kibana instance(s) will connect to.
It's not mandatory to install ReadonlyREST in all Elasticsearch nodes, but only in the ones in where you need the HTTP interface to be secured.
### After purchasing
If you didn't install it yet, download the latest [universal build](https://docs.readonlyrest.com/universal-builds) from our [download page](https://readonlyrest.com/download/) and install it manually.
Alternatively, see below if you want to install it directly via the command line without downloading it from the browser.
This file has been truncated. show original
It’s a tiny bug of the build process, which is super easy to work around, but mad annoying. Will look into it to see if anything has changed.