# Kibana running on 0.0.0.0 but other computer not able to access it **URL:** \ **Category:** Kibana\ **Created:** [November 20, 2019, 2:44am UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600 "2019-11-20T02:44:54Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)\ **Post date:** [November 20, 2019, 2:44am UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/1 "2019-11-20T02:44:54Z")
Here is the kibana.yml. I can access kibana from my ip address, but when I gave my ip address to another user to access kibana, it wont let them access ```auto # Kibana is served by a back end server. This setting specifies the port to use. 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" ``` I have turned off my firewall as well. Please help! ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [November 20, 2019, 8:41am UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/2 "2019-11-20T08:41:19Z")
Hi @Mehak_Bhargava, Your configuration looks fine. Can the other user access your ip in general? For example does `ping ` work? If that's not the case it's indicating a problem with routing not related to Kibana. ---
**Author:** ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)\ **Post date:** [November 20, 2019, 6:23pm UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/3 "2019-11-20T18:23:33Z")
Hi @flash1293, Others are able to ping my ip. Just not able to access kibana port. What else could be an issue? ---
**Author:** ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)\ **Post date:** [November 20, 2019, 7:44pm UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/4 "2019-11-20T19:44:27Z")
@flash1293 here is my kibana.yml- ```auto # Kibana is served by a back end server. This setting specifies the port to use. 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" # Enables you to specify a path to mount Kibana at if you are running behind a proxy. # Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath # from requests it receives, and to prevent a deprecation warning at startup. # This setting cannot end in a slash. #server.basePath: "" # Specifies whether Kibana should rewrite requests that are prefixed with # `server.basePath` or require that they are rewritten by your reverse proxy. # This setting was effectively always `false` before Kibana 6.3 and will # default to `true` starting in Kibana 7.0. #server.rewriteBasePath: false # The maximum payload size in bytes for incoming server requests. #server.maxPayloadBytes: 1048576 # The Kibana server's name. This is used for display purposes. #server.name: "your-hostname" # The URLs of the Elasticsearch instances to use for all your queries. #elasticsearch.hosts: ["http://localhost:9200"] # When this setting's value is true Kibana uses the hostname specified in the server.host # setting. When the value of this setting is false, Kibana uses the hostname of the host # that connects to this Kibana instance. #elasticsearch.preserveHost: true # Kibana uses an index in Elasticsearch to store saved searches, visualizations and # dashboards. Kibana creates a new index if the index doesn't already exist. #kibana.index: ".kibana" # The default application to load. #kibana.defaultAppId: "home" ``` Please help whats the issue. ---
**Author:** ![AnshuPal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anshupal/32/53261_2.png) [@AnshuPal](https://discuss.elastic.co/u/AnshuPal)\ **Post date:** [November 20, 2019, 8:04pm UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/5 "2019-11-20T20:04:06Z")
Hey Mehak, can you share the netstat results. Use command : netstat -plant and netstat -tlunp Or check if kibana port is in listening state : netstat -plant | grep 5601 Thanks Anshu ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [December 3, 2019, 12:55pm UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/6 "2019-12-03T12:55:59Z")
Hey, could you run the command @AnshuPal posted and paste the results here? It might also be worth it checking with your network administrator whether ports other than 80/443 get blocked. ---
**Author:** ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)\ **Post date:** [December 16, 2019, 7:07pm UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/7 "2019-12-16T19:07:47Z")
I tried the command but I get an error saying "netstat" is not recognized as an internal or external command on my windows terminal. ---
**Author:** ![Camilo\_Diaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/camilo_diaz/32/46512_2.png) [@Camilo\_Diaz](https://discuss.elastic.co/u/Camilo_Diaz)\ **Post date:** [December 16, 2019, 7:27pm UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/8 "2019-12-16T19:27:55Z")
The problem could be a local firewall in your computer. You can test external connectivity using 'telnet `` 5601' and see if they can establish a connection. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 13, 2020, 7:28pm UTC](https://discuss.elastic.co/t/kibana-running-on-0-0-0-0-but-other-computer-not-able-to-access-it/208600/9 "2020-01-13T19:28:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.