# Kibana - cant connect to self hosted elastic

**URL:** <https://discuss.elastic.co/t/kibana-cant-connect-to-self-hosted-elastic/355190>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [March 11, 2024, 8:05pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-self-hosted-elastic/355190 "2024-03-11T20:05:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Dart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick_dart/32/123572_2.png) [@Nick\_Dart](https://discuss.elastic.co/u/Nick_Dart)\
**Post date:** [March 11, 2024, 8:05pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-self-hosted-elastic/355190/1 "2024-03-11T20:05:59Z")

</div>

Hi there, I recently launched my self hosted elastic service, but I can't get Kibana to connect to it.

In my browser, I can access the instance i.e. health, license using a username + password.

However, when launching Kibana, I use "Configure Manually" in the setup, and when i enter the IP address of the instance it gives me an error and in the server I can see "Host "myurl" is not a valid Elasticsearch cluster: "\r\n401 Authorization Required\r\n\r\n

# 401 Authorization Required
\r\n
* * *
nginx/1.25.4\r\n\r\n\r\n""

which to me seems like it needs authorisation. so in my kibana.yml i added the username + password that work in the browser as:

elasticsearch.username: "abc123"  
elasticsearch.password: "123abc"  
elasticsearch.hosts: ["myurl"]

and this gives me a infinite loop with the message:

[2024-03-11T20:03:57.300+00:00][ERROR][plugins.security.authentication] License is not available or does not support security features, re-authentication is not possible (available: true, enabled: false).

yet my license seems fine:

```auto
{
* license:{
  * status: "active",
  * uid: "abc-123-def-456-ghi-789",
  * type: "basic",
  * issue_date: "2024-02-26T14:10:37.215Z",
  * issue_date_in_millis: 1708956637215,
  * max_nodes: 1000,
  * max_resource_units: null,
  * issued_to: "docker-cluster",
  * issuer: "elasticsearch",
  * start_date_in_millis: -1}
}

```

---

<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 11, 2024, 8:13pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-self-hosted-elastic/355190/2 "2024-03-11T20:13:13Z")

</div>

> [@Nick\_Dart](#):
>
> [2024-03-11T20:03:57.300+00:00][ERROR][plugins.security.authentication] License is not available or does not support security features, re-authentication is not possible (available: true, enabled: false).

That is just 1 of many messages when Kibana cannot connect with Elasticsearch... it probably really has nothing to do with the license.

There is probably other connection / authentication error messages

You did not mention Version...

or share your docker compose

what documentation you are following?

Did you follow

> **[Install Elasticsearch with Docker | Elasticsearch Guide \[8.12\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.12/docker.html)**

---

<div class="post-metadata">

**Author:** ![DOkuwa](https://avatars.discourse-cdn.com/v4/letter/d/90db22/32.png) [@DOkuwa](https://discuss.elastic.co/u/DOkuwa)\
**Post date:** [March 12, 2024, 2:50pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-self-hosted-elastic/355190/3 "2024-03-12T14:50:28Z")

</div>

please check your kibana.yml in /etc/kibana and check the elasticsearch name is valid either by hostname or ip

---

<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 9, 2024, 2:50pm UTC](https://discuss.elastic.co/t/kibana-cant-connect-to-self-hosted-elastic/355190/4 "2024-04-09T14:50:51Z")

</div>

Closed on April 9, 2024, 2:50pm UTC

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