# Brand New Installation of ElasticSearch and Kibana on Windows. Kibana is not able to connect to ElasticSearch

**URL:** <https://discuss.elastic.co/t/brand-new-installation-of-elasticsearch-and-kibana-on-windows-kibana-is-not-able-to-connect-to-elasticsearch/294490>\
**Category:** Kibana\
**Created:** [January 16, 2022, 1:52am UTC](https://discuss.elastic.co/t/brand-new-installation-of-elasticsearch-and-kibana-on-windows-kibana-is-not-able-to-connect-to-elasticsearch/294490 "2022-01-16T01:52:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![webdada](https://avatars.discourse-cdn.com/v4/letter/w/4bbf92/32.png) [@webdada](https://discuss.elastic.co/u/webdada)\
**Post date:** [January 16, 2022, 1:52am UTC](https://discuss.elastic.co/t/brand-new-installation-of-elasticsearch-and-kibana-on-windows-kibana-is-not-able-to-connect-to-elasticsearch/294490/1 "2022-01-16T01:52:53Z")

</div>

Both are on latest 7.16.3 version.

Elasticsearch-7.16.3

1. Elasticsearch starts fine, I was able to access  
[http://localhost:9200/](http://localhost:9200/)

2. Kibana command line start error:  
log [20:15:25.611] [warning][process] Error [ProductNotSupportedSecurityError]: The client is unable to verify that the server is Elasticsearch due to security privileges on the server side. Some functionality may not be compatible if the server is running an unsupported product.

---

<div class="post-metadata">

**Author:** ![webdada](https://avatars.discourse-cdn.com/v4/letter/w/4bbf92/32.png) [@webdada](https://discuss.elastic.co/u/webdada)\
**Post date:** [January 16, 2022, 1:53am UTC](https://discuss.elastic.co/t/brand-new-installation-of-elasticsearch-and-kibana-on-windows-kibana-is-not-able-to-connect-to-elasticsearch/294490/2 "2022-01-16T01:53:31Z")

</div>

```auto
  log [20:15:24.579] [info][plugins][ruleRegistry] Installing common resources shared between all indices
  log [20:15:25.213] [info][config][plugins][reporting] Chromium sandbox provides an additional layer of protection, and is supported for Win32 OS. Automatically enabling Chromium sandbox.
  log [20:15:25.611] [warning][process] Error [ProductNotSupportedSecurityError]: The client is unable to verify that the server is Elasticsearch due to security privileges on the server side. Some functionality may not be compatible if the server is running an unsupported product.
    at C:\tools\kibana-7.16.3-windows-x86_64\kibana-7.16.3-windows-x86_64\node_modules\@elastic\elasticsearch\lib\Transport.js:576:19
    at onBody (C:\tools\kibana-7.16.3-windows-x86_64\kibana-7.16.3-windows-x86_64\node_modules\@elastic\elasticsearch\lib\Transport.js:369:9)
    at IncomingMessage.onEnd (C:\tools\kibana-7.16.3-windows-x86_64\kibana-7.16.3-windows-x86_64\node_modules\@elastic\elasticsearch\lib\Transport.js:291:11)
    at IncomingMessage.emit (node:events:402:35)
    at endReadableNT (node:internal/streams/readable:1343:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
  log [20:15:26.455] [error][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. Could not validate credentials provided
  log [20:35:24.587] [error][plugins][ruleRegistry] Error: Timeout: it took more than 1200000ms
    at Timeout._onTimeout (C:\tools\kibana-7.16.3-windows-x86_64\kibana-7.16.3-windows-x86_64\x-pack\plugins\rule_registry\server\rule_data_plugin_service\resource_installer.js:54:20)
    at listOnTimeout (node:internal/timers:557:17)
    at processTimers (node:internal/timers:500:7)
  log [20:35:24.604] [error][plugins][ruleRegistry] Error: Failure installing common resources shared between all indices. Timeout: it took more than 1200000ms
    at ResourceInstaller.installWithTimeout (C:\tools\kibana-7.16.3-windows-x86_64\kibana-7.16.3-windows-x86_64\x-pack\plugins\rule_registry\server\rule_data_plugin_service\resource_installer.js:63:13)
    at ResourceInstaller.installCommonResources (C:\tools\kibana-7.16.3-windows-x86_64\kibana-7.16.3-windows-x86_64\x-pack\plugins\rule_registry\server\rule_data_plugin_service\resource_installer.js:77:5)`Preformatted text`

```

---

<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:** [January 17, 2022, 4:25am UTC](https://discuss.elastic.co/t/brand-new-installation-of-elasticsearch-and-kibana-on-windows-kibana-is-not-able-to-connect-to-elasticsearch/294490/3 "2022-01-17T04:25:25Z")

</div>

Can you share the Elasticsearch logs and the Kibana config?

---

<div class="post-metadata">

**Author:** ![webdada](https://avatars.discourse-cdn.com/v4/letter/w/4bbf92/32.png) [@webdada](https://discuss.elastic.co/u/webdada)\
**Post date:** [January 17, 2022, 2:43pm UTC](https://discuss.elastic.co/t/brand-new-installation-of-elasticsearch-and-kibana-on-windows-kibana-is-not-able-to-connect-to-elasticsearch/294490/4 "2022-01-17T14:43:21Z")

</div>

Thank you @warkolm

1. I used out-of-box Kibana config, essentially no customization. Also I tried to specify the elastic host, which is my localhost, you can see part of the Kibana.yml file below.

=======================================================

# The URLs of the Elasticsearch instances to use for all your queries.

elasticsearch.hosts: ["[http://localhost:9200](http://localhost:9200)"]

# Kibana uses an index in Elasticsearch to store saved searches, visualizations and

# dashboards. Kibana creates a new index if the index doesn't already exist.

#kibana.index: ".kibana"

# The default application to load.

#kibana.defaultAppId: "home"

---

<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:** [February 14, 2022, 2:44pm UTC](https://discuss.elastic.co/t/brand-new-installation-of-elasticsearch-and-kibana-on-windows-kibana-is-not-able-to-connect-to-elasticsearch/294490/5 "2022-02-14T14:44:18Z")

</div>

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