# Kibana lost all configuration

**URL:** <https://discuss.elastic.co/t/kibana-lost-all-configuration/295578>\
**Category:** Kibana\
**Created:** [January 27, 2022, 12:04pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578 "2022-01-27T12:04:17Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\
**Post date:** [January 27, 2022, 12:04pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578/1 "2022-01-27T12:04:17Z")

</div>

I upgraded Kibana to the lastest version about a month ago and it has been working fine. Today however, when I tried to access Kibana I got this error in my browser:

{"statusCode":500,"error":"Internal Server Error","message":"An internal server error occured."}

Ok, that's strange. So I restarted the service "systemctl restart kibana".

Now, when I navigate to Kibana, all configurations is lost. It asks me to add index patterns to see my data. If I navigate to Stack Monitoring, everything looks fine. ES & Logstash are running and everything is green. But navigating Kibana, all is lost, index patterns, dashboards, everything. It even lost my spaces. It basicly look lite a brand new installation.

So, maybe a corrupt index and Kibana created a new one? Which index could I look at to find the old index-patterns? I did not have them backed up..

Any ideas where to go from here?

Thanks!

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [January 27, 2022, 12:12pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578/2 "2022-01-27T12:12:20Z")

</div>

What version are running? What version did you upgrade from?

Kibana persisted state is stored in an Elasticsearch index specified by configuration setting `kibana.index`. The default value is `.kibana`. Are you setting `kibana.index` configuration? Did your `.kibana` index get removed from Elasticsearch?

---

<div class="post-metadata">

**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\
**Post date:** [January 27, 2022, 12:26pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578/3 "2022-01-27T12:26:51Z")

</div>

Running version is 7.16.2, and I upgraded from 7.15.something. Not sure which.

The "Default index"-setting looks to be empty.

Just saw that my lifetime policies are still there, that's nice.

If I list indecies containing "kibana" it finds these (all green and open), the number is doc-count:

```auto
.kibana-event-log-7.16.2-000001 3
.kibana-event-log-7.16.2-000002 21
.kibana_1 129
.kibana_2 134
.kibana_3 1221
.kibana_7.16.2_001 72
.kibana_task_manager_1 2
.kibana_task_manager_2 3
.kibana_task_manager_7.16.2_001 17
.monitoring-kibana-7-2022.01.21 17280
.monitoring-kibana-7-2022.01.22 17278
.monitoring-kibana-7-2022.01.23 17280
.monitoring-kibana-7-2022.01.24 17278
.monitoring-kibana-7-2022.01.25 17280
.monitoring-kibana-7-2022.01.26 8360
.monitoring-kibana-7-2022.01.27 1500

```

Edit: I believe I ran 7.15.12 before.  
Edit 2: Doc-count was off by one row.

---

<div class="post-metadata">

**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\
**Post date:** [January 27, 2022, 1:04pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578/4 "2022-01-27T13:04:36Z")

</div>

If I do this query, I do see the names of visualizations that are missing.

```auto
GET /.kibana_3/_search
{
    "query": {
        "match_all": {}
    }
}

```

Do you think it would be safe to change the `kibana.index`-setting to .kibana\_3?

---

<div class="post-metadata">

**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\
**Post date:** [January 27, 2022, 1:18pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578/5 "2022-01-27T13:18:04Z")

</div>

Changing defaultIndex to .kibana\_3 and restarting only reverts the setting back to blank.

---

<div class="post-metadata">

**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\
**Post date:** [January 27, 2022, 2:50pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578/6 "2022-01-27T14:50:30Z")

</div>

My fault, I changed the wrong setting.

Solution:

`nano /etc/kibana/kibana.yml`  
Added this row:  
`kibana.index: ".kibana_3"`  
Restarted Kibana

And now it's all back to normal. For some reason Kibana decided to create a new index for its settings and moved my old settings to .kibana\_3. Maybe a bug?

---

<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 24, 2022, 2:51pm UTC](https://discuss.elastic.co/t/kibana-lost-all-configuration/295578/7 "2022-02-24T14:51:15Z")

</div>

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