# Inability to sign in to Kibana Dashboard

**URL:** <https://discuss.elastic.co/t/inability-to-sign-in-to-kibana-dashboard/338884>\
**Category:** Kibana\
**Created:** [July 20, 2023, 1:23pm UTC](https://discuss.elastic.co/t/inability-to-sign-in-to-kibana-dashboard/338884 "2023-07-20T13:23:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohzis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohzis/32/123699_2.png) [@mohzis](https://discuss.elastic.co/u/mohzis)\
**Post date:** [July 20, 2023, 1:23pm UTC](https://discuss.elastic.co/t/inability-to-sign-in-to-kibana-dashboard/338884/1 "2023-07-20T13:23:01Z")

</div>

i deployed my elasticsearch, kibana and fleet using aks, but recently i started getting an error as pasted below.

## [2023-07-19T16:33:48.709+00:00][ERROR][plugins.security.user-profile] Failed to activate user profile: {"error":{"root\_cause":[{"type":"cluster\_block\_exception","reason":"index [.security-profile-8] blocked by: [TOO\_MANY\_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];"}],"type":"cluster\_block\_exception","reason":"index [.security-profile-8] blocked by: [TOO\_MANY\_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];"},"status":429}.

This is talking about my discs, now I am afraid that if I increase the nod count in my elasticsearch.yaml file in the prod environment, my storage might be affected asides the number of pods it should create.

Can anyone give me an advise on what to do?

---

<div class="post-metadata">

**Author:** ![mohzis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohzis/32/123699_2.png) [@mohzis](https://discuss.elastic.co/u/mohzis)\
**Post date:** [July 20, 2023, 1:36pm UTC](https://discuss.elastic.co/t/inability-to-sign-in-to-kibana-dashboard/338884/2 "2023-07-20T13:36:40Z")

</div>

I have it fixed now

I increased my node counts and it worked

---

<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:** [July 23, 2023, 7:14pm UTC](https://discuss.elastic.co/t/inability-to-sign-in-to-kibana-dashboard/338884/3 "2023-07-23T19:14:38Z")

</div>

Yes, that message above means you exceed the Disk Usage Watermark... so adding more nodes provided more disk space, that is one way to solve that... keep and eye as you may fill up again.

---

<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:** [August 20, 2023, 7:14pm UTC](https://discuss.elastic.co/t/inability-to-sign-in-to-kibana-dashboard/338884/4 "2023-08-20T19:14:59Z")

</div>

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