# I can't access to my kibana remotely

**URL:** <https://discuss.elastic.co/t/i-cant-access-to-my-kibana-remotely/114251>\
**Category:** Kibana\
**Created:** [January 5, 2018, 9:41am UTC](https://discuss.elastic.co/t/i-cant-access-to-my-kibana-remotely/114251 "2018-01-05T09:41:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kaouther\_Mechri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaouther_mechri/32/55329_2.png) [@Kaouther\_Mechri](https://discuss.elastic.co/u/Kaouther_Mechri)\
**Post date:** [January 5, 2018, 9:41am UTC](https://discuss.elastic.co/t/i-cant-access-to-my-kibana-remotely/114251/1 "2018-01-05T09:41:38Z")

</div>

Hello; I've installed the latest version of EKL stack on my linux server.  
I 'can access locally to my kibana but not remotely

curl [http://192.168.9.160:5601](http://192.168.9.160:5601)

var hashRoute = '/app/kibana'; var defaultRoute = '/app/kibana'; var hash = window.location.hash; if (hash.length) { window.location = hashRoute + hash; } else { window.location = defaultRoute; this is locally . Remotely : $ curl -v http://192.168.9.160:5601 \* STATE: INIT =\> CONNECT handle 0x600057980; line 1423 (connection #-5000) \* Rebuilt URL to: http://192.168.9.160:5601/ \* Added connection 0. The cache now contains 1 members \* Trying 192.168.9.160... \* TCP\_NODELAY set \* STATE: CONNECT =\> WAITCONNECT handle 0x600057980; line 1475 (connection #0) \* Connection timed out after 300913 milliseconds \* multi\_done \* stopped the pause stream! \* Closing connection 0 \* The cache now contains 0 members curl: (28) Connection timed out after 300913 milliseconds I've not installed X-pack my kibana.yml section server.port: 5601 # Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values. # The default is 'localhost', which usually means remote machines will not be able to connect. # To allow connections from remote users, set this parameter to a non-loopback address. server.host: 0.0.0.0 server.host: "192.168.9.160" I have no selinux Could you help me please thank you

---

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [January 5, 2018, 1:51pm UTC](https://discuss.elastic.co/t/i-cant-access-to-my-kibana-remotely/114251/2 "2018-01-05T13:51:19Z")

</div>

Your troubleshooting information is very hard to read

I would do the following

```auto
netstat -nltp

```

double check your instance is listing on the right ip. (Probably but a good double check)

It is probably your iptables/firewalld or some ACL/Firewall in between your remote system and Kibana

---

<div class="post-metadata">

**Author:** ![Kaouther\_Mechri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaouther_mechri/32/55329_2.png) [@Kaouther\_Mechri](https://discuss.elastic.co/u/Kaouther_Mechri)\
**Post date:** [January 12, 2018, 8:45am UTC](https://discuss.elastic.co/t/i-cant-access-to-my-kibana-remotely/114251/3 "2018-01-12T08:45:44Z")

</div>

> [@eperry](#):
>
> probably your iptables/firewalld or some ACL/

thank you for your help. It was my firewall

---

<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:** [February 9, 2018, 8:45am UTC](https://discuss.elastic.co/t/i-cant-access-to-my-kibana-remotely/114251/4 "2018-02-09T08:45:57Z")

</div>

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