# We couldn't log you in. Please try again

**URL:** <https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [September 13, 2022, 12:21pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294 "2022-09-13T12:21:28Z")\
**Posts on this page:** 15\
**Page:** 3

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:28pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/41 "2022-09-13T14:28:06Z")

</div>

Thank you 🙂  
here, I used the super\_user credential

```auto
.kibana-event-log-7.16.2 .kibana-event-log-7.16.2-000005 - - - false
.kibana-event-log-7.11.0 .kibana-event-log-7.11.0-000017 - - - true
.kibana .kibana_7.16.2_001 - - - -
.kibana_7.16.2 .kibana_7.16.2_001 - - - -
exception exception_v1 - - - -
.kibana-event-log-7.11.0 .kibana-event-log-7.11.0-000014 - - - false
.transform-notifications-read .transform-notifications-000002 - - - -
.kibana_task_manager .kibana_task_manager_7.16.2_001 - - - -
.kibana_task_manager_7.16.2 .kibana_task_manager_7.16.2_001 - - - -
.kibana-event-log-7.16.2 .kibana-event-log-7.16.2-000006 - - - false
.kibana-event-log-7.11.0 .kibana-event-log-7.11.0-000016 - - - false
.data-frame-internal-3 .transform-internal-005 - - - -
.kibana-event-log-7.11.0 .kibana-event-log-7.11.0-000015 - - - false
task task_v1 - - - -
.data-frame-internal-3 .transform-internal-007 - - - -
.security .security-7 - - - -
.kibana-event-log-7.16.2 .kibana-event-log-7.16.2-000007 - - - true
.kibana-event-log-7.16.2 .kibana-event-log-7.16.2-000004 - - - false
endorsement endorsement_v2 - - - -

```

---

<div class="post-metadata">

**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\
**Post date:** [September 13, 2022, 2:31pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/42 "2022-09-13T14:31:46Z")

</div>

The aliases for Kibana look good. So I am not sure what happened there with the indices. Strange.

---

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:34pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/43 "2022-09-13T14:34:52Z")

</div>

btw, my kibana page still "not yet ready", maybe because I delete the .Kibana\_security\_session\_1? tried as well to `GET /.kibana_security_session_1` and it happened to not found

```auto
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [.kibana_security_session_1]","index_uuid":"_na_","resource.type":"index_or_alias","resource.id":".kibana_security_session_1","index":".kibana_security_session_1"}],"type":"index_not_found_exception","reason":"no such index [.kibana_security_session_1]","index_uuid":"_na_","resource.type":"index_or_alias","resource.id":".kibana_security_session_1","index":".kibana_security_session_1"},"status":404}

```

---

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:35pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/44 "2022-09-13T14:35:23Z")

</div>

just wondering if we can bring it back thru mapping? 🙏

---

<div class="post-metadata">

**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\
**Post date:** [September 13, 2022, 2:39pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/45 "2022-09-13T14:39:35Z")

</div>

I just noticed that the `.tasks` index is red and that looks to be causing the issue (c.f `Reason: No shard available for [get [.tasks][task]`) .

If it was not restored because of the missing snapshot, then you don't have a choice but to delete that index as well (i.e `DELETE .tasks`).

---

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:41pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/46 "2022-09-13T14:41:49Z")

</div>

should I use super\_user again as my user to delete? or the original user, sorry I am suddenly confused

---

<div class="post-metadata">

**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\
**Post date:** [September 13, 2022, 2:42pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/47 "2022-09-13T14:42:53Z")

</div>

same user as you use for the delete of the `.kibana_security_session_1` index.

---

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:44pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/48 "2022-09-13T14:44:25Z")

</div>

> [@ropc](#):
>
> .tasks

okay, and then I will restart kibana?

---

<div class="post-metadata">

**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\
**Post date:** [September 13, 2022, 2:45pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/49 "2022-09-13T14:45:23Z")

</div>

yes, let's try to restart Kibana again (I cannot remember which process creates the `.tasks`). Let's see if that works, if it does not, I will need to check internally.

---

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:46pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/50 "2022-09-13T14:46:31Z")

</div>

OMGGGG!!!! It worksssssss

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/f/bf7ea40f23a43921958c1d5980598c749240730e.png)

---

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:46pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/51 "2022-09-13T14:46:48Z")

</div>

Thanks for saving meee \<3

---

<div class="post-metadata">

**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\
**Post date:** [September 13, 2022, 2:47pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/52 "2022-09-13T14:47:39Z")

</div>

awesome 🙂 , glad we sorted this out. However, we would not be in this situation if the snapshot was there. I would strongly recommend that you check your snapshot configuration and make sure that the snapshots do not get deleted too fast.

---

<div class="post-metadata">

**Author:** ![wonderland14](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wonderland14/32/102959_2.png) [@wonderland14](https://discuss.elastic.co/u/wonderland14)\
**Post date:** [September 13, 2022, 2:48pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/53 "2022-09-13T14:48:47Z")

</div>

yes I will, Thanks for sharing your time! Happy Monday 😊

---

<div class="post-metadata">

**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\
**Post date:** [September 13, 2022, 2:49pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/54 "2022-09-13T14:49:25Z")

</div>

thank you ^^ Happy Tuesday 😉

---

<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:** [October 11, 2022, 2:50pm UTC](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294/55 "2022-10-11T14:50:10Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/we-couldnt-log-you-in-please-try-again/314294.md?page=2)