# Problem with login after upgrading to 8.8.0

**URL:** <https://discuss.elastic.co/t/problem-with-login-after-upgrading-to-8-8-0/335083>\
**Category:** Kibana\
**Created:** [June 2, 2023, 1:07pm UTC](https://discuss.elastic.co/t/problem-with-login-after-upgrading-to-8-8-0/335083 "2023-06-02T13:07:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ccaillet](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@ccaillet](https://discuss.elastic.co/u/ccaillet)\
**Post date:** [June 2, 2023, 1:07pm UTC](https://discuss.elastic.co/t/problem-with-login-after-upgrading-to-8-8-0/335083/1 "2023-06-02T13:07:36Z")

</div>

Hi all,

I've upgrade a cluster from 8.7.1 to 8.8.0 it's a small cluster with 3 nodes and two kibana instances. All is working well until the upgrade to 8.8.0. Globally no error during upgrade BUT unable to log in through Kibana with the following messages on kibana pod log :

```auto
[2023-06-02T12:54:58.155+00:00][ERROR][plugins.security.user-profile] Failed to activate user profile: Request timed out.
[2023-06-02T12:54:58.157+00:00][ERROR][http] TimeoutError: Request timed out
    at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:527:31)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at KibanaTransport.request (/usr/share/kibana/node_modules/@kbn/core-elasticsearch-client-server-internal/src/create_transport.js:51:16)
    at Security.activateUserProfile (/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/api/api/security.js:60:16)
    at UserProfileService.activate (/usr/share/kibana/node_modules/@kbn/security-plugin/server/user_profile/user_profile_service.js:111:26)
    at Authenticator.updateSessionValue (/usr/share/kibana/node_modules/@kbn/security-plugin/server/authentication/authenticator.js:588:24)
    at Authenticator.login (/usr/share/kibana/node_modules/@kbn/security-plugin/server/authentication/authenticator.js:196:37)
    at /usr/share/kibana/node_modules/@kbn/security-plugin/server/routes/authentication/common.js:137:34
    at Router.handle (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/src/router.js:149:30)
    at handler (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/src/router.js:115:50)
    at exports.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
    at Object.internals.handler (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)
    at exports.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)
    at Request._lifecycle (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:371:32)
    at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:281:9)
[2023-06-02T12:55:52.533+00:00][INFO][plugins.security.routes] Logging in with provider "basic" (basic)

```

Anyone with the same error ? Maybe someone could tell me where to start my search for troubleshoot and fix this issue ?

Thanks by advance

Regards,  
Christophe

---

<div class="post-metadata">

**Author:** ![ccaillet](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@ccaillet](https://discuss.elastic.co/u/ccaillet)\
**Post date:** [June 2, 2023, 2:40pm UTC](https://discuss.elastic.co/t/problem-with-login-after-upgrading-to-8-8-0/335083/2 "2023-06-02T14:40:30Z")

</div>

Hi all,

I add here an ugly workaround ...

I've destroyed my Kibana instances and rebuild them. Now works I'm able to log in Kibana again ...

If anyone has a solution without this ugly workaround ... I'm in for test ... I've another cluster to upgrade 🙂

Regards

---

<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:** [June 30, 2023, 2:40pm UTC](https://discuss.elastic.co/t/problem-with-login-after-upgrading-to-8-8-0/335083/3 "2023-06-30T14:40:55Z")

</div>

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