# Elasticsearch is not accessible via machine IP Address **URL:** \ **Category:** Elasticsearch\ **Created:** [October 31, 2019, 6:25pm UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090 "2019-10-31T18:25:59Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![premkumar](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@premkumar](https://discuss.elastic.co/u/premkumar)\ **Post date:** [October 31, 2019, 6:25pm UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090/1 "2019-10-31T18:25:59Z")
Hi All, I have installed Elasticsearch 7.2 on CentOS 7. After installation without making any changes to the yml file, I was able to access Elasticsearch using the curl command curl [http://localhost:9200/\_cluster/health?pretty](http://localhost:9200/_cluster/health?pretty) Once I got a successful response, I modified network.host: IP\_ADDRESS (IP address of the machine). Once making the changes, I tried starting the Elasticsearch but it fails to start. Noticing the following in the log file. ``` > [2019-10-31T14:21:01,725][INFO][o.e.x.s.a.s.FileRolesStore] [master-node] parsed [0] roles from file [/etc/elasticsearch/roles.yml] ``` > [2019-10-31T14:21:02,271][INFO][o.e.x.m.p.l.CppLogMessageHandler] [master-node] [controller/30093] [Main.cc@110] controller (64 bit): Version 7.2.0 (Build 65aefcbfce449b) Copyright (c) 2019 Elasticsearch BV > [2019-10-31T14:21:02,745][DEBUG][o.e.a.ActionModule] [master-node] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security > [2019-10-31T14:21:03,021][INFO][o.e.d.DiscoveryModule] [master-node] using discovery type [zen] and seed hosts providers [settings] > [2019-10-31T14:21:03,760][INFO][o.e.n.Node] [master-node] initialized > [2019-10-31T14:21:03,761][INFO][o.e.n.Node] [master-node] starting ... > [2019-10-31T14:21:03,886][INFO][o.e.t.TransportService] [master-node] publish\_address {10.202.10.xxx:9300}, bound\_addresses {10.202.10.xxx:9300} > [2019-10-31T14:21:03,893][INFO][o.e.b.BootstrapChecks] [master-node] bound or publishing to a non-loopback address, enforcing bootstrap checks > [2019-10-31T14:21:03,913][ERROR][o.e.b.Bootstrap] [master-node] node validation exception > [1] bootstrap checks failed > [1]: initial heap size [4294967296] not equal to maximum heap size [6442450944]; this can cause resize pauses and prevents mlockall from locking the entire heap > [2019-10-31T14:21:03,916][INFO][o.e.n.Node] [master-node] stopping ... > [2019-10-31T14:21:03,931][INFO][o.e.n.Node] [master-node] stopped > [2019-10-31T14:21:03,932][INFO][o.e.n.Node] [master-node] closing ... > [2019-10-31T14:21:03,942][INFO][o.e.n.Node] [master-node] closed > [2019-10-31T14:21:03,944][INFO][o.e.x.m.p.NativeController] [master-node] Native controller process has stopped - no new native processes can be started Also, tried changing network.host from IP Address to 0.0.0.0. But no luck. Please help me out on this. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 31, 2019, 7:04pm UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090/2 "2019-10-31T19:04:19Z")
Please read [https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html) ---
**Author:** ![premkumar](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@premkumar](https://discuss.elastic.co/u/premkumar)\ **Post date:** [November 1, 2019, 11:47am UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090/3 "2019-11-01T11:47:45Z")
Hi @dadoonet, I tried to explicitly add the bootstrap check in JVM options file. But failed with the same error. After including the following properties in elasticsearch.yml I was able to use curl command via IP Address. transport.host: localhost transport.tcp.port: 9300 network.host: 0.0.0.0 By adding the above properties I was able to start elastic search and access via IP address. But I'm still not able to form a cluster since the port 9300 is mapped to localhost and not accessible from other nodes. ---
**Author:** ![premkumar](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@premkumar](https://discuss.elastic.co/u/premkumar)\ **Post date:** [November 1, 2019, 1:43pm UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090/4 "2019-11-01T13:43:04Z")
Hi @dadoonet This is my elasticsearch.yml settings cluster.name: lower-env-cluster node.name: lower-env-master node.master: true node.data: false path.data: /var/lib/elasticsearch path.log: /var/log/elasticsearch network.host: IP\_ADDRESS discovery.zen.ping.unicast.hosts: ["IP\_ADDRESS"] cluster.initial\_master\_nodes: ["IP\_ADDRESS"] Even if I add the JVM option -Des.enforce.bootstrap.checks=true or not, still getting the same error as mentioned in the initial post. Can you please help out what has to be done. I'm not able to start even one node. I'm trying to configure a cluster with 1 master and 2 data nodes. ---
**Author:** ![premkumar](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@premkumar](https://discuss.elastic.co/u/premkumar)\ **Post date:** [November 1, 2019, 1:48pm UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090/5 "2019-11-01T13:48:25Z")
Hi @the1bit I tried out the steps you have mentioned in the post. > [@Network.host issue: elasticsearch.service: Main process exited, code=exited, status=78](https://discuss.elastic.co/t/network-host-issue-elasticsearch-service-main-process-exited-code-exited-status-78/200193): > > Hi, I try to configure an Elasticsearch cluster on Ubuntu 18.04 (on Azure). The basic installation is fine. Nevertheless when I try to configure the "network.host" value in the configuration file the Elasticsearch service does not start. Error message: systemd[1]: Started Elasticsearch. -- Subject: Unit elasticsearch.service has finished start-up -- Defined-By: systemd -- Support: [http://www.ubuntu.com/support](http://www.ubuntu.com/support) -- Unit elasticsearch.service has finished starting up. -- The start-up result… The above comment holds my configuration of Elasticsearch. But still, I'm not able to start even an elasticsearch node. Could you please help out on this. ---
**Author:** ![premkumar](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@premkumar](https://discuss.elastic.co/u/premkumar)\ **Post date:** [November 1, 2019, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090/6 "2019-11-01T14:51:48Z")
I have found the issue and fixed it myself. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 29, 2019, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-is-not-accessible-via-machine-ip-address/206090/7 "2019-11-29T14:51:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.