I put Kibana behind the apache reverse proxy. Many things seem fine, I can access kibana through https://XXXXX/app/kibana and I can also find my indexes in elasticsearch through Management -> Create New Index, I can also find data in Discover. Everything's fine until maybe some configs I don't know have been changed. When I want to refresh an index, there will be 404 GET _fields_for_wildcards error. If I go create a new index, hit the create index pattern button, there will also be 404 Get _fields_for_wildcards error.
In kibana.yml, only server.name is enabled. Before the crash, I've set the server.bathPath to "/kibana" and it works fine. But when crash happens it keeps prompting the red label "kibana is not loaded properly, balabala" until I comment the server.bathPath. I'm very confused about that sudden crash.
Hey @kesha, you're only proxying specific URLs to Kibana, which is really brittle, is there any reason why you aren't doing something similar to the following?
Hi @Brandon_Kobel, thank you for the reply! I've modified the apache config and kibana.yml just as you said and they work perfectly. Actually I want to proxy kibana on a real+virtual directory, like https://XXXXX/{real directory}/{virtual directory}/, for product purpose. I'm figuring out how to do this. But I'm a newbie and I'm still learning. I'm still confused about the difference between https://XXXXX/kibana/ and https://XXXXX/app/kibana/. Why the latter URL is brittle and the former is good?
the /app/kibana route is an internal route that we use, so taking your previous approach you have to ensure that all internal routes are designated to be proxied to Kibana. That's what was happening previously, there was an api/index_patterns route which you missed, and it was causing the 404s to appear.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.