# Kibana ELB \> Not Loading Kibana EC2 on port 5601

**URL:** <https://discuss.elastic.co/t/kibana-elb-not-loading-kibana-ec2-on-port-5601/118108>\
**Category:** Kibana\
**Created:** [February 1, 2018, 9:51pm UTC](https://discuss.elastic.co/t/kibana-elb-not-loading-kibana-ec2-on-port-5601/118108 "2018-02-01T21:51:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [February 1, 2018, 9:51pm UTC](https://discuss.elastic.co/t/kibana-elb-not-loading-kibana-ec2-on-port-5601/118108/1 "2018-02-01T21:51:09Z")

</div>

Am trying to connect my Kibana ELB to Kibana EC2 Instances.  
My Kibana EC2 are running behind SG taht allows INbOUND access to 5601 from the ELB Security Groups.  
My Kibana ELB is running behind SG taht allows OUTBOUND access to 5601 to the EC2 Security Groups.  
The ELB Listerner is configured on 443 port forwarding to 5601.  
Kibana services have started up successfully on all EC2 Instances

When I do a

> curl -i -XGET [http://localhost:5601](http://localhost:5601)

on my Kibana EC2 Instances I get a 200 OK response  
However, the ELB shows all my EC2 Instances as OutOfService.  
I have a similar configuration on my Elasticsearch ELB\>EC2 and it works fine.

Can anyone suggest what could be wrong ?

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [February 1, 2018, 9:56pm UTC](https://discuss.elastic.co/t/kibana-elb-not-loading-kibana-ec2-on-port-5601/118108/2 "2018-02-01T21:56:05Z")

</div>

Have you made any kibana.yml changes? By default it the server only listens on localhost.

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [February 1, 2018, 9:59pm UTC](https://discuss.elastic.co/t/kibana-elb-not-loading-kibana-ec2-on-port-5601/118108/3 "2018-02-01T21:59:11Z")

</div>

The only changes are to point to my Elasticsearch ELB which I think its working fine. I see the following log in my Journal:

> ["listening","info"],"pid":22561,"message":"Server running at [http://localhost:5601](http://localhost:5601)"}

> ["status","ui settings","info"],"pid":22561,"state":"green","message":"Status changed from uninitialized to green - Ready"

curl -XGET [http://localhost:5601](http://localhost:5601) returns 200 OK when I'm on the instance itself

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [February 2, 2018, 3:29pm UTC](https://discuss.elastic.co/t/kibana-elb-not-loading-kibana-ec2-on-port-5601/118108/4 "2018-02-02T15:29:09Z")

</div>

Update changing the Server Host to 0.0.0.0 fixed this problem. This is my final YML

> server.port: 5601  
> server.host: 0.0.0.0  
> elasticsearch.url: "[https://MYELB:443](https://MYELB:443)"  
> elasticsearch.ssl.verify: false

---

<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 2, 2018, 3:29pm UTC](https://discuss.elastic.co/t/kibana-elb-not-loading-kibana-ec2-on-port-5601/118108/5 "2018-03-02T15:29:10Z")

</div>

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