I've been trying to protect Kibana behind a proxy under Windows IIS. I haven't found a solution that works online, so I thought I might ask the experts here.
When I start at localhost:5601, everything works. When I try the proxy, I get the title bar and tabs (discover, visualize, dashboard, settings), but nothing else. There is no content in the main part of the page.
I turned verbose logging on in kibana.yml to see if it would reveal anything. It appears Kibana is making requests to Elasticsearch that are not being answered? As I said, everything works OK using localhost:5601.
respons [12:37:08.192] GET / 200 62ms - 9.0B
respons [12:37:08.317] GET /app/kibana 200 94ms - 9.0B
respons [12:37:08.364] GET /bundles/kibana.style.css?v=9732 200 16ms - 9.0B
respons [12:37:08.380] GET /bundles/commons.style.css?v=9732 200 32ms - 9.0B
respons [12:37:08.567] GET /bundles/commons.bundle.js?v=9732 200 219ms - 9.0B
log [12:37:08.692] [debug][plugin] Checking Elasticsearch version
respons [12:37:08.989] GET /bundles/kibana.bundle.js?v=9732 200 344ms - 9.0B
respons [12:37:09.599] GET /bundles/node_modules/font-awesome/fonts/fontawesome-webfont.eot 200 0ms - 9.0B
respons [12:37:09.717] GET /bundles/src/ui/public/images/kibana.svg 200 0ms - 9.0B
respons [12:37:09.754] POST /elasticsearch/_mget?timeout=0&ignore_unavailable=true&preference=1460489829499 200 5ms - 9.0B
respons [12:37:09.789] POST /elasticsearch/.kibana/index-pattern/_search?fields= 200 0ms - 9.0B
ops [12:37:10.341] memory: 43.8MB uptime: 0:00:22 load: [0.00 0.00 0.00] delay: 2.126
log [12:37:11.231] [debug][plugin] Checking Elasticsearch version
log [12:37:13.755] [debug][plugin] Checking Elasticsearch version
ops [12:37:15.342] memory: 44.1MB uptime: 0:00:27 load: [0.00 0.00 0.00] delay: 1.930
The Kibana and Elasticsearch services are on the same computer (at this point), and I get a response from Elasticsearch using localhost:9200 and 127.0.0.1:9200.
Any help would be appreciated. Thanks!