# NoShardAvailableActionException Error on ElasticSearch on Docker

**URL:** <https://discuss.elastic.co/t/noshardavailableactionexception-error-on-elasticsearch-on-docker/279555>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [July 25, 2021, 10:09am UTC](https://discuss.elastic.co/t/noshardavailableactionexception-error-on-elasticsearch-on-docker/279555 "2021-07-25T10:09:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![panagiss](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@panagiss](https://discuss.elastic.co/u/panagiss)\
**Post date:** [July 25, 2021, 10:09am UTC](https://discuss.elastic.co/t/noshardavailableactionexception-error-on-elasticsearch-on-docker/279555/1 "2021-07-25T10:09:05Z")

</div>

I set up basic security for the Elastic Stack plus secured HTTPS traffic recently and i encrypted all communication between the elastic nodes even though i use only one node.  
The thins is now kibana will have this error message `Unable to retrieve version information from Elasticsearch nodes.`. Take in mind that elastic and kibana are running on containers but are able to reach each other. They were working perfectly before i tried to set up the [advanced security](https://www.elastic.co/guide/en/elasticsearch/reference/7.13/security-basic-setup-https.html).

So i checked the logs and elastic throws and error that states: `org.elasticsearch.action.NoShardAvailableActionException: No shard available for [org.elasticsearch.action.fieldcaps.FieldCapabilitiesIndexRequest/unset]`

Here are the full [elastic logs](https://gist.github.com/Panagiss/185776fad6d3597d56886072ae22d602)

So i'm new here and i don't know what is casing this.... but yeah kibana cannot reach now elastic.  
Please help.

Thanks in advance

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 25, 2021, 11:06pm UTC](https://discuss.elastic.co/t/noshardavailableactionexception-error-on-elasticsearch-on-docker/279555/2 "2021-07-25T23:06:39Z")

</div>

You can ignore that one, it's not relevant.

This is though;

```auto
{"type": "server", "timestamp": "2021-07-25T09:55:16,445Z", "level": "WARN", "component": "o.e.x.s.t.n.SecurityNetty4HttpServerTransport", "cluster.name": "docker-cluster", "node.name": "ab3126eeaab4", "message": "received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/172.18.0.2:9200, remoteAddress=/172.18.0.1:40704}", "cluster.uuid": "RYzBZKX6QBGHfy-OE1eX3g", "node.id": "2lN-JR6HR_S8AQ_Qnsh8sw" }

```

Did you configure Kibana to use HTTPS to talk to Elasticsearch?

---

<div class="post-metadata">

**Author:** ![panagiss](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@panagiss](https://discuss.elastic.co/u/panagiss)\
**Post date:** [July 26, 2021, 11:52am UTC](https://discuss.elastic.co/t/noshardavailableactionexception-error-on-elasticsearch-on-docker/279555/3 "2021-07-26T11:52:49Z")

</div>

Yes. I think this is my test i was making with Curl command. I tried to hit https without providing a crt.

So the NoShardAvailableAction is not something that i should fix right?

---

<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 23, 2021, 11:53am UTC](https://discuss.elastic.co/t/noshardavailableactionexception-error-on-elasticsearch-on-docker/279555/4 "2021-08-23T11:53:08Z")

</div>

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