# Unable to access ElasticSearch -Standalone Setup using version 6.8.10

**URL:** <https://discuss.elastic.co/t/unable-to-access-elasticsearch-standalone-setup-using-version-6-8-10/239150>\
**Category:** Elasticsearch\
**Created:** [June 29, 2020, 3:53pm UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-standalone-setup-using-version-6-8-10/239150 "2020-06-29T15:53:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![viuha8](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viuha8/32/21889_2.png) [@viuha8](https://discuss.elastic.co/u/viuha8)\
**Post date:** [June 29, 2020, 3:53pm UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-standalone-setup-using-version-6-8-10/239150/1 "2020-06-29T15:53:03Z")

</div>

Hello All,

Iam trying to set up a Standalone ElasticSearch instance but not a Cluster One.

For that , i have the following in the yml file:

bootstrap.memory\_lock: false  
cluster.name: elasticsearch  
discovery.zen.minimum\_master\_nodes: 1  
http.port: 9200  
network.host: mypcip address.  
discovery.type: single-node  
node.data: true  
node.ingest: false  
node.master: true  
node.max\_local\_storage\_nodes: 1  
node.name: Machine1-VS-016  
path.data: C:\ProgramData\Elastic\Elasticsearch\data  
path.logs: C:\ProgramData\Elastic\Elasticsearch\logs  
transport.tcp.port: 9300  
xpack.license.self\_generated.type: basic  
xpack.security.enabled: false

With this set up, iam not getting any error message in the log , but at the same time, i can n't access the ElasticSearch in port 9200. Please advice us what is the problem in the yml file for this requirement . Iam using ES 6.8.10 version .

Log Details:

[2020-06-29T21:10:00,857][INFO][o.e.x.m.p.l.CppLogMessageHandler] [MACHINE-VS-016] [controller/6980] [Main.cc@109] controller (64 bit): Version 6.8.10 (Build a5f7163bca0250) Copyright (c) 2020 Elasticsearch BV  
[2020-06-29T21:10:01,560][INFO][o.e.d.DiscoveryModule] [[2020-06-29T21:10:00,857][INFO][o.e.x.m.p.l.CppLogMessageHandler] [MACHINE-VS-016] [controller/6980] [Main.cc@109] controller (64 bit): Version 6.8.10 (Build a5f7163bca0250) Copyright (c) 2020 Elasticsearch BV  
[2020-06-29T21:10:01,560][INFO][o.e.d.DiscoveryModule] [MACHINE-VS-016] using discovery type [single-node] and host providers [settings]  
[2020-06-29T21:10:02,388][INFO][o.e.n.Node] [MACHINE-VS-016] initialized  
[2020-06-29T21:10:02,388][INFO][o.e.n.Node] [MACHINE-VS-016] starting ...  
[2020-06-29T21:10:02,591][INFO][o.e.t.TransportService] [MACHINE-VS-016] publish\_address {XX.XX..65.54:9300}, bound\_addresses {XX.XX..65.54:9300}  
[2020-06-29T21:10:02,732][INFO][o.e.h.n.Netty4HttpServerTransport] [MACHINE-VS-016] publish\_address {XX.XX..65.54:9200}, bound\_addresses {XX.XX..65.54:9200}  
[2020-06-29T21:10:02,732][INFO][o.e.n.Node] [MACHINE-VS-016] started  
[2020-06-29T21:10:03,060][INFO][o.e.l.LicenseService] [MACHINE-VS-016] license [0e158899-6a4b-4126-8ef6-cc7d65428b39] mode [basic] - valid  
[2020-06-29T21:10:03,076][INFO][o.e.g.GatewayService] [MACHINE-VS-016] recovered [0] indices into cluster\_state  
] using discovery type [single-node] and host providers [settings]  
[2020-06-29T21:10:02,388][INFO][o.e.n.Node] [MACHINE-VS-016] initialized  
[2020-06-29T21:10:02,388][INFO][o.e.n.Node] [MACHINE-VS-016] starting ...  
[2020-06-29T21:10:02,591][INFO][o.e.t.TransportService] [MACHINE-VS-016] publish\_address {XX.XX..65.54:9300}, bound\_addresses {XX.XX..65.54:9300}  
[2020-06-29T21:10:02,732][INFO][o.e.h.n.Netty4HttpServerTransport] [MACHINE-VS-016] publish\_address {XX.XX..65.54:9200}, bound\_addresses {XX.XX..65.54:9200}  
[2020-06-29T21:10:02,732][INFO][o.e.n.Node] [MACHINE-VS-016] started  
[2020-06-29T21:10:03,060][INFO][o.e.l.LicenseService] [MACHINE-VS-016] license [0e158899-6a4b-4126-8ef6-cc7d65428b39] mode [basic] - valid  
[2020-06-29T21:10:03,076][INFO][o.e.g.GatewayService] [MACHINE-VS-016] **recovered [0] indices into cluster\_state**

---

<div class="post-metadata">

**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\
**Post date:** [July 13, 2020, 6:50am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-standalone-setup-using-version-6-8-10/239150/2 "2020-07-13T06:50:28Z")

</div>

Odd, seems normal - you might try to bind to all addresses (0.0.0.0), but weird it's not coming up for something - is it listening on that port? Not sure how to check that on windows, like 'netstat -l' or you can telnet to that port, then try curl, etc. and work you way up to a browser, but if not listening at all, that's weird = also ensure you have enough heap to get started, like 1GB to make sure it can start (though less should work).

As idiot check, mark darn sure the IP you put in XX.XX..65.54 it really the IP the machine is using; you might be surprised 😉

---

<div class="post-metadata">

**Author:** ![viuha8](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viuha8/32/21889_2.png) [@viuha8](https://discuss.elastic.co/u/viuha8)\
**Post date:** [July 14, 2020, 6:06pm UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-standalone-setup-using-version-6-8-10/239150/3 "2020-07-14T18:06:03Z")

</div>

If i make network.host: 0.0.0.0 , then atleast , **i can able to access Elastic Search using the [http://localhost:9200](http://localhost:9200)** , but not outside of the server.

Please suggest whether is this due to network issue or some other configuration issue

---

<div class="post-metadata">

**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\
**Post date:** [July 16, 2020, 6:47am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-standalone-setup-using-version-6-8-10/239150/4 "2020-07-16T06:47:22Z")

</div>

What is this on, a VM or Docker or some weird networking situation? Any firewalls, iptables/win FW, etc.? Did you verify the IP is what you think it is and that it's listening (netstat -lrnt but this is Windows so who knows) - with it bound to \* and you can reach it we know it's up and listening so we must have networking issues - get reliable machine on same LAN to telnet to that port and work to get that to work, as ES seems fine at least for now (though find way to ensure it's listening on all IPs or \*)

---

<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:** [August 13, 2020, 6:48am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-standalone-setup-using-version-6-8-10/239150/5 "2020-08-13T06:48:25Z")

</div>

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