# NoNodeAvailableException, cannot connect Java API and Elasticsearch

**URL:** <https://discuss.elastic.co/t/nonodeavailableexception-cannot-connect-java-api-and-elasticsearch/25474>\
**Category:** Elasticsearch\
**Created:** [July 13, 2015, 7:14pm UTC](https://discuss.elastic.co/t/nonodeavailableexception-cannot-connect-java-api-and-elasticsearch/25474 "2015-07-13T19:14:01Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Harlin\_ES](https://avatars.discourse-cdn.com/v4/letter/h/977dab/32.png) [@Harlin\_ES](https://discuss.elastic.co/u/Harlin_ES)\
**Post date:** [July 13, 2015, 8:53pm UTC](https://discuss.elastic.co/t/nonodeavailableexception-cannot-connect-java-api-and-elasticsearch/25474/7 "2015-07-13T20:53:00Z")

</div>

The cluster name should be kept in elasticsearch.yml like you said. Though I can't say for sure ES is finding the right file. The default ES cluster name is just "elasticsearch". Try sending a request to that cluster name instead and see what happens.

---

_[View the full topic](https://discuss.elastic.co/t/nonodeavailableexception-cannot-connect-java-api-and-elasticsearch/25474)._