# Latest Kibana proxy under IIS (Windows)

**URL:** <https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167>\
**Category:** Kibana\
**Created:** [April 12, 2016, 7:54pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167 "2016-04-12T19:54:29Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 12, 2016, 7:54pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/1 "2016-04-12T19:54:29Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\
**Post date:** [April 12, 2016, 8:11pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/2 "2016-04-12T20:11:07Z")

</div>

What URL are you hitting to get at your proxy? Have you tried setting server.port, server.host, and server.basePath in your kibana.yml?

---

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 12, 2016, 8:55pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/3 "2016-04-12T20:55:02Z")

</div>

I have not changed server.port or server.host. Any changes I have tried to server.basePath have not worked. For example, using "/app/kibana" resulted in a url of ...com/app/kibana/app/kibana#/...

---

<div class="post-metadata">

**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\
**Post date:** [April 12, 2016, 9:52pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/4 "2016-04-12T21:52:27Z")

</div>

What is the URL of your proxy?

---

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 12, 2016, 10:40pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/5 "2016-04-12T22:40:49Z")

</div>

It's not public, but it's [dashboard.testsite.com](http://dashboard.testsite.com) and points to 127.0.0.1:5601

---

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 14, 2016, 8:11pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/6 "2016-04-14T20:11:53Z")

</div>

Any updates here? It's been a couple of days. Thanks...

---

<div class="post-metadata">

**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\
**Post date:** [April 15, 2016, 12:06am UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/7 "2016-04-15T00:06:49Z")

</div>

So, both Kibana and your proxy are running on port 5601 of your localhost?

---

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 15, 2016, 4:20am UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/8 "2016-04-15T04:20:21Z")

</div>

Not quite... It proxies port 80 in a browser to Kibana on port 5601. I'm trying to put authentication in front of Kibana. From what I've gathered online, it worked on Kibana 3, but there's been some issues with the latest versions of Kibana 4+. I'm hoping it was solved, but I couldn't find it posted anywhere. Thanks again...

---

<div class="post-metadata">

**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\
**Post date:** [April 15, 2016, 3:37pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/9 "2016-04-15T15:37:27Z")

</div>

Okay, that makes sense. So when you open the developer console, are you seeing any errors? And if so, could you screenshot them or paste them here? Thanks.

---

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 15, 2016, 4:12pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/10 "2016-04-15T16:12:40Z")

</div>

No errors that I can see. Using IE11, the Console is empty, and the Debugger only shows the normal html:

Kibana.ui-app-loading {

From Network:  
Name Protocol Method Result Content type Received Time Initiator  
[http://dashboard.testsite.com/bundles/commons.style.css?v=9732](http://dashboard.testsite.com/bundles/commons.style.css?v=9732) HTTP GET 200 text/css 36.39 KB 24.54 ms parsedElement

I already posted the log output in my first message. From that, it looks like the request is made for the .kibana index, but that's where things stop. Visually, it displays the "please wait while kibana loads" screen, and then it goes to a blank screen. I can't see any error messages anywhere that could point me toward a fix. If there's any additional information I could post that might help, please let me know. Thanks...

---

<div class="post-metadata">

**Author:** ![anhlqn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anhlqn/32/5454_2.png) [@anhlqn](https://discuss.elastic.co/u/anhlqn)\
**Post date:** [April 15, 2016, 4:43pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/11 "2016-04-15T16:43:38Z")

</div>

Give this a try [https://www.ulyaoth.net/resources/tutorial-install-logstash-and-kibana-on-a-windows-server.34/](https://www.ulyaoth.net/resources/tutorial-install-logstash-and-kibana-on-a-windows-server.34/), I was able to use IIS as reverse proxy with some modifications from his guide.

---

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 15, 2016, 8:09pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/12 "2016-04-15T20:09:30Z")

</div>

That is the guide I used initially, but it doesn't seem to work for me. When you say "with some modifications", what modifications are you referring to? The only modifications I made was removing some of the other log services, and stripped it down to ELK (Elasticsearch, Logstash, Kibana), I did not use any of the "beats" products.

---

<div class="post-metadata">

**Author:** ![anhlqn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anhlqn/32/5454_2.png) [@anhlqn](https://discuss.elastic.co/u/anhlqn)\
**Post date:** [April 15, 2016, 11:00pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/13 "2016-04-15T23:00:26Z")

</div>

Follow steps in the section in that guide to install necessary component including creating an IIS site for Kibana, but skip the URL Rewrite Add Rules part,

> Here double click on the "Rewrite URL" button the on I added a red box around and then you should see the following window:

Instead, go to `IIS > Application Request Routing Cache >`, on the right side, click `Server Proxy Settings`, and configure as in screenshots

 ![](https://us1.discourse-cdn.com/elastic/original/2X/c/c20060a3a9581772155d7642f458fef91913f1cf.jpg)

 ![](https://us1.discourse-cdn.com/elastic/original/2X/0/0870f6fa0920e7b11e0e9d488b1289659f28d4b9.jpg)

This will automatically create URL rewrite rules. The `192.168.1.10:5601` should be server IP and Kibana port. Hope this will work for you.

---

<div class="post-metadata">

**Author:** ![johncst](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@johncst](https://discuss.elastic.co/u/johncst)\
**Post date:** [April 16, 2016, 6:33pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/14 "2016-04-16T18:33:47Z")

</div>

Thanks Anh! After a few tweeks of my own, I got it working. Again, many thanks for your help!!!

---

<div class="post-metadata">

**Author:** ![Annie178](https://avatars.discourse-cdn.com/v4/letter/a/4bbf92/32.png) [@Annie178](https://discuss.elastic.co/u/Annie178)\
**Post date:** [January 6, 2017, 5:23pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/15 "2017-01-06T17:23:18Z")

</div>

Hi all,

I've just started to use the elasticstack and I have also encountered problems when trying to use Kibana and IIS. When I access Kibana through the IIS, the index patterns and indices are all mixed up.

I have tried to follow the steps above to see if my issue can be resolved in a similar way, but I cannot find the option IIS \> Application Request Routing Cache \>. I am using IIS version 7. I have used the URL Rewrite Add Rules bit though. Where should I find Application Request Routing Cache? Would any of you be able to help me please?

---

<div class="post-metadata">

**Author:** ![Patrik\_Soderstrom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrik_soderstrom/32/53928_2.png) [@Patrik\_Soderstrom](https://discuss.elastic.co/u/Patrik_Soderstrom)\
**Post date:** [April 13, 2017, 8:59am UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/16 "2017-04-13T08:59:36Z")

</div>

Thanks, I tried this and it worked. But then all pages on my IIS server are redirected to my Kibana instance. Thats not really what I want 🙂 I only would like to have a specific site/dnsname redirected. How can one solve that?  
Thanks

---

<div class="post-metadata">

**Author:** ![anhlqn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anhlqn/32/5454_2.png) [@anhlqn](https://discuss.elastic.co/u/anhlqn)\
**Post date:** [April 14, 2017, 3:19am UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/17 "2017-04-14T03:19:26Z")

</div>

You can create an IIS website with host header and create URL Rewrite rule at the site level, not at the IIS top level like the previous guide. There's no need to configure ARR at the IIS top level.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:32pm UTC](https://discuss.elastic.co/t/latest-kibana-proxy-under-iis-windows/47167/18 "2017-07-06T13:32:16Z")

</div>


