# None of the configured nodes are available - but only sometimes **URL:** \ **Category:** Elasticsearch\ **Created:** [July 5, 2018, 8:29am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available-but-only-sometimes/138666 "2018-07-05T08:29:01Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![Applesauce](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@Applesauce](https://discuss.elastic.co/u/Applesauce)\ **Post date:** [July 11, 2018, 2:11pm UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available-but-only-sometimes/138666/11 "2018-07-11T14:11:16Z")
Tentative fix: The solution addressed here > [@Transport Client - NoNodeAvailableException\[None of the configured nodes are available\]](https://discuss.elastic.co/t/transport-client-nonodeavailableexception-none-of-the-configured-nodes-are-available/92000/2): > > Dear All I solved the issue. I used the docker image to run the elastic search. The command on this page: [https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html) docker run -p 9200:9200 -e "http.host=0.0.0.0" -e "transport.host=127.0.0.1" docker.elastic.co/elasticsearch/elasticsearch:5.4.3 -e "transport.host=127.0.0.1" did not work. I have to change the elasticsearch.yml, uncomment this line: transport.host: 0.0.0.0 So that the transport client can correctly connect t… where adding transport: 0.0.0.1 to the elasticsearch.yml file. Ours did not have such a line to uncomment and already had lines related to transport, but adding it still worked. I'll monitor the system and close it if it doesn't act up again. --- _[View the full topic](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available-but-only-sometimes/138666)._