# Kibana is not loading on 5601

**URL:** <https://discuss.elastic.co/t/kibana-is-not-loading-on-5601/168561>\
**Category:** Kibana\
**Created:** [February 15, 2019, 10:09am UTC](https://discuss.elastic.co/t/kibana-is-not-loading-on-5601/168561 "2019-02-15T10:09:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![soumrock123](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/soumrock123/32/41473_2.png) [@soumrock123](https://discuss.elastic.co/u/soumrock123)\
**Post date:** [February 15, 2019, 10:09am UTC](https://discuss.elastic.co/t/kibana-is-not-loading-on-5601/168561/1 "2019-02-15T10:09:32Z")

</div>

I am using docker-compose to bring up the elastic stack. Everything was working fine till yesterday. I decided to push bulk size database query data, so Kibana started throwing timeout errors. Hence I customized the kibana.yml file as follows -

server.port: 5601  
server.host: "127.0.0.1"  
#server.basePath: ""  
#server.rewriteBasePath: false  
#server.maxPayloadBytes: 1048576  
#server.name: "your-hostname"  
elasticsearch.url: "[http://elasticsearch:9200](http://elasticsearch:9200)"  
#elasticsearch.preserveHost: true  
#kibana.index: ".kibana"  
#kibana.defaultAppId: "home"  
#elasticsearch.username: "user123"  
#elasticsearch.password: "password123"  
#server.ssl.enabled: false  
#server.ssl.certificate: /path/to/your/server.crt  
#server.ssl.key: /path/to/your/server.key  
#elasticsearch.ssl.certificate: /path/to/your/client.crt  
#elasticsearch.ssl.key: /path/to/your/client.key  
#elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"]  
#elasticsearch.ssl.verificationMode: full  
elasticsearch.pingTimeout: 5000  
elasticsearch.requestTimeout: 300000  
#elasticsearch.requestHeadersWhitelist: [authorization]  
#elasticsearch.customHeaders: {}  
elasticsearch.shardTimeout: 100000  
elasticsearch.startupTimeout: 20000  
#elasticsearch.logQueries: false  
#pid.file: /var/run/kibana.pid  
#logging.dest: stdout  
#logging.silent: false  
#logging.quiet: false  
#logging.verbose: false  
#ops.interval: 5000  
#i18n.locale: "en"

After this whenever I run docker-compose.yml, all data get pushed perfectly to Elasticsearch and it is reachable via 127.0.0.1:9200. But Kibana server is not connecting at all and throws "Empty Response error". Can anyone please help?

---

<div class="post-metadata">

**Author:** ![soumrock123](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/soumrock123/32/41473_2.png) [@soumrock123](https://discuss.elastic.co/u/soumrock123)\
**Post date:** [February 15, 2019, 10:31am UTC](https://discuss.elastic.co/t/kibana-is-not-loading-on-5601/168561/2 "2019-02-15T10:31:14Z")

</div>

I just solved it. Apparently while accessing Kibana from a VM or Docker, we need to specify "server.host" parameter in kibana.yml to point to "0.0.0.0" and not localhost or any local IP address.

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [February 18, 2019, 8:37pm UTC](https://discuss.elastic.co/t/kibana-is-not-loading-on-5601/168561/3 "2019-02-18T20:37:32Z")

</div>

Great. Thanks for keeping the community posted.

Cheers,  
Bhavya

---

<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:** [March 18, 2019, 8:37pm UTC](https://discuss.elastic.co/t/kibana-is-not-loading-on-5601/168561/4 "2019-03-18T20:37:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.