### Author:  [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)
#### Post date: [June 15, 2017, 6:12pm UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/1 "2017-06-15T18:12:45Z")
Hi all,
I installed elasticsearch 5.2.2 and kibana 5.2.2 on one ec2 instance. Both runs without any issue. But I cannot open kibana interface, for example in localhost mode, I can check kibana interface by 127.0.0.1:5601. My ec2 current IP for example is 172.31.12.21, why I cannot open that kibana interface by 172.31.12.21:5601 through the browser. Thanks for your answer.
Here's my kibana.yml:
server.host: "172.31.12.21"
elasticsearch.url: "[http://172.31.12.21:9200](http://172.31.12.21:9200)"
Here's my elasticsearch.yml:
network.host: 172.31.21.47
node.master: true
node.data: true
[cluster.name](http://cluster.name): mastertest
action.auto\_create\_index: true
bootstrap.system\_call\_filter: false
path.logs: /mnt/volume/logs
path.data: /datab
discovery.zen.ping.unicast.hosts: ["172.31.21.47:9300"]
---
### Author:  [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [June 15, 2017, 9:18pm UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/2 "2017-06-15T21:18:10Z")
Could you confirm that kibana is listening on that IP and port?
`lsof -Pan -p -i`
Also, I noticed in your kibana.yml your elasticsearch url doesn't match your elasticsearch.yml's network.host setting. Is that a mistake?
---
### Author:  [@tatdat](https://discuss.elastic.co/u/tatdat)
#### Post date: [June 16, 2017, 12:46am UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/3 "2017-06-16T00:46:13Z")
use command
> netstat -tupln
And looking for port 5601. What is ip listening? Your IP or `127.0.0.1`.
If u see `127.0.0.1:5601`. Open kibana config and change `localhost` to your IP (`172.31.12.21`)
> /etc/kibana/kibana.yaml
> server.host: "localhost" (line 7)
---
### Author:  [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)
#### Post date: [June 16, 2017, 2:28am UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/4 "2017-06-16T02:28:30Z")
Sorry, I made a mistake. But after I changed, I still cannot see Kibana interface by tying 172.31.12.21:5601. Any ideas? Thanks.
Here's my kibana.yml:
server.host: "172.31.12.21"
elasticsearch.url: "[http://172.31.12.21:9200](http://172.31.12.21:9200)"
Here's my elasticsearch.yml:
network.host: 172.31.12.21
node.master: true
node.data: true
[cluster.name](http://cluster.name): mastertest
action.auto\_create\_index: true
bootstrap.system\_call\_filter: false
path.logs: /mnt/volume/logs
path.data: /datab
discovery.zen.ping.unicast.hosts: ["172.31.12.21:9300"]
---
### Author:  [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)
#### Post date: [June 16, 2017, 2:29am UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/5 "2017-06-16T02:29:18Z")
@tatdat
Thanks for your answer. I updated my answer, please see if you have any ideas. Thanks.
---
### Author:  [@Makra](https://discuss.elastic.co/u/Makra)
#### Post date: [June 16, 2017, 5:02am UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/6 "2017-06-16T05:02:45Z")
Check if the firewall is blocking the traffic in the port 9200, 5601
Also in EC2 security group you have to add the above ports.
---
### Author:  [@tatdat](https://discuss.elastic.co/u/tatdat)
#### Post date: [June 16, 2017, 7:13am UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/7 "2017-06-16T07:13:01Z")
@Ximeng_Zhao
How do u start kibana?
Can u start kibana manual with command and give me log in your screen ? ( with centos )
> /usr/share/kibana/bin/kibana
---
### Author:  [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)
#### Post date: [June 16, 2017, 3:07pm UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/8 "2017-06-16T15:07:19Z")
log [15:06:22.229] [info][status][plugin:kibana@5.2.2] Status changed from uninitialized to green - Ready
log [15:06:22.299] [info][status][plugin:elasticsearch@5.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [15:06:22.361] [info][status][plugin:console@5.2.2] Status changed from uninitialized to green - Ready
log [15:06:22.812] [info][status][plugin:timelion@5.2.2] Status changed from uninitialized to green - Ready
log [15:06:22.829] [info][listening] Server running at [http://172.31.21.47:5601](http://172.31.21.47:5601)
log [15:06:22.830] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow
log [15:06:23.030] [info][status][plugin:elasticsearch@5.2.2] Status changed from yellow to green - Kibana index ready
log [15:06:23.031] [info][status][ui settings] Status changed from yellow to green - Ready
---
### Author:  [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)
#### Post date: [June 16, 2017, 3:23pm UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/9 "2017-06-16T15:23:11Z")
EC2 security group setting Inbound:
Type Protocol Port Range Source
All traffic All All 0.0.0.0/0
Is that correct if I set as all traffic?
---
### Author:  [@dmcn\_es](https://discuss.elastic.co/u/dmcn_es)
#### Post date: [June 16, 2017, 4:00pm UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/10 "2017-06-16T16:00:13Z")
hi,
You can set inbound as above for test proposes for a short time.
What is you outbound setting ? Does it include port 5601?
which linux flavour do you use? Do the firewall rules let port 5601 out. ?
systemctl status firewalld
Are you sure 172.31.21.47 is the public allocated by AWS when the instance started, could you be using the private IP by mistake ?
When you give below command is pot 5601 listed as LISTENING. ?
tcp 0 0 0.0.0.0:5601 0.0.0.0:\* LISTEN 123/node
netstat -anp
Daragh
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 14, 2017, 4:00pm UTC](https://discuss.elastic.co/t/kibana-interface-open-problem/89604/11 "2017-07-14T16:00:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.