-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ES/Kibana 5.1.1 support is broken #137
Comments
I noticed this too, basically the traffic pattern between Kibana 5 and ES is substantially different than it used to be in Kibana 4 and ES. This means I have to re-do the work of traffic snooping I had to do with Kibana 4 and allowing one by one the operations Kibana 5 needs to function. WIP for now, it will be in the official release of 1.13.0 |
I'm having the same issue with Kibana 5.1.1 / ES 5.1.1 , and Kibana 4 doesn't like ES 5.x.x so this fix is quite necessary. thanks Simone. |
Hi, Thanks. |
I am also meetting the same problem. Do you have ETA? |
I already fixed this on my side, but I'm waiting for kibana 5.1.2 to be released with some bug fixes necessary for this feature to work again as expected. So in a way I'm blocked from releasing a kibana-enabled readonlyrest for 5.x until they resolve on their side. Some progress is being made and I'm collaborating with them because I can test really quickly. Ref. elastic/kibana#9583 |
Awesome! It is really a good news!!! |
Hi , Is there any expected release date for kibana 5.1.2? |
I got this working with the newly released 1.13.0 for ES 5.1.1 and the snapshot version of Kibana: https://github.com/elastic/kibana/tree/5.1#snapshot-builds |
I have tried with the Snap shot version of kibana . It is working. But authentication is asking two times in kibana . Did you face this issue? |
ES and kibana 5.1.2 have been released by the way |
There's a build of ReadonlyREST for 5.1.2 available at https://readonlyrest.com. |
Hi,
I can't work with ES/Kibana 5.1.1. My ES config looks like:
Kibana config looks like:
On running Kibana I see:
and error in browser:
The text was updated successfully, but these errors were encountered: