# Cannot access Kibana from machine on different network, getting ERR\_CONNECTION\_RESET **URL:** \ **Category:** Kibana\ **Created:** [August 10, 2019, 10:16pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726 "2019-08-10T22:16:32Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![cspRules](https://avatars.discourse-cdn.com/v4/letter/c/ea5d25/32.png) [@cspRules](https://discuss.elastic.co/u/cspRules)\ **Post date:** [August 10, 2019, 10:16pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/1 "2019-08-10T22:16:32Z")
HI, I have installed Kibana 7.2.1 and hooked it to a locally run Elasticsearch instance. I can see the default app "discovery" from another machine ' s browser when that machine is on the same network. But from my laptop which is on a different network, I keep getting bootstrap.js:108 net::ERR\_CONNECTION\_RESET 200 which is "document.head.appendChild(dom); ``` I believe it may have been some kind of network setting but I am not sure where to look. I can curl to my ES on the same machine and I tried changed port and both has no issues. Other web application that run apache or node.js also has no such issue. Can anyone help? I am using the default kibana.yml and did not change anything other then setting the server.host and server.name to my host name. ``` Can anyone help? Thanks, ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [August 11, 2019, 8:18pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/2 "2019-08-11T20:18:47Z")
In kibana.yml ``` # 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: "localhost" ``` If you don't change this, you Kibana only listens on the localhost interface. ---
**Author:** ![cspRules](https://avatars.discourse-cdn.com/v4/letter/c/ea5d25/32.png) [@cspRules](https://discuss.elastic.co/u/cspRules)\ **Post date:** [August 12, 2019, 2:48am UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/3 "2019-08-12T02:48:27Z")
I have the server.host set to my machine IP address. I can connect to it from machines in the same network. I just can’t connect to it from machines from another network which can ping and curl to elastic or other web server running on the same host as my kibana. . ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [August 12, 2019, 3:21am UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/4 "2019-08-12T03:21:55Z")
Do you have any firewall rules on the system or network firewall devices? netstat -an | grep 5601 --\> check that it is listening on your machine IP. ---
**Author:** ![cspRules](https://avatars.discourse-cdn.com/v4/letter/c/ea5d25/32.png) [@cspRules](https://discuss.elastic.co/u/cspRules)\ **Post date:** [August 12, 2019, 3:41pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/5 "2019-08-12T15:41:17Z")
Hi, I found out it is related to internal security detection that thinks the vendors.bundle.dll has Javascript\_Suspicious\_Aliasing when eval and fromCharCode is aliased which is deemed as a security loop hole. This caused the vendor.bundle.dll response truncated and Kibana response in failed to load error. The question is how to fix this issue... ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [August 12, 2019, 7:48pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/6 "2019-08-12T19:48:38Z")
If it's this [https://www.cvedetails.com/cve/CVE-2019-7616/](https://www.cvedetails.com/cve/CVE-2019-7616/) I think you have to upgrade to 7.3.0 ---
**Author:** ![cspRules](https://avatars.discourse-cdn.com/v4/letter/c/ea5d25/32.png) [@cspRules](https://discuss.elastic.co/u/cspRules)\ **Post date:** [September 4, 2019, 2:59pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/7 "2019-09-04T14:59:19Z")
It is company security issue. Somehow it detect the following item: JavaScript\_Suspicious\_Aliasing and blocked the access. The access is from my laptop to another machine on another network but within the company. If it is in the same subnet, it is not blocked. The blocking result in truncated response which caused the Dom to fail. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 2, 2019, 2:59pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-from-machine-on-different-network-getting-err-connection-reset/194726/8 "2019-10-02T14:59:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.