# Index not creating **URL:** \ **Category:** Beats\ **Created:** [July 8, 2016, 5:33am UTC](https://discuss.elastic.co/t/index-not-creating/55016 "2016-07-08T05:33:54Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bala1](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@bala1](https://discuss.elastic.co/u/bala1)\ **Post date:** [July 8, 2016, 5:33am UTC](https://discuss.elastic.co/t/index-not-creating/55016/1 "2016-07-08T05:33:54Z")
I have started ES and trying to fetch indices on kibana-4 but getting error while fire command on powershell command: Output: 2016/07/08 05:12:35.119557 client.go:302: DBG Ping request failed with: Head [http://search-hmetest-tfy67zzlrfp7behwmnc2](http://search-hmetest-tfy67zzlrfp7behwmnc2) [vlgjxi.eu-west-1.es.amazonaws.com:9200](http://vlgjxi.eu-west-1.es.amazonaws.com:9200): dial tcp 52.17.142.15:9200: connectex: A connection attempt failed because the c onnected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. and on kiban setting panel show Unable to fetch mapping. Do you have indices matching the pattern? ![](https://us1.discourse-cdn.com/elastic/original/2X/1/1bc89121605f54c8c65d8277987c5a8405268289.JPG) ![](https://us1.discourse-cdn.com/elastic/original/2X/f/f806030542957a43a0e39c410ba1139fd1558bea.JPG) ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [July 8, 2016, 5:35am UTC](https://discuss.elastic.co/t/index-not-creating/55016/2 "2016-07-08T05:35:04Z")
Topbeat isn't able to connect to Elasticsearch. That's a network connectivity issue that we can't really help you with. ---
**Author:** ![bala1](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@bala1](https://discuss.elastic.co/u/bala1)\ **Post date:** [July 8, 2016, 5:41am UTC](https://discuss.elastic.co/t/index-not-creating/55016/3 "2016-07-08T05:41:14Z")
I really appreciate **magnusbeack** for you quick reply but when i am trying it on AWS server it happens same and ES Service and AWS EC2 in same VPC also access policy set to **allow all**. should i get assistance from AWS or is there any configuration mistake. ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [July 8, 2016, 5:59am UTC](https://discuss.elastic.co/t/index-not-creating/55016/4 "2016-07-08T05:59:02Z")
If the computer that Topbeat runs on can't connect to port 9200 on your ES server then it's a network problem that has nothing to do with Topbeat. I don't know your network topology so I have no idea who you should talk to. It could be a local firewall, an AWS setting, or something in between. Good luck. ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [July 8, 2016, 11:33am UTC](https://discuss.elastic.co/t/index-not-creating/55016/5 "2016-07-08T11:33:22Z")
have you tried to ping, telnet and curl with into elasticsearch host? ---
**Author:** ![bala1](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@bala1](https://discuss.elastic.co/u/bala1)\ **Post date:** [July 8, 2016, 11:35am UTC](https://discuss.elastic.co/t/index-not-creating/55016/6 "2016-07-08T11:35:46Z")
Yes issue resolve after apply 443 port to host because AWS ES only access through the **https** port ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 29, 2016, 5:33am UTC](https://discuss.elastic.co/t/index-not-creating/55016/7 "2016-07-29T05:33:56Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.