# Remotely accessing Kibana Web Interface

**URL:** https://discuss.elastic.co/t/remotely-accessing-kibana-web-interface/228415
**Category:** Kibana
**Created:** [April 16, 2020, 10:28pm UTC](https://discuss.elastic.co/t/remotely-accessing-kibana-web-interface/228415 "2020-04-16T22:28:38Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)
#### Post date: [April 20, 2020, 3:46pm UTC](https://discuss.elastic.co/t/remotely-accessing-kibana-web-interface/228415/5 "2020-04-20T15:46:02Z")

</div>

You'll want to set `server.host` in your `kibana.yml` . If you don't, Kibana will default to only binding to `localhost` . The important part to that is that the container is its own "localhost", so the default value will only allow Kibana to be seen from _inside the container_ , which is clearly not what you want.That's why, in the default config, we set `server.host` to `0` (shortcut for `0.0.0.0` ). This might be the issue - plz check.

Also a similar thread: [Reverse proxy behind nginx docker container not working Kibana 6.2.3](https://discuss.elastic.co/t/reverse-proxy-behind-nginx-docker-container-not-working-kibana-6-2-3/157466/15) which might have some ideas which you can use.

Thanks  
Rashmi

---

_[View the full topic](https://discuss.elastic.co/t/remotely-accessing-kibana-web-interface/228415)._