# Elasticsearch 8.1.0 on Windows VM running in Azure not showing or creating Indices

**URL:** <https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561>\
**Category:** Elasticsearch\
**Tags:** windows-installer, windows\
**Created:** [March 13, 2022, 10:02am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561 "2022-03-13T10:02:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ddynamight](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ddynamight/32/102974_2.png) [@ddynamight](https://discuss.elastic.co/u/ddynamight)\
**Post date:** [March 13, 2022, 10:02am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561/1 "2022-03-13T10:02:57Z")

</div>

I have just set up Elasticsearch 8.1.0 on a Windows Server 2022 VM running inside Azure, but the indexing is not working. I am unable to create new indices or view the default indices.

A get request to [localhost:9200/\_cat/indices?v](http://localhost:9200/_cat/indices?v) returns a blank response with no indices.

I will like to know if there is something I am missing or not doing right.

Here is my Elasticsearch.yml config.

```auto
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: myelastic
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1

#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#

path.data: C:\ProgramData\Elastic\Elasticsearch\data

#
# Path to log files:
#

path.logs: C:\ProgramData\Elastic\Elasticsearch\logs

#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#

bootstrap.memory_lock: false

#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
#network.host: localhost
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#

http.port: 9200
transport.port: 9300

#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#

cluster.initial_master_nodes: ["cs-w22"]

#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false

action.auto_create_index: .monitoring*,.watches,.triggered_watches,.watcher-history*,.ml*

#----------------------- BEGIN SECURITY AUTO-CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically      
# generated to configure Elasticsearch security features on 08-03-2022 07:32:28
#
# --------------------------------------------------------------------------------

http.host: [_local_, _site_]

# Enable security features
xpack.license.self_generated.type: basic
xpack.security.enabled: false

```

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [March 13, 2022, 6:12pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561/2 "2022-03-13T18:12:29Z")

</div>

You need to check the Elasticsearch logs.

Check the logs and share them here.

---

<div class="post-metadata">

**Author:** ![ddynamight](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ddynamight/32/102974_2.png) [@ddynamight](https://discuss.elastic.co/u/ddynamight)\
**Post date:** [March 13, 2022, 6:24pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561/3 "2022-03-13T18:24:51Z")

</div>

Here is the log:

Posting it here is a bit limiting, so I created a gist on github.

[Elasticsearch log (github.com)](https://gist.github.com/ddynamight/2c2c49b1107ce98c4830bf929879557d)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [March 15, 2022, 4:27am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561/4 "2022-03-15T04:27:32Z")

</div>

Hi @ddynamight

If you are getting

```auto
curl http://localhost:9200/_cat/indices?v
curl: (52) Empty reply from server

```

That is probably because 8.1 runs `https` so you should trying

`curl -u elastic:password -k https://localhost:9200/_cat/indices?v`

---

<div class="post-metadata">

**Author:** ![ddynamight](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ddynamight/32/102974_2.png) [@ddynamight](https://discuss.elastic.co/u/ddynamight)\
**Post date:** [March 15, 2022, 10:29pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561/5 "2022-03-15T22:29:32Z")

</div>

Hi @stephenb,

Even that didn't work. In cases when I do

`http://localhost:9200/_cat/command`

They all return a value. Only the indices show blank.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [March 16, 2022, 12:04am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561/6 "2022-03-16T00:04:01Z")

</div>

@ddynamight can you show the results please?

BTW

`http://localhost:9200/_cat/command` is not a valid command

If this is 8.1 did you configure the default security? if so `http` will not work

---

<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:** [April 13, 2022, 12:04am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-on-windows-vm-running-in-azure-not-showing-or-creating-indices/299561/7 "2022-04-13T00:04:17Z")

</div>

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